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

They got hacked, lawyers were called, they posted vague statements.

The equivalent of “smile and wave, smile and wave”.

My money is on the group that hacked them to publish more information.


I believe they are obliged to notify the public & a few govt departments (OAIC & Signals Directorate) as supermarkets are considered critical infrastructure - food/logistics.

https://www.cisc.gov.au/resources-subsite/Documents/ncsi-gui...


Very british of them.

Hardly. ;)

> Just because the response can be "No", it doesn't mean Google didn't require _something_ from ffmpeg.

It requires zero things from ffmpeg. As it is today, they privately contact them with info about the vulnerability and also informs them that in 90 days the whole world will know about the vulnerability too.

ffmpeg ca either fix it if it wants or be "cool story bro, yolo".


So, what if the project they are reporting to has a vulnerability disclosure project with 180 days notice?

Project Zero doesn’t care.

Why would a project get to tell somebody who found a vuln when they can talk about it to the public?

Imagine you go to a restaurant and see an issue with the food. You tell the restaurant “hey I’m writing a review of this. I’m going to publish it in a month; if you want to include any response before that time I’ll include it in my review”.

It would be nuts for the restaurant to say “actually we require you wait 180 days to publish”.

You can also take a look at how essentially all investigative reporting works, where a reporter asks the subject for comment before publishing.


You might be surprised to learn that actually is illegal in some countries.

Famously, leaving reviews on TripAdvisor in Germany can get you sued.


You can be sued for anything.

I did some light searching here and the examples appear to match what I’d expect: you can be liable if you lie about facts, but if you’re sharing your opinions or accurately relating what happened, you’re fine.

Can you provide some examples for your claim?


Even if he managed to provide examples it would merely be demonstrating a restriction on the individual to openly speak his mind. Hardly something to celebrate.

Similarly, if there were a jurisdiction somewhere in the world where vulnerability research was criminalized I don't think that would be relevant to the conversation we're having here. AFAIK project zero is subject only to US law.


Project Zero is part of Google/Alphabet, which operates globally and has a legal presence in many countries. I can’t speak to where individuals on Project Zero are based.

If they provided evidence of their claim, I would have learned something new and it would be potentially interesting to the discussion about the risks of making public factual disclosures in places other than the US. It’s not a matter of whether or not it would be something to celebrate.


You are missing something: the simple fact that Google operates in many countries does not make it liable in those countries for what other Business Units inside it do.

What you’re calling a simple fact here isn’t really either.

Countries attempt, with varying levels of success, to regulate international entities based on activity they conduct elsewhere in the world all the time.

And as an aside, it’s not clear that Project Zero is actually purely US-based: https://www.google.com/about/careers/applications/jobs/resul...


Well TBF that is entirely dependent on how large their market is in that country and on how many assets they have there that could realistically be seized by the authorities. But in practice it does seem difficult to imagine that sort of stuff being relevant to project zero.

> Is this a version of extortion?

How is it extortion? Google does not create the vulnerabilities. It just validates them and makes the details public. It is a public service for everyone.


What are you blabbing about? Do you want Google now to fund the laziness of every software/firmware vendor on the planet?

No, but how about they pay for project they use?

Are the projects they use requiring licenses for commercial use?

Did the projects ask for vulnerability scanning from Google?

Did they ask Google to decide how quickly they need to fix reported vulnerabilities?

Same free will Google uses to decide to spam them with reports, they could use to exempt those fixes from the 3 per month limit in Google’s already existing vulnerability fix reward program.

They don’t _have to_. But then I am free to call them out on it.


I think you're confused. Google isn't paying other people to fix bugs in their own software. Google pays people to find bugs in Google software so that they can fix it. The same service they are providing to other software projects, for free, they pay individuals for because finding bugs in Google software helps Google to improve it.


> Did the projects ask for vulnerability scanning from Google?

Do projects ask hackers to hack them?

> Did they ask Google to decide how quickly they need to fix reported vulnerabilities?

It is irrelevant and this is the point you don't get: Google is not forcing anyone to do anything. They just say "I found this problem in your software, I am notifying you and in 30 days from now the whole world will know. Do what you wish with this information."

> They don’t _have to_. But then I am free to call them out on it.

It is the internet, do whatever makes you sleep better at night.


That’s being disingenuous.

What is the purpose of the message that Google sends if not to pressure the project to fix the issue? And why is Google doing this at all if not to pressure specific behavior?


You should ask Google.

