Re: OpenSSL 3.0.14

FOPPE, JEFFERY B CIV USAF AFMC AFLCMC/WFRQ via Cygwin writes: > Is the OpenSSL 3.0.14 package going to be released soon? You should ask that question upstream first. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ DIY Stuff: http://Synth.Stromeko.net/DIY

Re: OpenSSL failure in Cygwin: SSL_set_tlsext_host_name returns 1 (SSL_TLSEXT_ERR_ALERT_WARNING)

Greetings, Yuri! > I've built the proxytunnel project in Cygwin > (https://github.com/proxytunnel/proxytunnel). > It is usually used to tunnel ssh through https using the https CONNECT > command. > The command "proxytunnel --no-check-certificate -E -p > {https-proxy-host}:{https-proxy-port} -d

[ANNOUNCEMENT] Re: openssl 1.1.1u-1, mingw64-{i686, x86_64}-openssl-1.1.1u-0.2 (security)

[…] Please disregard, this was sent before I finished editing it. -- *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address speci

Re: OpenSSL failure in Cygwin: SSL_set_tlsext_host_name returns 1 (SSL_TLSEXT_ERR_ALERT_WARNING)

On 5/8/23 10:40, Achim Gratz via Cygwin wrote: The port might not be open in the standard configuration of the Windows firewall. Maybe you can use either openssl or curl to check what happens when you are trying to connect. It looks like this function is used incorrectly, and it actually suc

Re: OpenSSL failure in Cygwin: SSL_set_tlsext_host_name returns 1 (SSL_TLSEXT_ERR_ALERT_WARNING)

Yuri via Cygwin writes: > The command "proxytunnel --no-check-certificate -E -p > {https-proxy-host}:{https-proxy-port} -d 127.0.0.1:22" works on Linux > and BSD. > > However, it fails in Cygwin with the exit code 1 > (SSL_TLSEXT_ERR_ALERT_WARNING), which causes this error message in > proxytunnel:

Re: OpenSSL failure in Cygwin: SSL_set_tlsext_host_name returns 1 (SSL_TLSEXT_ERR_ALERT_WARNING)

On 5/8/23 08:31, Brian Inglis wrote: Which Cygwin, ssl/tls-devel libraries, and ca-certificates... packages and versions are you using? libssl-devel-1.1.1t-1 openssl-1.1.1t-1 ca-certificates-2021.2.60-1 $ man SSL_set_tlsext_host_name says SSL_set_tlsext_host_name etc. returns 1 for s

Re: OpenSSL failure in Cygwin: SSL_set_tlsext_host_name returns 1 (SSL_TLSEXT_ERR_ALERT_WARNING)

On 2023-05-08 01:31, Yuri via Cygwin wrote: I've built the proxytunnel project in Cygwin (https://github.com/proxytunnel/proxytunnel). It is usually used to tunnel ssh through https using the https CONNECT command. The command "proxytunnel --no-check-certificate -E -p {https-proxy-host}:{https-

Re: OpenSSL v3

Greetings, Achim Gratz! > Andrey Repin writes: >> Is there a chance to update OpenSSL to v3? It has a number of improvements >> and >> bug fixes I'd like to use. > It also has a number of incompatibilities with the previous version(s). Meaning they can't be installed in parallel? > I am not su

Re: OpenSSL v3

Andrey Repin writes: > Is there a chance to update OpenSSL to v3? It has a number of improvements and > bug fixes I'd like to use. It also has a number of incompatibilities with the previous version(s). I am not sure yet how to deal with the packaging problems that is going to create. Regards, A

Re: OpenSSL

On 2021-01-04 08:11, Marco Atzeri via Cygwin wrote: On 04.01.2021 13:21, tommie.k...@alverservices.com wrote: But im struggling to see how I can upgrade openssl >1.1.1f Compliance checks state that we must have a more up to date version, I know that it exists (1.1.1g, 1.1.1h, 1.1.1i) https://c

Re: OpenSSL

