home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.update.uu.se
/
ftp.update.uu.se.2014.03.zip
/
ftp.update.uu.se
/
pub
/
rainbow
/
msdos
/
misc
/
lucifer.lzh
/
LUCIFER.DOC
next >
Wrap
Text File
|
1986-02-14
|
2KB
|
34 lines
***************************** lucifer **************************
* LUCIFER: encrypt/decrypt bytes using IBM's LUCIFER algorithm.
* Programmed by R.W.Outerbridge
*
* Usage: lucifer (+|-)([ecb]|<cbc|cks>) key1 <ivec>
* EN/DE MODES KEYS
*
* + : ENcrypt (default if MODE specified)
* - : DEcrypt (presumes encrypted input)
*
* Modes of Operation (choose ONE):
*
* ecb : (default) Electronic Code Book. Only uses one key.
* If simply "+" or "-" is specified, ecb is used.
* cbc : Cipher Block Chaining. Uses two keys.
* cks : ChecKSum. Generates a 128-bit checksum using two keys.
*
* Both keys may be as long as you wish. The practical limit
* on keylength is the size of your system's argument buffer.
* WARNING: on some machines all arguments become CAPITALS.
* WARNING: non-ascii machines MAY get different results.
*
* Any character may be used in keys - depending on the O/S -
* except ASCII NULL (0x00). The one-letter key '#', when used
* for "key1", will cause lucifer to use a preset default key
* (for verification and testing). Failing to specify "ivec", if
* required, will result in "key1" being used for both keys. It
* is an error to omit "key1". There is no provision for giving
* arbitrary, absolute, bit-valued keys.
*
* As painful as they are to use, long keys are MUCH safer;
* think up nonsense phrases you can safely remember.
*