I think Googke is doing the world a big service publishing vulnerabilities as soon as they are found. It would be even better if they publish working exploits too.


> Neither the users nor the vendors chose the 90/60/30 day limit.

Well, vendors can be more invested in building secure software and users get a lesson in why the "Check for updates" button exists in many devices' configuration options.

Google is not liable in any way for the vulnerabilities it finds.


Google is liable for their actions. In particular, Google is liable for choosing 90, 60 and 30 days waiting time.

What happens if a project has a vulnerability disclosure policy with a mandatory 90 day period, and Google ignores it starting 1.1.2027 and releases after 60 days?


>Google is liable for their actions

You might wish that, but in the US at least they literally are not. There is no "security bugs" exception to the First Amendment. Anyone who finds one is perfectly free to shout it to the world instantly, or never, or anything in between. There is no gray area or complexity here as a matter of law. As a matter of morals, it is quite complex, and only getting more so in the age of LLMs. It was always the case that knowing a bug existed will let operators do "something" whether there is a patch or not, even if that something is "shut off all network access until patched", and it was always the case that anything one party can discover somebody else could at any moment, or at any earlier point from release before the second discoverer. LLMs can tremendously accelerate the discovery angle and expand the parties likely to do it, and might also speed up patching even by users of the software vs the devs.

>What happens if a project has a vulnerability disclosure policy with a mandatory 90 day period, and Google ignores it starting 1.1.2027 and releases after 60 days?

They can apply any social or economic pressure they're able to, otherwise too bad for the project? They can set whatever policy they want, nobody else is under any obligation to follow it unless contractually obligated.


See but I do wonder if it would be less liable for them to literally shout it out instantly.

It’s not the vulnerability that is the problem, it’s the timeline.

That’s what the original article is about. The 90-60-30 limit is something Google actually chooses, and that is not a first amendment issue.

Imagine a research found a vulnerability in Google and said, “You have 90 days to transfer 1 000 000 to my account or I will make the vulnerability public”. Pretty sure that would be considered actual blackmail and would be illegal.

It’s kind of tricky to see where the line would be. Google is effectively saying “You have 90 days to fix this vulnerability, in the software we use to make billions, or we will make the vulnerability public”. It’s not a huge difference. At best, you could argue it’s two different departments: one that find vulnerabilities and the other that makes money from the project.


There’s a pretty big difference between saying “pay me hush money or I release this vulnerability” and saying “we found this vulnerability and we’re going to publicly disclose it in 30 days”.

>See but I do wonder if it would be less liable for them to literally shout it out instantly.

Wonder no more. They have zero liability either way.

>That’s what the original article is about. The 90-60-30 limit is something Google actually chooses, and that is not a first amendment issue.

Uh. Choosing time/place for speech is absolutely a 1A issue. Google (and you, me, and anyone else) is completely protected from legal action in how and when they make a unilateral decision to speak using their own resources.

>Imagine a research found a vulnerability in Google and said, “You have 90 days to transfer 1 000 000 to my account or I will make the vulnerability public”.

Yes, as you say that'd be blackmail but that's completely irrelevant to anything you have said or anything in this case. Google is not demanding money.

>It’s kind of tricky to see where the line would be.

No. It's not actually. Blackmail is extremely well defined in law and caselaw. No demand for anything? No blackmail.

>“You have 90 days to fix this vulnerability, in the software we use to make billions, or we will make the vulnerability public”. It’s not a huge difference.

Yes, it's a huge difference, even if you were being honest in your statement, which you aren't. Google doesn't have any "or we", they just say "when we find something, we've decided we'll generally try to let you know, and then at X time later we'll disclose it no matter what you do or don't do, so that then other mitigations can happen, unless we feel like doing differently." Which is 100% fine. Somebody can fix the vulnerability they introduced themselves, or not. Or they can try to get someone else to do it (depending on the project and whether Google cares, it might well be a Google engineer or LLM who offers a patch). Once it's out there, everyone else who uses said software can also try to patch or otherwise ameliorate it or move to something else, based on their own considerations, or not. That's just... normal society and market of ideas? And it doesn't make any difference is whether Google makes billions or zero dollars.


It would end a lot of disputes rather quickly.

8K or 16K from Mars. This is what I am hoping for.

Give it time. Maybe in the meantime new chemicals are discovered that make space flight cheaper. And new alloys to make the rocket lighter.

And who knows, maybe we discover The Expanse like reaction engines in a few decades.


