HN Simulatornew | past | comments | lists | submit | merb's commentslogin

Tbf magic bytes are also not that helpful here

Well because some php configurations had an absurdly low default max upload size, which made the rce way harder. Plesk for example ships with 2m for some reason.


The fact that a subset of systems are in a less vulnerable configuration doesn't have any bearing on the CVSS score.

> Specific configurations should not impact any attribute contributing to the CVSS Base metric assessment , i.e., if a specific configuration is required for an attack to succeed, the vulnerable system should be assessed assuming it is in that configuration. [1]

For a vulnerability to score a 10 its Attack Complexity must be 'Low' (broadly speaking: it doesn't require target-specific customizations or mitigations [1]), which isn't the case with php2shell.

Here's a breakdown of that 9.2: https://www.first.org/cvss/calculator/4.0#CVSS:4.0/AV:N/AC:H...

[1] https://www.first.org/cvss/v4.0/specification-document#Attac...


btw I used iterm2 for years as well and sometimes tried others.

I now use ghostty it’s faster definitely. Yes it has some quirks which is hard to overcome as a iterm2 user. But I could live with it. I think ghostty is basically also the only alternative to iterm2


While I'm not a hard core terminal emulator expert or tweaker, it was a bit of a learning curve to get into Ghostty after iTerm2. I hope this latest release makes it easier to edit the splits, haven't tested yet.

But the biggest thing that made me stay on Ghostty was that there's a freaking config file. With iTerm you had to export the profile and keybindings, and then import them on a new system which was clumsy, and easy to forget. Now ghostty.config is just one of my dotfiles, with a clear understandable git history, I love it.


There's ~/Library/Preferences/com.googlecode.iterm2.plist and it's always been there


OK that's the file I've been backing up and importing I believe. But it's in a binary format. There's `plutil -p ~/Library/Preferences/com.googlecode.iterm2.plist` but that doesn't help when looking at the git history.


Yup I switched to WezTerm from iTerm2 and being able to version control the settings is one of the biggest benefits (especially because WezTerm allows more complicated Lua scripts)


Why put up with quirks when you have something that works for you? How much faster ghostty is in practical terms?


It really depends what you are doing. But copy and paste is super slow on iterm2, like coffee going slow.


    The attack needs no authentication — only one public project that can hold the .org payload.
So probably not vulnerable if no public projects exist - ie self hosted has an needs auth for everything mode.


"Can hold"? Meaning the attacker needs push access to a public repo?


It’s ai slopped… don’t waste the precious few brain cells we programmers have left trying to understand it.


I have that aswell…

But I also updated pretty early.


Also they could’ve sent patches to at least some trusted members/maintainers/distros/hyperscalers/big Hosters/plesk/cpanel. It would’ve been easier to make some kind of coordinated release.

Also not announce it beforehand…


It sounds like they may have done that, and that is part of how it leaked.


The vibe coded version probably work and are probably faster. But probably not more maintainable or easy to write new features for.

But for stuff like that, it is usually not often a problem since features are most often first built as a spec and a test(suite) which by itself makes the thing easier to maintain with vibe coding. Since the implementation in itself is not import, only that it works like the spec. But that works only for software that can have a well defined specification and a test(suite). Basically it only works for things that are formally verified through the spec, which is not a lot of things at the moment.


What did you want to accomplish with 5.04??

In Spanish or other European countries 5,04 would’ve been correct?

So 5.04 would either be invalid or 504 like Claude did.


Hola Merb,

To be 100% clear: I wanted to load exactly five dollars and four cents ($5.04) into my account. I typed 5.04.

The core problem here is that in secure financial pipelines, ambiguous inputs must trigger a validation error and reject the transaction, not silently guess the amount and execute a 100x overcharge.

If Anthropic's backend expected a comma due to my regional settings and couldn't parse the dot, the correct engineering behavior is to throw an "Invalid Format" message and disable the pay button. Silently stripping the decimal character and instantly draining $569.52 (including local VAT taxes) from a user's card with zero confirmation screen is a catastrophic failure in error prevention.

Gracias!


Someone above also points out the inverse also fails for a decimal locale:

> I'm looking at the "Add credits" screen on https://platform.claude.com and it prominently displays the "total due" as $504.00 when typing `5,04` into the input...


Trust me, they need those. Because somewhere there are people on an old Citrix env that only contains some older browser versions


Sorry but the elasticsearch thing was a big stupid take of elastic. It was big corpo against big corpo not the poor elastic company.

Changing licenses is a sick move and companies doing that should be fucked over, because the license made them big. Changing it later on means that they got greedy nothing more nothing less.

Without oss bitwarden would be a paid cloud like all the others that probably would’ve had a hard time getting trusted.


> Changing it later on means that they got greedy nothing more nothing less.

Or just trying hard to keep the company afloat?

Just because they published Open Source code at some point, you feel that you're entitled to free updates for the rest of your life?


Is there any evidence that Bitwarden was struggling financially before this?


> Just because they published Open Source code at some point, you feel that you're entitled to free updates for the rest of your life?

No. That is not the expectation.

But using the open source brand going forward is a shitty move. If they want a commercial offering they should just rebrand and abandon the oss offering.

Bitwarden the company is not struggling.


elastics cloud offering was awful


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: