There's crypt(1) and there's crypt(3). I am referring to crypt(1) i.e. the shell command, viz:
User Commands                                            crypt(1)

NAME
     crypt - encode or decode a file

SYNOPSIS
     crypt [ password ]

DESCRIPTION
     crypt encrypts and decrypts the contents of  a  file.  crypt
     reads  from  the  standard  input and writes on the standard
     output.  The password is a key  that  selects  a  particular
     transformation.   If  no  password is given, crypt demands a
     key from the terminal and turns off printing while  the  key
     is being typed in. crypt encrypts and decrypts with the same
     key:

          example% crypt key<clear.file> encrypted.file
          example% crypt key<encrypted.file | pr

     will print the contents of  clear.file.

     Files encrypted by crypt are compatible with  those  treated
     by the editors ed(1), ex(1), and vi(1) in encryption mode.

     The security of encrypted files depends  on  three  factors:
     the  fundamental method must be hard to solve; direct search
     of the key space must be infeasible; "sneak paths" by  which
     keys or cleartext can become visible must be minimized.

     crypt implements a  one-rotor  machine  designed  along  the
     lines  of  the  German Enigma, but with a 256-element rotor.
     Methods of attack on such machines are  widely  known,  thus
     crypt provides minimal security.

     The transformation of a key into the  internal  settings  of
     the  machine  is deliberately designed to be expensive, that
     is, to take a substantial fraction of a second  to  compute.
     However,  if  keys  are restricted to (say) three lower-case
     letters, then encrypted files can be read by expending  only
     a substantial fraction of five minutes of machine time.

     Since the key is an argument to the  crypt  command,  it  is
     potentially visible to users executing ps(1) or a derivative
     command.  To minimize this possibility, crypt takes care  to
     destroy  any  record  of the key immediately upon entry.  No
     doubt the choice of keys  and  key  security  are  the  most
     vulnerable aspect of crypt.

FILES
     /dev/tty
           for typed key

--
I'm Not Just Another Perl Hacker


In reply to Re^2: How to decrypt a file encrypted with vi -x or shell crypt by rinceWind
in thread How to decrypt a file encrypted with vi -x or shell crypt by rinceWind

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.