john -format=crypt -wordlist=various.dic -session=test2 -rules t est2 Many salts: 7128 c/s real, 6923 c/s virtual john -format=crypt -wordlist=various.dic -session=test2 -rules test2 Only one salt: 7128 c/s real, 6923 c/s virtual Many salts: 7152 c/s real, 6948 c/s virtual
SHA512 CRYPT3 PASSWORD
Loaded 5 password hashes with 5 different salts (generic crypt(3) ) john -format=crypt -wordlist=various.dic -session=test2 -rules test2
Many salts: 8108 c/s real, 8188 c/s virtual Why such a hudge difference between the test and actual?īenchmarking: generic crypt(3). Is the sha512 hash, or something else, to blame on this poor performance? Well, maybe just two builds, since omp4 and omp7 performed about the same. See, the performance I experienced below for three different builds. Secondly, I'm very surprised at how slow my real world run is, compared to the performance test. Not too long ago, it believe it was worked as format=sha512, or sha, or something like that. (I don't know what the definition of RAW SHA512 is) My Solaris builds were compilied with the latest version of gcc, version 4.6.1 and latest version of opensll, version 1.0.0d.įirst, I was surprised that the sha512 passwords are worked as format=crypt (hash encoding string length 98, type id $6), and not format=raw-sha512. If anyone knows of a version of Linux that supports sha512 hashes, please reply to this message and let me know.
SHA512 CRYPT3 WINDOWS
This same test can't be performed on the Windows build, Linux build on Suse, Linux build on Owl, since it doesn't support the sha512 format. I compiled JtR on Solaris and ran it against some Sha512 password hashes. To: Terrible performance of sha512 (crypt) hash audit on/for Solaris Hash Suite - Windows password security audit tool. each do | a, b, c | v = final >= 6 end end v = final 2. Rearranged = " " if defined? ( " has_ord? ". digest end # This is the bit that uses to64() in the original code.
SHA512 CRYPT3 UPDATE
update ( password ) end if ( i & 1 ) != 0 m2. update ( salt ) end if ( i % 7 ) != 0 m2. update ( final ) end if ( i % 3 ) != 0 m2.
digest # and now, just to make sure things don't run too fastġ000. # Also really broken, as far as I can tell. Also I changed the 1 to the 6, since the manpage of crypt says that this would create an SHA512 hash. I have pretty much copied the examplecode from the GNU, even though I know the salt calculation isnt very good. update ( password + magic + salt ) # Then just as many characters of the MD5(pw,salt,pw) As the title is saying I want to implement a simple Sha512 encryption with the C function crypt (3). upcase ) # The password first, since that is what is most unknown. crypt ( password, algo = :md5, salt = nil, magic = ' $1$ ' ) salt ||= generate_salt ( 8 ) case algo when :md5 require " digest/md5 " when :sha1 require " digest/sha1 " when :rmd160 require " digest/rmd160 " when :sha256, :sha384, :sha512 require " digest/sha2 " else raise ( ArgumentError, " unknown algorithm " ) end digest_class = Digest. # File 'lib/crypt3.rb', line 50 def self.
0 kommentar(er)