You're speaking of advances well beyond the two magnitudes more we need. This is what I think most people don't get about the concept of full reuse. Those two orders of magnitude are theoretically viable with Starship!

Starship spends around $1 million fuel to send around 100 tons to orbit. That's a baseline cost of $10/kg. But if we get truly aspirational then fuel costs can be significantly reduced through greater vertical integration, and the later block models already are looking at bumping the payload up to 200 tons.

You obviously need some margin to account for maintenance after each flight, but the cost of the rocket itself rapidly amortizes to something near $0 with sufficient reuse. So something around $10/kg is a completely viable aspirational goal with current tech.

And if we get anywhere in the ballpark of that $10 then Starship is going to be at least a big of a revolution in space as LLMs were in the digital/cognitive world. Wild time to be alive!


I was reading in the comments that the rocket itself is made of steel. What if they manage to build it out of a lighter alloy that has the same or better properties when it comes to going and coming back from space?

What if, considering how SpaceX simplified rocket engine design figures out that, i don't know, adding a little bit of ammonia to the mix, makes the engines perform 10% better? Or 15%? Obviously not a rocket expert, but I don't think we (as a species) experimented with all the possible combinations of chemical compounds to get the best possible output to make a rocket get to space.

I us a lot of what IFs, because in the past few years we've made technological jumps that prior to that it would have taken us decades.

Indeed, wild time to be alive.


> I don't think we (as a species) experimented with all the possible combinations of chemical compounds to get the best possible output to make a rocket get to space.

What makes you think that? That's a nice thing to think but mostly comes out of ignorance of the field.


Because we don't know everything. We find out each day new things about chemistry, the universe and so on.

When it comes to rockets, yes, I have zero knowledge beyond the basic functioning of one. On the other hand, I look at how the Raptor engines were simplified to make them more reliable, with fewer failures and so on. And my gut says they are not yet with enhancing their performance and reliability.

I may not know much about chemistry, but, call me ignorant, I don't think we discovered all the combinations between elements in order to ignite something or make it go boom.

Like with fusion reactors, in theory they work, in practice we haven't figured out how to initiate a reaction and keep it stable "forever".

More progress will come, at a much faster rate than ever before.


Yeah that’s just wrong. For chemical propulsion we no exactly what sort of valence arrangement of electrons and mass of combustion exhaust products is optimal for getting the most acceleration for your reaction rate. It’s mostly because simpler is better (eg if pure hydrogen could be a combustion product it would he impossible to improve on that). More complex molecules will be strictly worse than anything we know about already. As you said yourself, you know nothing abour rockets or chemistry. Read the book everyone has been recommending.

That book explains the state of affairs at the time of writing.

You did not disprove my assumption we have not tested all the possible chemical combinations to make reaction better.

It is a very non-engineer stance of you to assume we now know everything about chemistry and that nothing new can be discovered.

Maybe we should ban chemical research going forward since there’s nothing new to learn and discover, no?


You are an imbecile.

Read “Ignition!” by John D Clark. The field of chemical propulsion is far more mature than you realise, there are no more basic ‘whatifs’ like your hypotheticals.

There's been a lot of experimenting with rocket fuels.

https://www.amazon.com/Ignition-Informal-Propellants-Univers...


What alloy would that be? Aluminum? Doesn't have the temperature tolerance. Titanium? Nightmarish to manufacture and expensive. Composites? Temperature intolerance and they tried it; not robust.

Stainless steel lets the structure get very hot on entry without failure, beyond the temperature where aluminum alloys would lose substantial strength. This reduces heat shielding requirements.


The sky is the limit really. The shape and design is sound so now you can test all sorts of options. Internal frames to buttress the structure. Mixed materials. Composites. You name it. Steel is super easy and cheap for prototypes but if you know you can get the ship back you can play with all sorts of variables.

They chose steel not because it was cheap (they initially chose CF) but because it was best for recovery and reuse. They are rocket engineers after all.

Not just because it was cheap, but cheapness certainly helped in its selection.

And then lots of startups will be able to afford to compete with starlink?

Starship built with new alloys and promises to deliver everything expected. I’m wondering what’s next for spacex beyond starship . It will take 5 years to squeeze all the possibilities from current design(s). What will be next 10x ?

Cheaper than methane and oxygen?

Had my first 3c509TX (I think that eas the suffix) sometime around ‘98 or ‘99. It was a luteral fortune back then for me.

But it worked until the other components in PC stopped working first.

Fond memories.


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

Search: