@jubes Another reason to : 100 million debit/credit card users leaked from Amazon's credit card processor (who foolishly used AWS to store the data):

@resist1984 @jubes According to the article most of the actual card info was hashed; here's hoping they didn't use MD5 or something...

@gerowen @jubes i guess the critical question is how much of it was hashed. If just 4 digits were hashed, it would be trivial to hash and compare 10,000 combinations.

Follow

@jubes @gerowen i'm assuming all hashes are designed to be fast and simple to compute.. at least, I've not heard of hashes that are deliberately computationally slow.

@resist1984 @jubes @gerowen bcrypt, for instance, is designed to be slow ("bcrypt is an adaptive function: over time, the iteration count can be increased to make it slower", en.m.wikipedia.org/wiki/Bcrypt ). So are proof of work functions.

Sign in to participate in the conversation
Mastodon 🔐 privacytools.io

Fast, secure and up-to-date instance. PrivacyTools provides knowledge and tools to protect your privacy against global mass surveillance.

Website: privacytools.io
Matrix Chat: chat.privacytools.io
Support us on OpenCollective, many contributions are tax deductible!