By now I assume that any service where I've registered for an account is being actively targeted and that any organisation that's not a Google, Microsoft or the likes has already been breached. MFA is your friend, and even plain vanilla SMS based MFA is better than just a username and password for authentication. I've enabled hardware based MFA anywhere it's supported. 15-20 years ago it was fun to sign up for dozens…
Opensubtitles.org breached – Email addresses, IP addresses, Passwords, Usernames
111–120 of 194 posts
Re: Opensubtitles.org breached – Email addresses, IP addresses, Passwords, Usernames
#112Earlier quoted context omitted.
> Opensubtitles became really frustrating to use once they began asking for a login and a password to download subtitles in VLC or Xbmc/kodi (basically every time you need to use the API). This was actually optional, and always was. I think the issue was that they had made some changes in the backend, but the addons didn't update the code to accommodate. At least this was the case for Kodi. The opensubtitles addon ha…
Can you name a few please?
anonymous, scrapes a handful of sites including opensubtitles + subscene
Re: Opensubtitles.org breached – Email addresses, IP addresses, Passwords, Usernames
#113Earlier quoted context omitted.
$1 / 1000 visitor is $110k / month with 11 million visitors which agrees with my estimation.
You want to double check your math there?
Re: Opensubtitles.org breached – Email addresses, IP addresses, Passwords, Usernames
#114Earlier quoted context omitted.
> to prevent super long passwords from eating up CPU time Is that why websites sometimes have low maximum password length requirements ? Ex: must be less than 20 characters.
Super long is >100 character passwords. Not much point: either the hash function is broken or some other hack will happen before humanity develops enough compute power to crack 100 char bcrypt passwords. Websites (like some banks used to) that have less-than 20 char limits for passwords are purely bad security strategy.
I've run across that at least once and it was a total pain to troubleshoot and figure out.
Re: Opensubtitles.org breached – Email addresses, IP addresses, Passwords, Usernames
#115I've seen a lot of people on HN talk about how they never store passwords because they don't want the liability, and I've seen some talk about how they do since it's simple. In my experience, hashing with Argon2 and keeping that in the DB (for toy personal projects) has been very easy, especially to how scary keeping passwords seems to have been made.
I guess my real question is: If I'm hashing with an actual password acceptable hash method (salt and all), is there any reason I shouldn't still do this? I'm legitimately interested, because for all I know, I'm experiencing the Dunning-Kruger effect.
Re: Opensubtitles.org breached – Email addresses, IP addresses, Passwords, Usernames
#116Earlier quoted context omitted.
Defense against rainbow tables is obtained via salt, not via slow hashes. A rainbow table is a space-time tradeoff (you give space, and you get time), so using a slow hash only "encourages" (for lack of me knowing a better word) creating rainbow tables. Adding long salts on the other hand requires the attacker to create an infeasible number of rainbow tables (one for each possible value of the salt).
Where do you store the salt?
Re: Opensubtitles.org breached – Email addresses, IP addresses, Passwords, Usernames
#117A tip I learned recently: if you see a database with a simple hash with no salt(md5, sha256…) like this, and you want to migrate to a secure password hashing function (bcrypt, argon2…) you don't need to wait for the users to re-login: simply do bcrypt(md5(password)) immediately, and delete the old hashes, and you get higher security.
> simply do bcrypt(md5(password)) This could also be problematic. Password Shucking https://www.youtube.com/watch?v=OQD3qDYMyYQ
https://security.stackexchange.com/questions/234794/is-bcryp...
Re: Opensubtitles.org breached – Email addresses, IP addresses, Passwords, Usernames
#118> The site was created in 2006 with little knowledge of security, so passwords were stored in md5() hashes without salt Ouch! I hope they learned their lesson: Security is an ongoing effort.
for 2006 that's actually not bad. When I joined my first company in 2010, to my horror, they were using plain text passwords for users
Re: Opensubtitles.org breached – Email addresses, IP addresses, Passwords, Usernames
#119Which is why I use password manager, with one unique & strong password per site. Risk management is important as there is no way to know what website has any known or unknown security holes in it. (Especially those built years ago) When possible use password manager with End to End Encryption (E2EE). Maybe Independent Security Audit too.
Well, for this kind of negligible importance website risk management is simple : just use a variation on "password for opensubtitles" as a password (and maybe even have it saved by your browser). (If like me, you find the idea of a password manager not acceptable.)
Re: Opensubtitles.org breached – Email addresses, IP addresses, Passwords, Usernames
#120(paraphrasing) "We were stupid 15 years ago and have been lazy ever since" is a slap to the face.
Maybe they should have done something about their platform instead of watching anime with subtitles.
Those people should have their internet privileges permanently removed and the whole site should be burned in a dumpster like the dumpsterfire of security they had running for fucking 15 years.