https://gunkies.org/index.php?action=history&feed=atom&title=32v_1m_crypt 2026-05-12T19:29:48Z Revision history for this page on the wiki MediaWiki 1.30.1 https://gunkies.org/w/index.php?title=32v_1m_crypt&diff=6947&oldid=prev 2009-10-26T13:37:17Z

<p>New page: CRYPT(1) UNIX Programmer&#039;s Manual CRYPT(1) == NAME == crypt - encode/decode == SYNOPSIS == crypt [ password ] == DESCRIPTION == _C_r_y_p_t reads ...</p> <p><b>New page</b></p><div>CRYPT(1) UNIX Programmer's Manual CRYPT(1)<br /> <br /> <br /> <br /> == NAME ==<br /> crypt - encode/decode<br /> <br /> == SYNOPSIS ==<br /> crypt [ password ]<br /> <br /> == DESCRIPTION ==<br /> _C_r_y_p_t reads from the standard input and writes on the stan-<br /> dard output. The _p_a_s_s_w_o_r_d is a key that selects a particu-<br /> lar transformation. If no _p_a_s_s_w_o_r_d is given, _c_r_y_p_t demands<br /> a key from the terminal and turns off printing while the key<br /> is being typed in. _C_r_y_p_t encrypts and decrypts with the<br /> same key:<br /> <br /> crypt key &lt;clear &gt;cypher<br /> crypt key &lt;cypher | pr<br /> <br /> will print the clear.<br /> <br /> Files encrypted by _c_r_y_p_t are compatible with those treated<br /> by the editor _e_d in encryption mode.<br /> <br /> The security of encrypted files depends on three factors:<br /> the fundamental method must be hard to solve; direct search<br /> of the key space must be infeasible; `sneak paths' by which<br /> keys or cleartext can become visible must be minimized.<br /> <br /> _C_r_y_p_t implements a one-rotor machine designed along the<br /> lines of the German Enigma, but with a 256-element rotor.<br /> Methods of attack on such machines are known, but not<br /> widely; moreover the amount of work required is likely to be<br /> large.<br /> <br /> The transformation of a key into the internal settings of<br /> the machine is deliberately designed to be expensive, i.e.<br /> to take a substantial fraction of a second to compute. How-<br /> ever, if keys are restricted to (say) three lower-case<br /> letters, then encrypted files can be read by expending only<br /> a substantial fraction of five minutes of machine time.<br /> <br /> Since the key is an argument to the _c_r_y_p_t command, it is<br /> potentially visible to users executing _p_s(1) or a deriva-<br /> tive. To minimize this possibility, _c_r_y_p_t takes care to<br /> destroy any record of the key immediately upon entry. No<br /> doubt the choice of keys and key security are the most<br /> vulnerable aspect of _c_r_y_p_t.<br /> <br /> == FILES ==<br /> /dev/tty for typed key<br /> <br /> == SEE ALSO ==<br /> [[32v 1m ed|ed(1)]], [[32v 8m makekey|makekey(8)]]<br /> <br /> == BUGS ==<br /> There is no warranty of merchantability nor any warranty of<br /> fitness for a particular purpose nor any other warranty,<br /> either express or implied, as to the accuracy of the<br /> enclosed materials or as to their suitability for any par-<br /> ticular purpose. Accordingly, Bell Telephone Laboratories<br /> assumes no responsibility for their use by the recipient.<br /> Further, Bell Laboratories assumes no obligation to furnish<br /> any assistance of any kind whatsoever, or to furnish any<br /> additional information or documentation.<br /> <br /> [[Category:32v man section 1]]</div>

Neozeed