On 04.01.2021 13:21, tommie.k...@alverservices.com wrote: Hey, sorry if this is the wrong place. Hi Tommie, this is the right place. But im struggling to see how I can upgrade openssl >1.1.1f Compliance checks state that we must have a more up to date version, I know that it exists (1.1

RE: OpenSSL

> Am 08.04.2020 um 11:30 schrieb Tommie King: > > Hey, sorry if this is the wrong place. > > Hi Tommie, > right place > > > But im struggling to see how I can upgrade openssl >1.1.1d > > > > Compliance checks state that we must have a more up to date version, I > > know that it exists (1.1.1f) > >

Re: OpenSSL

Am 08.04.2020 um 11:30 schrieb Tommie King: Hey, sorry if this is the wrong place. Hi Tommie, right place But im struggling to see how I can upgrade openssl >1.1.1d Compliance checks state that we must have a more up to date version, I know that it exists (1.1.1f) that was released just 2

Re: OpenSSL 1.1.1d/1.0.2t Availability

On Fri, 2019-09-13 at 14:25 +, D'Ambra, Nikki M wrote: > Now that the latest versions of openssl, versions 1.1.1d and 1.0.2t, are > available > to the public, are there plans, or an ETA, to make these openssl packages > available > to the cygwin community? Of course there are, but it hasn'

Re: OpenSSL 1.0.2t Availability

On 2019-08-22 12:03, Yaakov Selkowitz wrote: > On Thu, 2019-08-22 at 14:31 +, D'Ambra, Nikki M [US] (MS) (Contr) > wrote: >> Are there plans to make the openssl 1.0.2t package available to the cygwin >> community? > > 1.0.2t has yet to be released upstream. ...and no plans currently as the on

Re: OpenSSL 1.0.2t Availability

On Thu, 2019-08-22 at 14:31 +, D'Ambra, Nikki M [US] (MS) (Contr) wrote: > Are there plans to make the openssl 1.0.2t package available to the cygwin > community? 1.0.2t has yet to be released upstream. -- Yaakov -- Problem reports: http://cygwin.com/problems.html FAQ:

Re: openssl-devel in openssh README

Greetings, Sorin Adrian Savu! >> Greetings, Sorin Adrian Savu! >> >> > Hello! >> >> > I had to compile openssh recently, and the README for cygwin is >> referencing >> > openssl-devel package which is obsolete now. I spent some time trying to >> > figure this out. Can you please update >> > >> htt

Re: openssl-devel in openssh README

On Sun, May 26, 2019 at 10:50 AM Andrey Repin wrote: > Greetings, Sorin Adrian Savu! > > > Hello! > > > I had to compile openssh recently, and the README for cygwin is > referencing > > openssl-devel package which is obsolete now. I spent some time trying to > > figure this out. Can you please up

Re: openssl-devel in openssh README

On 2019-05-26 00:19, Sorin Adrian Savu wrote: > I had to compile openssh recently, and the README for cygwin is referencing > openssl-devel package which is obsolete now. I spent some time trying to > figure this out. Can you please update > https://github.com/openssh/openssh-portable/blob/85ceb0e6

Re: openssl-devel in openssh README

Greetings, Sorin Adrian Savu! > Hello! > I had to compile openssh recently, and the README for cygwin is referencing > openssl-devel package which is obsolete now. I spent some time trying to > figure this out. Can you please update > https://github.com/openssh/openssh-portable/blob/85ceb0e64bff6

Re: OpenSSL 1.1

On Sun, 2019-03-10 at 14:47 -0700, Steven Penny wrote: > Current Cygwin OpenSSL is 1.0.2r. However OpenSSL 1.1 has been available for > several years now: > > https://github.com/openssl/openssl/releases/tag/OpenSSL_1_1_0 We are well aware, and this delay was planned. 1.1 broke API compatibility

Re: OpenSSL 1.0.2r Availability

On Fri, 2019-03-01 at 18:08 +, Anana, Lowell [US] (MS) wrote: > Are there plans to make the openssl 1.0.2r package available to the cygwin > community? Yes, hopefully next week. -- Yaakov -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/

Re: openssl 1.1 beta release available?

2016-04-05 15:59 GMT+02:00 Andrey Repin wrote: > Greetings, Gerrit Haase! > >> is there an openssl 1.1 beta build available somewhere, or is it >> planned to release soon? > > Betas are rarely built for Cygwin. > Wait for a full release, or ask to build with a specific patch, if you need > and unab

Re: openssl 1.1 beta release available?

Greetings, Gerrit Haase! > is there an openssl 1.1 beta build available somewhere, or is it > planned to release soon? Betas are rarely built for Cygwin. Wait for a full release, or ask to build with a specific patch, if you need and unable to do that yourself. -- With best regards, Andrey Rep

Re: OpenSSL as Base package

> > These Perl scripts are nonessential for OpenSSL functionality, and not > > required to be used, unless you have very specific needs. > > Fair enough. In that case, the correct solution is to create a separate > openssl-perl package with those (like Fedora does), and leave those > outside of

Re: OpenSSL as Base package

On Dec 16 13:25, Yaakov Selkowitz wrote: > On 2014-12-16 11:46, Andrey Repin wrote: > The only trouble I see with this is currently Cygwin OpenSSL has Perl > dependency. > >>> > >>>That's likely a bug. > > > >>The openssl package comes with two perl scripts. The dependency > >>gets added au

Re: OpenSSL as Base package

Greetings, Yaakov Selkowitz! > The only trouble I see with this is currently Cygwin OpenSSL has Perl > dependency. That's likely a bug. >> >>> The openssl package comes with two perl scripts. The dependency >>> gets added automatically. >> >> That's a reoccurring issue with depen

Re: OpenSSL as Base package

On 2014-12-16 11:46, Andrey Repin wrote: The only trouble I see with this is currently Cygwin OpenSSL has Perl dependency. That's likely a bug. The openssl package comes with two perl scripts. The dependency gets added automatically. That's a reoccurring issue with dependency walker. Perha

Re: OpenSSL as Base package

Greetings, Corinna Vinschen! >> > The only trouble I see with this is currently Cygwin OpenSSL has Perl >> > dependency. >> >> That's likely a bug. > The openssl package comes with two perl scripts. The dependency > gets added automatically. That's a reoccurring issue with dependency walker. Pe

Re: OpenSSL as Base package

On Dec 16 16:11, Andrey Repin wrote: > Greetings, Steven Penny! > > > I feel that OpenSSL should be a Cygwin Base package. I looked at these > > distros > > > Debian http://debian.org/CD/live > > Fedora http://spins.fedoraproject.org/lxde > > Puppy http://puppylinux.org > > P

Re: OpenSSL as Base package

Greetings, Steven Penny! > I feel that OpenSSL should be a Cygwin Base package. I looked at these distros > Debian http://debian.org/CD/live > Fedora http://spins.fedoraproject.org/lxde > Puppy http://puppylinux.org > Porteus http://porteus.org > MSYS2 http://sourceforge

RE: openssl man pages

From: nu774 > (2013/10/07 1:15), Stan Moore wrote: > > I did a quick google with no joy so I'll throw this out here. Is there > > a reason the man pages for openssl install in /usr/ssl/man instead of > > the system /usr/share/man? It's not really a problem; it came up while > > doing some long over

Re: openssl man pages

(2013/10/07 1:15), Stan Moore wrote: I did a quick google with no joy so I'll throw this out here. Is there a reason the man pages for openssl install in /usr/ssl/man instead of the system /usr/share/man? It's not really a problem; it came up while doing some long overdue maintenance on my shell

Re: Openssl program not compiling

> You should rather add the #define NOCRYPT, but otherwise the answer is > "yes". We switched to the newer set of Windows header files deliberately. Thank you. I will do that. -- Eduardo -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Do

Re: Openssl program not compiling

On Dec 13 18:12, Eduardo Chappa wrote: > >> This used to work in the past, there was no need to switch the order, but > >> it fails now. Why? > > > Because the new Windows headers from Mingw64 define X509_NAME and > > OCSP_RESPONSE, which the former Mingw32 Windows headers didn't. > > Hi Corinna

Re: Openssl program not compiling

>> This used to work in the past, there was no need to switch the order, but it >> fails now. Why? > Because the new Windows headers from Mingw64 define X509_NAME and > OCSP_RESPONSE, which the former Mingw32 Windows headers didn't. Hi Corinna,  Thank you for your reply. In this case, the reas

Re: Openssl program not compiling

On Dec 13 16:37, Eduardo Chappa wrote: > Hello, > >  I am trying to understand why a program that used to compile before, now it > does not. I can make the program compile if I switch the order of the > #include directives. > [...] > #include > #include > #include > > int main(int argc, cha

Re: [OpenSSL]Is it possible to show the numerical value of the public and private key's exponent in a certificate

Risposta al messaggio di Corinna Vinschen : Since this is a OpenSSL question, you will probably have more luck asking on the appropriate openssl-users mailing list: http://www.openssl.org/support/community.html Corinna Ok, I'll ask there in future. Thanks for the link. Sandro -- Proble

Re: [OpenSSL]Is it possible to show the numerical value of the public and private key's exponent in a certificate

Risposta al messaggio di Lou Losee : From the OpenSSL RSA man page: To print out the components of a private key to standard output: openssl rsa -in key.pem -text -noout Not explicitly in the man page, but from reading it, it appears to get the components of the private key, the fol

Re: [OpenSSL]Is it possible to show the numerical value of the public and private key's exponent in a certificate

From the OpenSSL RSA man page: To print out the components of a private key to standard output:         openssl rsa -in key.pem -text -noout Not explicitly in the man page, but from reading it, it appears to get the components of the private key, the following should work:         openssl rsa -

Re: [OpenSSL]Is it possible to show the numerical value of the public and private key's exponent in a certificate

On Jun 26 13:01, gialloporpora wrote: > Dear all, > I am trying to learn how S/MIME encryption/digital signing works. > > I would like to show the numerical values assigned to my private and > public key. > > I have converted my personal certificate from p12 to pem, in this way: > > openssl pkcs

Re: openssl-1.0.1b-1 breaks csh and tcsh

On Apr 29 11:11, Ola Strömfors wrote: > Hi, > > After installing openssl-1.0.1b-1 csh and tcsh give the > following error at startup: > > if: Badly formed number. > > The reason is that the new package contains a corrupt version of > /etc/profile.d/openssl.csh I noticed that earlier today, to

Re: OpenSSL 1.0.1-1 does not seem to support engine aesni

Oh, sorry, yes. I suspect that the AES-NI instructions are used 'silently' where supported by the processor. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cyg

Re: OpenSSL 1.0.1-1 does not seem to support engine aesni

On Apr 17 20:19, Nick Lowe wrote: > In 1.0.1: > > http://www.openssl.org/news/changelog.html > > "Add RC4-MD5 and AESNI-SHA1 "stitched" implementations. > > This work was sponsored by Intel. > [Andy Polyakov]" I didn't mean to imply that there's no new aesni mode, but if you take a look into th

Re: OpenSSL 1.0.1-1 does not seem to support engine aesni

In 1.0.1: http://www.openssl.org/news/changelog.html "Add RC4-MD5 and AESNI-SHA1 "stitched" implementations. This work was sponsored by Intel. [Andy Polyakov]" -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://c

Re: OpenSSL 1.0.1-1 does not seem to support engine aesni

On Apr 17 11:53, Bing Ho wrote: > Hi, > > I have cygwin 1.7.13-1 with openssl 1.0.1-1 installed and was interested in > benchmarking the new aesni hardware accelerated engine, and receive the error > below. > > Does aesni engine support require that I compile openssl myself? There is no aesni

Re: "openssl speed" hangs on cygwin

On Wed, Jul 06, 2011 at 09:21:34AM +0200, Corinna Vinschen wrote: >On Jul 5 12:56, smujushi wrote: >> >> I have an issue when running "openssl speed" on either a 64 bit Windows 7 PC >> (Intel Core i7 870 2.93GHz) or a 64 bit Windows 2008 R2 Std Server (Xeon >> X5450 3GHz) under Cygwin. "openssl s

Re: "openssl speed" hangs on cygwin

On Jul 5 12:56, smujushi wrote: > > I have an issue when running "openssl speed" on either a 64 bit Windows 7 PC > (Intel Core i7 870 2.93GHz) or a 64 bit Windows 2008 R2 Std Server (Xeon > X5450 3GHz) under Cygwin. "openssl speed" runs fine on all the other *Nix's > I manage. > > It hangs eithe

Re: OpenSSL update breaks Subversion

OK, I installed the update once again, and now things work as expected. I'm not sure what changed, but thank you David for your support. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsub

Re: OpenSSL update breaks Subversion

On 2/26/2010 1:59 PM, David Rothenberger wrote: On 2/26/2010 10:37 AM, K Stahl wrote: Cygcheck output attached (Edited to remove personal content). That didn't help me, sorry. The cygcheck output does indicate some possible BLODA interference. Ken -- Problem reports: http://cygwin.co

Re: OpenSSL update breaks Subversion

On 2/26/2010 10:37 AM, K Stahl wrote: Cygcheck output attached (Edited to remove personal content). That didn't help me, sorry. What does "svn help; echo $?" output? -- David Rothenberger daver...@acm.org Cursor, n.: One whose program will not run. -- Robb Russ

Re: OpenSSL update breaks Subversion

On 2/26/2010 5:52 AM, K Stahl wrote: > After updating cygwin this morning, I discovered that the subversion > command line client did not work. > > I tried the following: > svn stat > svn info > svn help > > All svn command simply would not return anything. > > I first reinstalled the subversion

Re: OpenSSL package install - Solution

Hi, I have solved the issue below and figured I would post the solution in case anyone has a similar issue at some point: Apparently, the install for Cygwin 1.7 won't let you install this version of OpenSSL anymore. So I solved it by installing Cygwin 1.7, then getting the setup.exe for 1.5, run

Re: OpenSSL eating CPU.

On Sun, 2008-09-14 at 15:32 -0700, David Woodhouse wrote: > How would I go about debugging it? Without strace and gdb, I'm a > little lost... I managed to reproduce on Linux -- it looks like a real bug in OpenSSL, rather than with the way Cygwin handles select(). https://bugzilla.redhat.com/show_

Re: openssl errors creating password for certificate authority (CA Request)

On Aug 28 11:35, Auteria W. Winzer Jr. wrote: > Here's the steps in creating the CA request and self-signed cert: > [...] > /usr/bin/openssl req -new -key server.key -out server.csr I can reproduce the problem when entering a challenge password here. The strace shows that openssl tries to allocate

Re: openssl errors creating password for certificate authority (CA Request)

hu, 8/28/08, Corinna Vinschen <[EMAIL PROTECTED]> wrote: > From: Corinna Vinschen <[EMAIL PROTECTED]> > Subject: Re: openssl errors creating password for certificate authority (CA > Request) > To: cygwin@cygwin.com > Date: Thursday, August 28, 2008, 10:21 AM > On Aug 28 16:

Re: openssl errors creating password for certificate authority (CA Request)

On Aug 28 16:00, Dr. Volker Zell wrote: > FWIW, I'm in the process of updating neon to the latest version and see the > same error in the latest neon test suite with > openssl-0.9.8h (the latest): > > Write out database with 1 new entries > Data Base Updated > + MKPKCS12='/usr/bin/openssl p

Re: openssl errors creating password for certificate authority (CA Request)

> Corinna Vinschen writes: > On Aug 27 00:33, Auteria W. Winzer Jr. wrote: >> I opt to use a challenge password for sending a CA request. When I incorporate the challenge password I get the following error: >> >> Please enter the following 'extra' attributes >> to be sent

Re: openssl errors creating password for certificate authority (CA Request)

On Aug 27 05:28, [EMAIL PROTECTED] wrote: > $ cygcheck -c openssl > Cygwin Package Information > Package Version Status > Openssl 0.9.8h-1 OK http://cygwin.com/acronyms/#TOFU > -Original Message- > From: Corinna Vinschen <[EMAIL PROTECTED]> http://cygwin.com/acronyms/#PCYMTNQREAIYR

RE: openssl errors creating password for certificate authority (CA Request)

$ cygcheck -c openssl Cygwin Package Information Package Version Status Openssl 0.9.8h-1 OK -Original Message- From: Corinna Vinschen <[EMAIL PROTECTED]> Sent: Wednesday, August 27, 2008 1:58 AM To: cygwin@cygwin.com Subject: Re: openssl errors creating password for certi

Re: openssl errors creating password for certificate authority (CA Request)

On Aug 27 00:33, Auteria W. Winzer Jr. wrote: > I opt to use a challenge password for sending a CA request. When I > incorporate the challenge password I get the following error: > > Please enter the following 'extra' attributes > to be sent with your certificate request > A challenge password []

Re: OpenSSL 0.9.7d 17 Mar 2004 problem with crl function

On Sep 24 15:28, Naipaul Ojar wrote: > OpenSSL problem with crl loading file in current directory. > > OpenSSL> version > OpenSSL 0.9.7d 17 Mar 2004 > OpenSSL> crl -in orego.crl -inform DER -text > unable to load CRL > 2812:error:0D06B08E:asn1 encoding routines:ASN1_d2i_bio:not enough > data:a_d2i

Re: openssl and openssh are downloaded but not installed

On Thu, 4 Mar 2004, Charles wrote: > I downloaded a few dozen files from a mirror and then > was forced off-line. When I came back, I downloaded a few > more files from another mirror.I could not access the first mirror. > Then I did an "Install from Local" and it seemed to be OK but openssl > was

Re: openssl and openssh are downloaded but not installed

Hi Charles, > c:\...\cygwin\ftp%3a%2f%2fcygwin.csie.ntu.edu.tw%2f/pub%2fcygwin\openssh-3.8p1-1.tar.bz2 > c:\...\cygwin\ftp%3a%2f%2fcygwin.csie.ntu.edu.tw%2f/pub%2fcygwin\openssl-0.9.7c-1.tar.bz2 Maybe the files were not donwloaded completely, is it possible to extract them from the command line (

Re: OpenSSL libcrypto

> It's amazing what a package search will turn up... > > Hi, thanks for that. Turned out I needed to install the openssl-devel package. cheers King -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem report

Re: OpenSSL libcrypto

At 08:47 PM 1/27/2004, King Lung Chiu you wrote: >Hi, > >I'm trying to build openssh-3.7.1p2 on Cygwin, but I get the following >error after running configure: > > configure: error: *** Can't find recent OpenSSL libcrypto (see config.log > for details) *** > >I haven't seen any similar posts in t

Re: OpenSSL problem ? (Was Re: Pine 4.58 for Cygwin takes a very long time to close a certain IMAP INBOX)

On Wed, 12 Nov 2003, Corinna Vinschen wrote: > On Wed, Nov 12, 2003 at 04:15:46PM -0200, Fr?d?ric L. W. Meunier wrote: > > On Wed, 12 Nov 2003, Brian Ford wrote: > > > > > Corinna, > > > > > > Did you get a chance to look at the strace output he posted here: > > > > > > http://pervalidus.port5.com

Re: OpenSSL problem ? (Was Re: Pine 4.58 for Cygwin takes a very long time to close a certain IMAP INBOX)

On Wed, Nov 12, 2003 at 04:15:46PM -0200, Fr?d?ric L. W. Meunier wrote: > On Wed, 12 Nov 2003, Brian Ford wrote: > > > Corinna, > > > > Did you get a chance to look at the strace output he posted here: > > > > http://pervalidus.port5.com/tmp/imap.txt.gz > > > > A glance there by trained eyes might

Re: OpenSSL problem ? (Was Re: Pine 4.58 for Cygwin takes a very long time to close a certain IMAP INBOX)

On Wed, 12 Nov 2003, Brian Ford wrote: > Corinna, > > Did you get a chance to look at the strace output he posted here: > > http://pervalidus.port5.com/tmp/imap.txt.gz > > A glance there by trained eyes might save him some time. I don't have the > time or the training for mine :). It appears to

Re: OpenSSL problem ? (Was Re: Pine 4.58 for Cygwin takes a very long time to close a certain IMAP INBOX)

Corinna, Did you get a chance to look at the strace output he posted here: http://pervalidus.port5.com/tmp/imap.txt.gz A glance there by trained eyes might save him some time. I don't have the time or the training for mine :). It appears to be stuck in close on the socket after is has shutdown

Re: OpenSSL problem ? (Was Re: Pine 4.58 for Cygwin takes a very long time to close a certain IMAP INBOX)

On Wed, 12 Nov 2003, Corinna Vinschen wrote: > On Wed, Nov 12, 2003 at 12:20:57AM -0200, Fr?d?ric L. W. Meunier wrote: > > Now I'm trying with gdb, but don't know if the following is > > right. > > > > $ openssl s_client -connect mail.postaccesslite.com:993 > > $ gdb > > (gdb) attach PPID of opens

Re: OpenSSL problem ? (Was Re: Pine 4.58 for Cygwin takes a very long time to close a certain IMAP INBOX)

On Wed, Nov 12, 2003 at 12:20:57AM -0200, Fr?d?ric L. W. Meunier wrote: > Now I'm trying with gdb, but don't know if the following is > right. > > $ openssl s_client -connect mail.postaccesslite.com:993 > $ gdb > (gdb) attach PPID of openssl > (gdb) where > #0 0x77f75a59 in ntdll!DbgUiConnectToDb

Re: OpenSSL problem ? (Was Re: Pine 4.58 for Cygwin takes a very long time to close a certain IMAP INBOX)

On Tue, 11 Nov 2003, Frédéric L. W. Meunier wrote: > On Tue, 11 Nov 2003, Brian Ford wrote: > > > On Tue, 11 Nov 2003, Frédéric L. W. Meunier wrote: > > > On Tue, 11 Nov 2003, Corinna Vinschen wrote: > > > > Me neither. Seems to be a local problem. > > > > > > I don't see what could be wrong with

Re: OpenSSL problem ? (Was Re: Pine 4.58 for Cygwin takes a very long time to close a certain IMAP INBOX)

On Tue, 11 Nov 2003, Brian Ford wrote: > On Tue, 11 Nov 2003, Frédéric L. W. Meunier wrote: > > On Tue, 11 Nov 2003, Corinna Vinschen wrote: > > > Me neither. Seems to be a local problem. > > > > I don't see what could be wrong with my installation. > > > More likely, your network setup. BTW, I

Re: OpenSSL problem ? (Was Re: Pine 4.58 for Cygwin takes a very long time to close a certain IMAP INBOX)

On Tue, 11 Nov 2003, Brian Ford wrote: > On Tue, 11 Nov 2003, Frédéric L. W. Meunier wrote: > > On Tue, 11 Nov 2003, Corinna Vinschen wrote: > > > Me neither. Seems to be a local problem. > > > > I don't see what could be wrong with my installation. > > > More likely, your network setup. > > > An

Re: OpenSSL problem ? (Was Re: Pine 4.58 for Cygwin takes a very long time to close a certain IMAP INBOX)

On Tue, 11 Nov 2003, Frédéric L. W. Meunier wrote: > On Tue, 11 Nov 2003, Corinna Vinschen wrote: > > Me neither. Seems to be a local problem. > > I don't see what could be wrong with my installation. > More likely, your network setup. > Anyway, any steps I can do to debug it are appreciated. > Y

Re: OpenSSL problem ? (Was Re: Pine 4.58 for Cygwin takes a very long time to close a certain IMAP INBOX)

nOn Tue, 11 Nov 2003, Corinna Vinschen wrote: > On Tue, Nov 11, 2003 at 01:52:36AM -0200, Fr?d?ric L. W. Meunier wrote: > > OK, so here's what turns out to be an OpenSSL issue. All thanks > > to Eduardo. > > > > On Mon, 10 Nov 2003, Eduardo Chappa wrote: > > > > > *** Fr?d?ric L. W. Meunier wrote

Re: OpenSSL problem ? (Was Re: Pine 4.58 for Cygwin takes a very long time to close a certain IMAP INBOX)

On Tue, Nov 11, 2003 at 01:52:36AM -0200, Fr?d?ric L. W. Meunier wrote: > OK, so here's what turns out to be an OpenSSL issue. All thanks > to Eduardo. > > On Mon, 10 Nov 2003, Eduardo Chappa wrote: > > > *** Fr?d?ric L. W. Meunier wrote on Nov 11, 2003: > > > > :) > Is there any delay? > > :) >

Re: openssl-0.9.7-1

Mai, Vinh wrote: > Hi There, > > I've read your document regarding this version of openssl. I noticed that > this version now supports Windows CE platform. I developed an application > using Embedded Visual C++ (Windows CE 3.0). I am looking for an open source > to use in my program regarding c

Re: openssl question

On Mon, Jun 23, 2003 at 02:08:43AM +0100, james lankton wrote: > I have configured open ssl-0.9.7b with the command ./ > but am having a problem with the make command. Have a look into ${your_openssl_source_dir}/util/cygwin.sh which is the script to create the Cygwin distro version of OpenSSL. Co

Re: openssl commandline tools always output in text mode

On Sat, Jun 07, 2003 at 11:50:21AM +0200, Corinna Vinschen wrote: Since I was a bit bored a few minutes ago I started to run your test on Linux and guess what? The testit.out file had CRLF lineendings, too. Ups, I just gave it a try on FreeBSD and got the same results as well! Weird. Perhaps thi

Re: openssl commandline tools always output in text mode

On Sat, Jun 07, 2003 at 11:50:21AM +0200, Corinna Vinschen wrote: > On Fri, Jun 06, 2003 at 09:19:12PM +0200, Patrick Eisenacher wrote: > > Please let me know whether you get the same result as I do and whether > > Yes, I do get the same result. > > > this helps identifying the culprit. > > Oh,

Re: openssl commandline tools always output in text mode

On Fri, Jun 06, 2003 at 09:19:12PM +0200, Patrick Eisenacher wrote: > Please let me know whether you get the same result as I do and whether Yes, I do get the same result. > this helps identifying the culprit. Oh, you don't have to wait for me, you can debug this also very easily by yourself.

Re: openssl commandline tools always output in text mode

Hi Corinna, On Fri, Jun 06, 2003 at 01:29:29PM +0200, Patrick Eisenacher wrote: 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 binar

Re: openssl commandline tools always output in text mode

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

Re: openssl commandline tools always output in text mode

Hello Corinna, attached you find the output of cygcheck. Your example also works for me. So I should rephrase my statement, that all openssl commandline tools output in text mode to openssl's smime commandline tool outputs in text mode. Perhaps others as well... Did you try the example I provi

Re: openssl commandline tools always output in text mode

On Thu, Jun 05, 2003 at 10:40:35PM +0200, Patrick Eisenacher wrote: > Heyho, > > openssl's commandline tools always output in text mode, no matter what > your mount type is, be it binary or text. > > Is this a bug or a feature? ;o) Weird. It works for me: $ openssl version OpenSSL 0.9.7b 10 A

Re: openssl - MANPATH - bug?

On Tue, Apr 02, 2002 at 03:10:52PM +0200, Gerrit P. Haase wrote: >Earnie schrieb: > >> Wrong list. I've modified the headers to the appropriate list. > >Why??? Openssl IS a Cygwin Application. - cygwin-apps: a by-approval developers list for discussing packaging issues regarding applications

Re: openssl - MANPATH - bug?

Corinna schrieb: >> > You've assumed that MANPATH had a previous value. >> >> This is the default file which gets installed with openssl by setup.exe. >> So if there is no previous value for MANPATH this cannot work. >> Other application are looking for MANPATH in the environment and don't >> fi

Re: openssl - MANPATH - bug?

On Tue, Apr 02, 2002 at 03:10:52PM +0200, Gerrit P. Haase wrote: > Earnie schrieb: > > > Wrong list. I've modified the headers to the appropriate list. > > Why??? Openssl IS a Cygwin Application. > > > You've assumed that MANPATH had a previous value. > > This is the default file which gets

Re: openssl - MANPATH - bug?

Earnie schrieb: > Wrong list. I've modified the headers to the appropriate list. Why??? Openssl IS a Cygwin Application. > You've assumed that MANPATH had a previous value. This is the default file which gets installed with openssl by setup.exe. So if there is no previous value for MANPATH t

Re: openssl - MANPATH - bug?

Wrong list. I've modified the headers to the appropriate list. You've assumed that MANPATH had a previous value. Earnie. "Gerrit P. Haase" wrote: > > Hallo, > > This > $ cat /etc/profile.d/openssl.sh > export MANPATH="${MANPATH}:/usr/ssl/man" > > results in: > $ set | grep MANPATH > MANPATH