Fixed in rsalz-monolith branch of akamai/openssl fork on github.
Will be merged post-1.0.2; thanks
commit 8a5466bd0fbfd3131ae5f5f93d35cfa77c979a2f
Author: Kurt Cancemi
Date: Fri Aug 22 17:03:24 2014 -0400
PR3501: Typo's in s_server help text.
Fixed help text for -crl_check and -crl_check_all
-
It'd be good to fix this.
Opening an RT (email to r...@openssl.org) is the simplest way. Thanks!
--
Principal Security Engineer
Akamai Technologies, Cambridge MA
IM: rs...@jabber.me Twitter: RichSalz
Update patch, the previous version of the patch had corrections to
words that were correct in UK English but not in US English, unless
the OpenSSL project wants to use US English only now then disregard
this updated patch.
---
Kurt Cancemi
https://www.x64Architecture.com
>From 27c9379231ac6cce871
As per my experimentation, reported results and ensuing discussion,
I'd appreciate a decision on whether to move forward with adopting a
"single-Makefile" build structure:
Report (Google Docs): http://goo.gl/yhvCno
https://groups.google.com/d/topic/openssl-testing/AUJME_4xkWM/discussion
https://gr
I have the global sign new and old CA certs in a single file.
Successful verification seems to depend on the order of the
certificates in the file:
$ cat globalsign_new.pem globalsign_old.pem > test.pem
$ openssl s_client -connect bbc.co.uk:443 -CAfile test.pem
...
Verify return code: 0 (ok)
$
> So I would not understand that we go in a hurry to remove WCE compatibility
I do not think we are in a hurry to do that.
Your patch looks nice. I am CC'ing rt, so that this thread becomes an issue
and we'll see the link to your mail.
--
Principal Security Engineer
Akamai Technologies, Camb
Cause I've not figured out how to reply to openssl-dev ... without
subscribe, so, here is how to reproduce the failure:
On one console, execute this command:
$ yes "hello client" | openssl s_server -accept -CAfile ca.crt -cert
server.pem -key server.pem -state
On another console, execute thi
Executive summary:
Forgive me if I have overlooked something, but I could not
find any discussion of the nameConstraints bypass bug on
openssl.org. Is everybody aware of this? Do we need to
add it to the request tracker?
On the cryptography list, on 07/19/2014 02:37 PM,
Applied in slightly amended form to all branches, see commits
be0477a8e97a1f771f8aa6e97aa064033f4dcade
and
3aac17a82fbaf2bc23ee62f24611e5883d3e7b97
__
OpenSSL Project http://www.openssl.org
Developm
Applied to all applicable branches (1.0.0+), see commits
bc46db60f170873cc323e78e71e582adfa0ddf7f
and
e19c93811f0db499c98d2888f1c0c0ab65e6238a
__
OpenSSL Project http://www.openssl.org
Development M
In message <14082121323639_20200...@antinode.info> on Thu, 21 Aug 2014 21:32:36
-0500, "Steven M. Schweda" said:
sms> From: Richard Levitte
sms>
sms> > There is some similar package for Perl, isn't there? Is that very
sms> > much of a pain? [...]
sms>
sms>I expect it to be one more thin
11 matches
Mail list logo