On the other hand, we try to keep the advertised (c) on binaries up to date.
About the only way to do that is to make updating the (c) date part of the build scripts, that's relatively easy on Windows as the resource file is text and gets compiled.
Which reminds me ... :{Peter
- Original Message -
From: Matt Caswell via RT r...@openssl.org
To: hka...@redhat.com
Cc: openssl-dev@openssl.org
Sent: Tuesday, 17 June, 2014 12:50:03 AM
Subject: [openssl.org #3385] Patch: document -trusted_first option in man
pages and help.
Hi Hubert
Thanks for the patch!
- Original Message -
From: Matt Caswell via RT r...@openssl.org
To: hka...@redhat.com
Cc: openssl-dev@openssl.org
Sent: Tuesday, 17 June, 2014 12:50:03 AM
Subject: [openssl.org #3385] Patch: document -trusted_first option in man
pages and help.
Hi Hubert
Thanks for the patch!
On Tue Jun 17 13:38:49 2014, hka...@redhat.com wrote:
Thank you, somehow missed that.
For now I just removed changes to s_time and ts from patch set.
Fixed pull request: https://github.com/openssl/openssl/pull/138
The -trusted_first option is handled through a common verify options function
- Original Message -
From: Stephen Henson via RT r...@openssl.org
To: hka...@redhat.com
Cc: openssl-dev@openssl.org
Sent: Tuesday, 17 June, 2014 2:31:07 PM
Subject: [openssl.org #3385] Patch: document -trusted_first option in man
pages and help.
On Tue Jun 17 13:38:49 2014,
- Original Message -
From: Stephen Henson via RT r...@openssl.org
To: hka...@redhat.com
Cc: openssl-dev@openssl.org
Sent: Tuesday, 17 June, 2014 2:31:07 PM
Subject: [openssl.org #3385] Patch: document -trusted_first option in man
pages and help.
On Tue Jun 17 13:38:49 2014,
In openssl-1.0.1h, script ssl/misc/tsget
the last line
WWW::Curl::Easy::global_cleanup();
isn't needed as of WWW::Curl v4.15
(also tested with WWW::Curl v4.17)
Cheers,
Daniel
I had occasion to check the dgst(1) manpage and found several minor flaws
(in 1.0.1h, haven't tried 1.0.2 yet and don't do repository), a few of which
might benefit from discussion
header and synopses: The list of alg names, (correctly) used as both
dash-options
and (sub)command-names, also
Spelling corrections in openssl.cnf
$ git diff apps/openssl.cnf
diff --git a/apps/openssl.cnf b/apps/openssl.cnf
index ccc21a2..c861dd4 100644
--- a/apps/openssl.cnf
+++ b/apps/openssl.cnf
@@ -40,12 +40,12 @@ default_ca = CA_default# The default ca section
[ CA_default ]
dir
Applied, thanks for the report.
Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http://www.openssl.org
__
OpenSSL Project
Sunil wrote:
I am trying to compile openssl-0.9.8za but it is giving the below compilation
errors. I could not find the definition for the INT_MAX.
It's listed as a known issue in the 0.9.8za release notes. You need to
#include limits.h. It's fixed in the dev branch for 0.9.8zb.
Does openssl handle a clientHello (or any handshake message) that splits across
records?
I can't quite tell ... :)
--
Principal Security Engineer
Akamai Technologies, Cambridge, MA
IM: rs...@jabber.memailto:rs...@jabber.me; Twitter: RichSalz
Does openssl handle a clientHello (or any handshake message) that splits
across records?
Mostly yes (I know because I made the changes to allow this a long time
ago). A notable exception is that the cross-version code in s23_srvr.c
requires that the first fragment contain at least 6 bytes of
Ø Mostly yes (I know because I made the changes to allow this a long time ago).
That’s what it seemed to me (because read_message will fill a buffer as
needed), but the intern here was pretty sure of himself.
Now, maybe not so sure ☺
--
Principal Security Engineer
Akamai Technologies,
Merged:
https://git.openssl.org/gitweb/?p=openssl.git;a=commit;h=8a6c6bbf21cc11ea0fed69a106250af0d734d786
https://git.openssl.org/gitweb/?p=openssl.git;a=commit;h=96fc4b72506c1573fd80cfc1d2e5ca4d3d0c2b3f
15 matches
Mail list logo
