News for hackers. Stuff that matters.
Re:Plex Security Incident by mvdtnz on Monday September 08, 2025 @06:58PM (#45175211)
For all practical purposes what you're saying is just wrong.
Re:Plex Security Incident by Someone1234 on Monday September 08, 2025 @07:54PM (#45175676)
I've done so within the last year, successfully. Cost $7 for a single password in just compute and took about 17 hours (lowest, cheapest priority).

So please explain your reply further. Also recall their claim for context of what I was replying to, and what you're here defending now.

If their claim is credible what I did and what you're reiterating wasn't possible.

Re:Plex Security Incident by mvdtnz on Monday September 08, 2025 @07:57PM (#45175698)
No you haven't, not for a reasonably strong password.
Re:Plex Security Incident by 0points on Tuesday September 09, 2025 @03:48AM (#45178824)
You brute forced a random argon2 hashed password using cheap compute in 17 hours?

Granted the suggested defaults for argon2 is like ~0.1 second per verification on a rather beefy CPU, in 17h that's about 620 000 guesses.

Your cheap compute would likely perform worse.

That is beyond improbable. You are making it up.

Re:Plex Security Incident by IAmBroom on Tuesday September 09, 2025 @11:17AM (#45183134)
Your story lacks important context. Was the password "password"? "123456"? Or a 12-character mix of cases, numbers, and special characters?