You should verify your facts before repeating provably false information.
3,137 karma · joined December 3, 2009
You should verify your facts before repeating provably false information.
Disclaimer: works at Google, maintains some FOSS code in my own time, both under my own copyright for some projects and under Google's copyright for others.
Of course it's usually going to be somewhere in the middle. But not everyone lives in the Bay Area where you can hop between jobs and change employer every week.
The coach probably didn't even take a wrong decision based on the information available at the time (it isn't rain season yet).
tl;dr: a non-profit got fined 75K€ because their website leaked 42,562 private documents from their users. Anyone could modify numbers in the URL and read other users' documents. The documents included passports, tax information, identity documents, and more.
EDIT: better source: https://www.cnil.fr/fr/sanction-de-75-000-euros-pour-une-att...
> “We understand if this is disturbing -- it is designed to be. This is a thought-experiment by the Design team from years ago that uses a technique known as ‘speculative design’ to explore uncomfortable ideas and concepts in order to provoke discussion and debate. It’s not related to any current or future products.”
So the answer seems to be "nobody".
If you're willing to believe that the service matches the published source code, why wouldn't you also be willing to believe that the service matches the published "specifications" (e.g. privacy policy)?
> We don't correlate or combine information from our temporary or permanent logs with any personal information that you have provided Google for other services.
Of course, all of that is meaningless if you want to think that Google is lying in its privacy policies.
(Disclaimer: I work at Google, but not on 8888).
Do you have any public source detailing this or do you just make this claim based on your own assumptions?
(Disclaimer: I work at Google but have no idea how our self-driving cars work.)
To me is seems that this feature of browsers is really only meant as a protection against non-advanced attackers accessing an unlocked computer. For this scenario, having a stronger hash would do nothing.
Having a stronger hash would mitigate against exfiltration off the device by malware, but if malware can exfiltrate files off your device it's very likely they can e.g. read your passwords from memory, or keylog until the next time you input the password. It would also mitigate against someone being able to dump your password db off your filesystem if they get physical access to your computer, but full disk encryption does that better, and also protects all the rest of your personal data that's stored on the device.
Historically this is why Chrom{e,ium} has been resisting introducing this feature. Its uses are very limited against "real" attackers.
Mozilla spending time on cool tech rather than dumb migrations between password schemes that provide no value seems like a good tradeoff.
I think this is just coincidence though. Apple most likely performs their own layer of encryption on top of what Google already does.
They protect against two different attack scenarios: Google doesn't want plaintext data to show up on disks. Apple doesn't want plaintext data to be accessible by anyone at Google (or any other 3rd party provider).
Anonymous reporting in Chrome has been one of the leading use cases for differential privacy at Google. See e.g. https://github.com/google/rappor and https://static.googleusercontent.com/media/research.google.c... which specifically mentions the Chrome use case. This seems to indicate the people who work on this do care at least in some amount about privacy.
(Given the fact that you use a throwaway account I'm very much not expecting to see anything else than FUD, but hey, I'll give you the benefit of the doubt.)
Bugs and errata can be a concern (I think I remember some issues regarding PowerPC atomic instructions misbehaving on the Wii U for example) but I would expect them to be fairly minor compared to the whole work of REing a custom microkernel and its associated services.
Do you have any source for this statement?