3 ms·
Here is what I do: require 'digest/sha1' puts "doubly troubly" thing = gets.chomp base = Digest::SHA1.hexdigest(Digest::SHA1.hexdigest(thing)) puts b
by 3pt14159 16y ago
Here is what I do:
require 'digest/sha1'
puts "doubly troubly"
thing = gets.chomp
base = Digest::SHA1.hexdigest(Digest::SHA1.hexdigest(thing))
puts base
puts base[0..3] + "^!!^E" + base[4..-1]
puts base[0..3] + "^!!^E" + base[4..6]
puts base[0..3] + "^!!^E"
For any site I input the domain (so "zach.tumblr.com" + my_salt would be inputed) then I copy one of the four outputs based on what security level I think the site deserves. THEN (and most critically) I add a password that rotates key characters based on factor X of the site. Think about this like a normal password, but it changes.
I then expose this little piece of code on every one of my computers as well as on a protected server that lives only on an IP.
I 100% agree with this article, but I have my own system and it works well.
- eli 16y agoYou might as well switch that to a proper HMAC. Check out HMAC::SHA1.digest
- decklin 16y agoIndeed. I rolled my own UI for doing this with HMAC because everything else seemed to be implemented with cargo-cult voodoo (I just read the SuperGenPass FAQ again to check... MD5 10 times? WTF? If 1 is not enough why are you using it? No personal offense meant to whoever wrote SuperGenPass, but it's not what I wanted. As for the parent comment... I don't know what to say). Shameless self-promotion link, if interested: https://chrome.google.com/extensions/detail/mjafhhefmkfchamfkcegnafkpjohcllp https://chrome.google.com/extensions/detail/mjafhhefmkfchamf...