Thread View: sci.crypt
1 messages
1 total messages
Started by Sam Hulick
Tue, 29 Sep 1992 21:19
One-way encryption...HOW?
Author: Sam Hulick
Date: Tue, 29 Sep 1992 21:19
Date: Tue, 29 Sep 1992 21:19
19 lines
1761 bytes
1761 bytes
Yes.. I admit, I'm new to the science of encryption, but I'm curious: How can there exist such a thing as "one-way" encryption (e.g. DES, UNIX crypt)? Can't ALL algorithms have a "nemesis?" For instance, take a very simple algorithm to encrypt a single character. newchar = char * 38 - 200. After so many guesses, that algorithm can be cracked and reversed. What makes UNIX password encryption so complex? I understand a little of it, e.g. an encrypted passwd consists of 13 chars, 2 of which are the salt, the rest is the actual password. The salt determines how the password will be interpreted, correct? But that can't be true, if UNIX encryption is "one-way." The encrypted password is never interpreted, it's the inputted password that is ENcrypted and compared to the real encrypted password. Could someone briefly explain how this works, or email me some kind of already-made documentation by UNIX? Source code for UNIX encryption would also be appreciated. Thanks. -- Sam Hulick | "The worst sin towards our fellow creatures is not to shulick@indiana.edu | hate them, but to be indifferent to them: that's the (NeXTmail welcome) | essence of inhumanity." --George Bernard Shaw
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads