this post was submitted on 01 Oct 2024
213 points (99.5% liked)
Privacy
31975 readers
387 users here now
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
- Don't promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
Chat rooms
-
[Matrix/Element]Dead
much thanks to @gary_host_laptop for the logo design :)
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
There was a previous article on this with more explanation that I'm struggling to find.
The gist was that they do hash all passwords stored, the problem was that there was a mistake made with the internal tool they use to do that hashing which led to the passwords inadvertently going into some log system.
Makes sense now, thank you
"mistake"
I call BS. The reviews I've gone through for trivial stuff would've exposed this.
This was intentional.
Hanlon's Razor revised: Never attribute to malice what can be attributed to incompetence, except where there is an established pattern of malice.
Then incompetence at a level that's incomprehensible.
A code review certainly exposed this, and some manager signed off on the risk.
Again, changes I make are trivial in comparison, and our code/risk reviews would've exposed this in no time.
Yeah, cause trivial systems are a lot easier to parse and review. At a base level that's nonsense logic.
My point being the extensiveness of a review process.
The more important a system, the more people it impacts, etc, the more extensive the review process.
Someone chose to ignore this risk. That's intentional.
You quite frankly, don't know what happened and if you're confident it's intentional, all that says is that you're a grump who likes to complain.
A mistake doesn't mean it's an accident. A mistake means they made the wrong choice.
Never assume malice when something can be explained by stupidity
I generally agree.
But any decent code review process would've exposed this, or at least a data surveillance system that checks this stuff. I've received a few notifications about my logs storing inappropriate data, as a result of a scanning system.
Some manager knew about this during a code review, and signed off on the risk because it was only in-house.