[openssl-users] Follow up

2017-12-21 Thread Sai Teja Chowdary
Hi all, Marry Christmas! Please take a look at my previous question, appreciate every bit of help I'm stuck. FYI the guy named ananthaneni saiteja chowdary and myself are same. This email had a problem subscribing to the mailing list earlier hence the other name. Thanks Saiteja. --

Re: [openssl-users] follow-up to: ChaCha20/Poly1305 in OpenSSL?

2016-02-17 Thread PGNd
pebkac. clean re-DL of Openssl 1.0.2f sources fixes that ; patch applies cleanly. -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

Re: [openssl-users] follow-up to: ChaCha20/Poly1305 in OpenSSL?

2016-02-17 Thread PGNd
On Wed, Feb 17, 2016, at 06:05 PM, Salz, Rich wrote: > > > (1) 1.0.2f + cloudflare patch > > (2) 1.1.0-alpha3 > > Did CF update their patch to the official version and codepoints? Cool. > Apparently. But 1st try has one glitch ... patch -p1 <

Re: [openssl-users] follow-up to: ChaCha20/Poly1305 in OpenSSL?

2016-02-17 Thread Salz, Rich
> (1) 1.0.2f + cloudflare patch > (2) 1.1.0-alpha3 Did CF update their patch to the official version and codepoints? Cool. -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

Re: [openssl-users] follow-up to: ChaCha20/Poly1305 in OpenSSL?

2016-02-17 Thread PGNd
On Wed, Feb 17, 2016, at 06:00 PM, Salz, Rich wrote: > > What's current plan status for these ciphers? > > > > Not until 1.1.0 release? Or earlier? > > Yup, 1.1. It's a new feature so it doesn't go into current releases which > only get fixes. Thanks. > And the code that's in master, which

Re: [openssl-users] follow-up to: ChaCha20/Poly1305 in OpenSSL?

2016-02-17 Thread Salz, Rich
> What's current plan status for these ciphers? > > Not until 1.1.0 release? Or earlier? Yup, 1.1. It's a new feature so it doesn't go into current releases which only get fixes. And the code that's in master, which just released alpha-3, rocks. :) -- openssl-users mailing list To

[openssl-users] follow-up to: ChaCha20/Poly1305 in OpenSSL?

2016-02-17 Thread PGNd
I'm looking for Openssl's Chacha20/Poly1305 cipher support, supported client-side in Chrome/Chromium-dev, and server-side in Nginx. Last I was able to find on list [openssl-users] ChaCha20/Poly1305 in OpenSSL? Fri Mar 27 05:05:59 UTC 2015

[openssl-users] follow-up to: ChaCha20/Poly1305 in OpenSSL?

2016-02-17 Thread PGNd
I'm looking for Openssl's Chacha20/Poly1305 cipher support, supported client-side in Chrome/Chromium-dev, and server-side in Nginx. Last I was able to find on list [openssl-users] ChaCha20/Poly1305 in OpenSSL? Fri Mar 27 05:05:59 UTC 2015

Follow up - Re: Can't get PKI Client Authentication Enforcement to work

2007-12-10 Thread Joseph Felten
Replying to my own message to add additional information. When I try it with Firefox, it asks which cert to use from my smart card etc. and then throws this error dialog.: Could not establish an encrypted connection because your certificate was rejected by euukmoappd003n.dev.local. Error Code:

Re: CA Key and Self-Signed Server Certificate Generation - Follow-up

2005-01-12 Thread Dr. Stephen Henson
the CA.pl script which works okay. On this issue, I would like to ask some follow-up questions: 1. Do I have to move server.key and ca.key to /etc/ssl/private and ca.crt /etc/ssl/certs directory respectively? If you used CA.pl correctly there wont be a 'server.key' file initially. The private

Re: CA Key and Self-Signed Server Certificate Generation - Follow-up

2005-01-11 Thread Servie Platon
like to ask some follow-up questions: 1. Do I have to move server.key and ca.key to /etc/ssl/private and ca.crt /etc/ssl/certs directory respectively? 2. Since the command sign.sh server.csr does not work because the sign.sh script is kind of obsoleted already, do I have to move newreq.pem

Follow-up

2001-11-02 Thread George Staikos
Thanks to everyone for pointing me to PEM_X509_INFO_read However I've noticed a very strange problem. If I call: ASN1_d2i_fp(X509_new, d2i_X509, fp, NULL); before I call PEM_X509_INFO_read(fp, NULL, myPemCallback, NULL), and the ASN1_d2i_fp call fails, the PEM_X509_INFO_read call _always_

follow up to Odd run-time failure.

2001-08-31 Thread sschaef2
Using Slackware 7.1 or 8.0 doesn't seem to matter. Program is written in C++ using GNU's g++ compiler. Same failure with OpenSSL-0.9.6a/b. Problem: The web app that I'm coding dies after a few calls to malloc() or C++'s new in the middle of the call. No error code is returned. I've took out

Follow up question to efficient usage of SSL_write().

2001-08-23 Thread Steven Schaefer
I'm not at a location to access the account that receives the subscription mail today so please CC this account on a reply, [EMAIL PROTECTED] I'm kind of delving over which way I should implement buffering. I looked through some of the source code and found in bf_buff.c #define

Re: Follow up question to efficient usage of SSL_write().

2001-08-23 Thread Lutz Jaenicke
On Thu, Aug 23, 2001 at 07:55:13AM -0700, Steven Schaefer wrote: I'm not at a location to access the account that receives the subscription mail today so please CC this account on a reply, [EMAIL PROTECTED] I'm kind of delving over which way I should implement buffering. I looked through

Re: SSL_ERROR_SYSCALL question (follow up)

2001-01-25 Thread Greg Stark
4, 2001 10:26 PM Subject: Re: SSL_ERROR_SYSCALL question (follow up) Hi, I guess what I was wondering was does this just indicate that the peer has simply gone away/shutdown? By violation, does this situation actually a indicate a protocol error? I'm thinking that its not. Take care, Cor

Random test fail on dual cpu i686 follow up!

2001-01-03 Thread Chris Bragg
I have two identical Dell servers, both exactly the same spec, dual pentium 667 with 512MB ram, Linux6.2. I have successfully compiled and tested openssl-0.9.6 on one machine However when I compile it on the second and run make test the test also hangs and when I look at top the %CPU