Well, they are actually not that different. Any block cipher (like AES) can easily be used as a hashing algorithm (using the last block as the "digest") with fixed key/IV. It can be used as a MAC the same way by varying the key.
Hashing algorithms can as well be used as stream ciphers. Since they have the property that they are "cryptographically secure" - ie. their output could as well have been random for all you care - they can be used to create a stream of pseudo-random bytes that you can XOR your message with.
The real difference between hashing algorithms and "real" two-way encryption is efficiency! Hashing algorithms are also commonly called one-way encryption schemes.
Re:Yeah..all that awesome 'peer reviewed' code...
on
Too Cool For Secure Code?
·
· Score: 2, Informative
Try Aleph1's excellent article from phrack.org: http://www.phrack.org/phrack/49/P49-1 4
libgnome* version 2.2 does not work with gtk+ 2.0 as seen in this thread: http://mail.gnome.org/archives/gtk-devel-list/2003 -January/msg00018.html.
It might be one of the reasons for bumping it.
Or Microsoft don't release them in a timely fashion.
Or Adobe does not. Flash and PDF exploits still tops the list.
Well, they are actually not that different. Any block cipher (like AES) can easily be used as a hashing algorithm (using the last block as the "digest") with fixed key/IV. It can be used as a MAC the same way by varying the key.
Hashing algorithms can as well be used as stream ciphers. Since they have the property that they are "cryptographically secure" - ie. their output could as well have been random for all you care - they can be used to create a stream of pseudo-random bytes that you can XOR your message with.
The real difference between hashing algorithms and "real" two-way encryption is efficiency! Hashing algorithms are also commonly called one-way encryption schemes.
Try Aleph1's excellent article from phrack.org:1 4
http://www.phrack.org/phrack/49/P49-
libgnome* version 2.2 does not work with gtk+ 2.0 as seen in this thread: http://mail.gnome.org/archives/gtk-devel-list/2003 -January/msg00018.html.
It might be one of the reasons for bumping it.