Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Fri, 6 Jun 2003 14:53:13 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: openssl commandline tools always output in text mode Message-ID: <20030606125313.GN875@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <3EE07B19 DOT 9080707 AT fillmore-labs DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3EE07B19.9080707@fillmore-labs.com> User-Agent: Mutt/1.4.1i On Fri, Jun 06, 2003 at 01:29:29PM +0200, Patrick Eisenacher wrote: > Hello Corinna, > > attached you find the output of cygcheck. Nothing enlightening, unfortunately. > Did you try the example I provided in my last posting? No, I don't have keys and that stuff to test with. What I did was, to examine the source code of OpenSSL. The OpenSSL tools do open input files generally in binary mode while writing sometimes in binary mode, sometimes in the "don't care" mode. If your input file contains CRLFs, the output file might contain them untranslated. Is that possible here? Are your input files "infected" with CRLFs? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/