58 karma · joined May 28, 2013
find . -name '*.<ext>' | xargs wc -l The two most common methods, md5 and sha-1 are
both susceptible to collisions, or birthday attacks.
As of writing this, I would recommend using
SHA-3-256 which has no known attacks.
Don't do that. Hashing algorithms without salt and iteration counts is a bad idea. Thankfully, languages and frameworks are starting to take this responsibility away from the programmer (or at least they're making it easier) – consider using has_secure_password in Rails, password_hash in PHP 5.5, etc. Don't use standard hashing algorithms. user.failed_login: Originated from 139.194.122.85 9 hours ago
user.failed_login: Originated from 201.210.254.161 11 hours ago
user.failed_login: Originated from 201.248.24.177 a day ago
user.failed_login: Originated from 183.89.77.84 a day ago
user.failed_login: Originated from 201.211.14.251 a day ago* Main focus: Transactional and marketing SMS application, it's a little boring and lots of companies do it, but none are truly self-service, and none make it super-easy.
* Back burner: Digital asset management, again it's done by many companies already, but there UIs are mostly upload, tag and try to retrieve. I have a background in AI (B.Sc) and I want to make it a little smarter than what's currently out there, with uploads that detect previous revisions of digital assets, etc – finally putting to an end file naming conventions such as x_final.ai, x_final_2.ai, x_final_final.psd (something I have seen used by every company I have worked for.)
* And later: I'm into brewing beer, and I have been working on recipes for a few years – Ambition is to make enough money to survive with the two projects above, and to begin investing in building a microbrewery and brew pub.