532 karma · joined June 12, 2017
This really seems like the recurring bubble where posters on HN somehow things that a large majority of the industry is hitting F5 on HN while they are instead busy doing actual work.
For _any_ database there will be important information only available in the documentation.
So if I have 1 machine and increase from 2 to 256 core the throughout will scale linearly without the SSD ever being a bottleneck?
What issue are we even talking about?
This company (is there a company behind it, I couldn't find those details) markets to countries outside of Israel I assume.
(If these companies signed up for the service then or course it would be legal to claim that.)
> Sustainable aviation fuel can be made from any of 60 different feedstocks — among them plant oils, algae, greases, fats, waste streams, alcohols, sugars, captured CO2 and other alternative feedstock sources and processes. The Department of Energy estimates that the United States alone has the resources to produce 50–60 billion gallons of SAF per year.
As I understand it:
According to the source, Google inserts unique user ID is into database name. An attacker can make a request to Google, pass in this unique user ID into their API and get profile details, for example a photo back.
The attacker does not need access to the database data, only the database name, since the user ID is embedded in the _name_.
You are right it's a leak of a database name, but Google store sensitive data in the database name.
* Connecting from my own IP with wrong password: It tells me to "Check my master password and try again."
* Connecting from another IP with wrong password: It tells me to "Check your inbox for an email from LastPass: <myemail**@gmail.com>" and also to check my login info.
It's a bit odd that it tells me to check my email even though the master password I provided was incorrect.
> Did the malware wait for me to open my keepass vault and snoop the password then?
It's not impossible at least. There's been vulnerabilities in Keepass RPC which allowed any javascripts on Internet reading your passwords [1]. If a simple javascript can read secrets from keepass, I would not be at all surprised if that has happened.
> the less probable it is that we were all hit with the same malware.
Sure. But there's also some selection bias here, were a lot of people visiting hackernews is affected. On twitter, everyone (more or less) who's discussing this issue links this post, which at least in theory could indicate that the scope of the issue is relatively narrow (compared to the entire internet). It could be that some specific developer tools or libraries have been affected for example (as any of the recent packages on NPM which people claim may have sniffed credentials).
1: https://forum.kee.pm/t/a-critical-security-update-for-keepas...
Or could it be that all of you guys are using the same router, same ISP, same anything-else, which has snooped on traffic and collected the credential?
I'm still seeing hackers trying to log on using passwords I haven't used in ~10 years, because it's on a list somewhere.
Only on hackernews I see this level of crazyness. You need to reduce your caffein intake drastically.
Your reasoning is like saying Red Cross isn't designed to reduce the suffering of people because there are still suffering people. It's an odd claim to make.