Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-Id: <5.1.0.14.2.20020404031530.00b05010@imap.local.mscha.org>
X-Sender: ml AT imap DOT local DOT mscha DOT org (Unverified)
Date: Thu, 04 Apr 2002 03:21:14 +0200
To: cygwin AT cygwin DOT com
From: Michael Schaap <cygwin AT mscha DOT org>
Subject: RE: mcrypt commnad
In-Reply-To: <657B20E93E93D4118F9700D0B73CE3EA0D39721A@goofy.epylon.lan>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 00:21 4-4-2002, Gupta, Sanjay wrote:
>My answer :- As I recall the crypt command in all Unix works the same way

You actually worked with "all Unix"?  Wow!  That's impressive!

>e.g. if I want to encrypt a file, I would use
>crypt crypt_password < file_you_want_to_encrypt > encrypted_file
>
>and to decrypt file, you would issue command
>crypt crypt_password encrypted_file
>
>but the same thing does not work in cygwin. The purpose of crypt command in
>cygwin is different than the purpose of crypt command in unix. I have no
>idea why it is different but it is.

On my copy of RedHat 7.1, crypt behaves as follows:

         $ crypt
         bash: crypt: command not found

Please update Cygwin ASAP so that it behaves the same!!!

  - Michael  ;-)

-- 
     I always wondered about the meaning of life.   So I looked it
     up in the dictionary under "L" and there it was - the meaning
     of life.  It was not what I expected.                  - Dogbert 


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/