Hello,
After following this as well as the users email chain for the past several
months I’ve noticed that once in a blue moon people will ask how to integrate a
new cipher. In response I decided to write up some documentation on the matter
and just added it to “Internals and Development” on
that
> trend with our next theme - documentation.
>
> Just find some missing documentation, write it and send us a PR on our
> github site. Or help us fix incorrect or out-of-date documentation, or
> broken links, etc.
We held another successful event yesterday. We saw a wide variety
> significant improvements merged as a result. We'd like to continue that
> trend with our next theme - documentation.
>
> Just find some missing documentation, write it and send us a PR on our
> github site. Or help us fix incorrect or out-of-date documentation, or
> broke
Hi all
Our next "Code Health Tuesday" event will be on Tuesday 28th March.
We've seen some great contributions during our last two events with many
significant improvements merged as a result. We'd like to continue that
trend with our next theme - documentation.
Ju
in the direction to some documentation on
>build.info<http://build.info> files?
>
>For the most part I’m creating mine using examples from other crypto
>ciphers but could use some more in depth explanation of what is going
>on when it is being parsed.
>
>More specifically, I’m attempt
Hello,
Can anyone here point me in the direction to some documentation on
build.info<http://build.info> files?
For the most part I’m creating mine using examples from other crypto ciphers
but could use some more in depth explanation of what is going on when it is
being parsed.
On 07/05/2016 02:42 PM, Rich Salz via RT wrote:
> this is for 1.0.2, right?
:; openssl version
OpenSSL 1.1.0-pre6-dev
:; git log
commit c2d551c01930df54bce6517cfecd214db6e98e80
Date: Wed Apr 27 14:47:45 2016 +0100
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4607
Please log i
this is for 1.0.2, right?
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4607
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
Hi --
Attached are four simple patches.
They make the apps more usable.
They should be pretty much self-explanatory.
Let me know if you have questions.
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4607
Please log in as guest with password guest if prompted
>From 07ff5a786d6d0677
commit d9e6d77 pushed to 1.0.2 branch (was already fixed in master). Thanks.
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4573
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
The doc/crypto/rand.pod file incorrectly documents the prototype for the
RAND_add function. The last argument is a double not an int.
It is correctly documented in the doc/crypto/RAND_add.pod file.
Fix attached.
Pauli
--
Oracle
Dr Paul Dale | Cryptographer | Network Security & Enc
Added a sub-section to ciphers.pod in commit 6d1e770. Thanks.
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4539
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
Fixed in commit 0b2d4755d67eece48d1
Thanks for the report.
Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http://www.openssl.org
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4302
Please log in as guest with password gue
Hello Folks,
I'd like to suggest the "ciphers" documentation in 1.1.0 be updated to include
the old EDH names for ciphers which were renamed to DHE between 1.0.2 &
1.1.0-pre.
I think there are only two affected which are still available:
EDH-RSA-DES-CBC3-SHA & EDH-D
This has now been applied, thanks for the contribution.
Ticket closed.
Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http://www.openssl.org
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4435
Please log in as guest with
Added now. Thanks for the contribution.
Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http://www.openssl.org
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4478
Please log in as guest with password guest if prompted
--
Some of PKCS#12 is documented, others are not. This adds missing
documentation for PKCS12_newpass.
The documentation should be placed at "doc/crypto/PKCS12_newpass.pod".
The full test program for EXAMPLE is attached.
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4478
https://github.com/openssl/openssl/pull/876
Add note about when EVP_CIPHER_CTX_set_padding should be called.
Conrado
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4435
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe: https://mt
Yes, that diff fixes the problem, thank you! (Hope to see it in Github :)
On 3/14/16, 11:45, "openssl-dev on behalf of Viktor Dukhovni"
wrote:
>On Mon, Mar 14, 2016 at 03:28:13PM +, Blumenthal, Uri - 0553 - MITLL
>wrote:
>> install ./doc/crypto/EVP_PKEY_set1_RSA.pod ->
>>/Users/ur20980/share
On Mon, Mar 14, 2016 at 03:28:13PM +, Blumenthal, Uri - 0553 - MITLL wrote:
> install ./doc/crypto/EVP_PKEY_set1_RSA.pod ->
> /Users/ur20980/share/man/man3/EVP_PKEY_set1_RSA.3
>
> IO::File=IO(0x7feb8c8029c0) around line 62: Unterminated B<...> sequence
> POD document had syntax errors at /op
Current Github version:
EVP_PKEY_print_public.3 => EVP_PKEY_print_private.3
link /Users/ur20980/share/man/man3/EVP_PKEY_print_params.3 ->
/Users/ur20980/share/man/man3/EVP_PKEY_print_private.3
EVP_PKEY_print_params.3 => EVP_PKEY_print_private.3
install ./doc/crypto/EVP_PKEY_set1_RSA.pod ->
/
pushed in commit 6baa3b430555d25b6eee6440a6b8bee80eaabfc3
thanks.
--
Rich Salz, OpenSSL dev team; rs...@openssl.org
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4312
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe: https://mta.op
001
From: Roumen Petrov
Date: Sat, 13 Feb 2016 10:41:49 +0200
Subject: [PATCH 3/5] documentation: RSA_new_method argument
---
doc/crypto/RSA_set_method.pod | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/crypto/RSA_set_method.pod b/doc/crypto/RSA_set_method.pod
index d09f
https://www.openssl.org/docs/manmaster/apps/x509.html says:
> -[digest]
>
> the digest to use. This affects any signing or display option that uses a
> message digest, such as the -fingerprint,
>-signkey and -CA options. Any digest supported by the OpenSSL dgst
command can be used. If n
Seems to me this can be closed now.
Cheers
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
The SSL_CTX_set1_verify_cert_store.pod changes have been applied
in the master and 1.0.2 branch, doesn't exist in other branches.
SSL_set_tmp_rsa_callback has been removed, so I didn't fix that.
Kurt
___
openssl-dev mailing list
To unsubscribe: https
A couple places in the OpenSSL documentation claims that SSL_foo()
takes an SSL_CTX* instead of an SSL*. i've corrected those here.
---
doc/ssl/SSL_CTX_set1_verify_cert_store.pod | 8
doc/ssl/SSL_CTX_set_tmp_rsa_callback.pod | 2 +-
2 files changed, 5 insertions(+), 5 dele
On Monday 30 November 2015 16:28:06 Salz, Rich wrote:
> > I think it omits a *huge* area of use cases where “openssl”
> > executable itself is used to (a) test and/or debug other SSL/TLS
> > applications and packages, (b) perform cryptographic processing on
> > files and data - either standalone, o
On Monday 30 November 2015 16:23:48 Blumenthal, Uri - 0553 - MITLL
wrote:
> On 11/30/15, 11:10 , "openssl-dev on behalf of Hubert Kario"
>
>
wrote:
> >On Friday 27 November 2015 13:39:36 Tom Jay via RT wrote:
> >> 3. Some kind of useful examples of common usages
> >> of OpenSSL would be appreci
> I think it omits a *huge* area of use cases where “openssl” executable itself
> is used to (a) test and/or debug other SSL/TLS applications and packages, (b)
> perform cryptographic processing on files and data - either standalone, or as
> a part of a script (shell or such).
It would be great
On 11/30/15, 11:10 , "openssl-dev on behalf of Hubert Kario"
wrote:
>On Friday 27 November 2015 13:39:36 Tom Jay via RT wrote:
>> 3. Some kind of useful examples of common usages
>> of OpenSSL would be appreciated.
>
>https://wiki.openssl.org/index.php/Main_Page
>
>If you have specific use cases
On Friday 27 November 2015 13:39:36 Tom Jay via RT wrote:
> 3. Some kind of useful examples of common usages
> of OpenSSL would be appreciated. I'm still trawling through the
> documentation trying to figure out how to do what I want to do and am
> relying heaving on 3rd party gui
On Friday 27 November 2015 13:39:36 Tom Jay via RT wrote:
> 3. Some kind of useful examples of common usages
> of OpenSSL would be appreciated. I'm still trawling through the
> documentation trying to figure out how to do what I want to do and am
> relying heaving on 3rd party gui
Did you see the INSTALL and README files in whatever version you downloaded?
On the download page, I added a link to the release strategy which explains the
release numbering.
--
Rich Salz, OpenSSL dev team; rs...@openssl.org
___
openssl-dev mailing list
Tom Jay via RT wrote on 11/27/2015 02:39 PM:
Hello,
Why is there no meaningul documentation on the OpenSSL download page? Why,
if I'm building a SSL-enabled webserver, do I need to spend so much time on
OpenSSL specifically? Why do the other tasks, of which there are many, not
requires as
Hello,
Why is there no meaningul documentation on the OpenSSL download page? Why, if
I'm building a SSL-enabled webserver, do I need to spend so much time on
OpenSSL specifically? Why do the other tasks, of which there are many, not
requires as much time as OpenSSL to compile, install an
Fixed now to SUITEB* works at the beginning of cipher string.
Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http://www.openssl.org
___
openssl-dev mailing list
To unsubscribe: https://mta.open
fixed in master, thanks.
--
Rich Salz, OpenSSL dev team; rs...@openssl.org
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
already done.
--
Rich Salz, OpenSSL dev team; rs...@openssl.org
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
Fixed in master, 1.0.2, 1.0.1; thanks.
OpenSSL_1_0_1-stable 86de216 RT4019: Duplicate -hmac flag in dgst.pod
OpenSSL_1_0_2-stable 8e0b56b RT4019: Duplicate -hmac flag in dgst.pod
master fe50cd7 RT4019: Duplicate -hmac flag in dgst.pod
Author: Markus Rinne
Date: Mon Aug 24 16:20:13 2015 -0400
--
Message d'origine
De : Markus Rinne via RT
Date :24/08/2015 17:42 (GMT+01:00)
A :
Cc : openssl-dev@openssl.org
Objet : [openssl-dev] [openssl.org #4019] [PATCH] dgst.pod: Remove
redundant documentation of -hmac
Option -hmac was documented twice.
The issu
Option -hmac was documented twice.
The issue was reported here:
https://rt.openssl.org/Ticket/Display.html?user=guest&pass=guest&id=3930
---
doc/apps/dgst.pod | 5 -
1 file changed, 5 deletions(-)
diff --git a/doc/apps/dgst.pod b/doc/apps/dgst.pod
index 236e1b7..b156097 100644
--- a/doc
On Monday 17 August 2015 15:33:18 Wall, Stephen via RT wrote:
> Please, do not change to documentation to match what the code is currently
> doing - some projects try to enforce better security by adding "!EXP:!NULL"
> or similar to the user provided cipher string. Allowin
()], like so:
if (!strcmp(*prule_str, "SUITEB128") ||
!strncmp(*prule_str, "SUITEB128:", 10))
suiteb_flags = SSL_CERT_FLAG_SUITEB_128_LOS;
else ...
Please, do not change to documentation to match what the code is currently
doing - some projects try to
Done, ticket close.
Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http://www.openssl.org
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
fixed in master and 1.0.2, thanks.
--
Rich Salz, OpenSSL dev team; rs...@openssl.org
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
See https://github.com/openssl/openssl/pull/348
I was looking for something else but then saw this text about "normally
supplied by a function such as EVP_des_cbc()"; we should not be misleading
our users in such a fashion.
-Ben
___
openssl-bugs-mod ma
In dgst man page (doc/apps/dgst.pod),
there's duplicate -hmac option documentation:
-hmac arg
set the HMAC key to "arg".
...
-hmac key
create a hashed MAC using "key".
Michal Bozon
___
open
Fixed in master with some other doc/typo fixes with commit
4c583c36596cd86feebd983b0313733fe9870500
--
Rich Salz, OpenSSL dev team; rs...@openssl.org
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
Another small issue revealed on Stack Overflow: "Utilizing PBKDF2 with
OpenSSL library," http://stackoverflow.com/q/22795471.
In the question the OP cited the man page for EVP_BytesToKey. He knew
he needed to use PBKDF2 from the man page, but the man page did not
explicit call out OpenSSL's functi
Please add documentation for SSL_CTX_clear_extra_chain_certs to the man pages
and mention it's existence in SSL_CTX_add_extra_chain_cert.
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
The ECDH callback needs to query the server's certificate to discover
the EC group being used. The callback can then return a temporary key
in the field.
It looks like SSL_get_certificate can be used for the purpose.
SSL_get_certificate is used in apps/s_cb.c, but there's no
documentat
/evp.h#L589
>From 8efc6832a0ef5febbf06b9f70e39fb1232c471c5 Mon Sep 17 00:00:00 2001
From: Laetitia Baudoin
Date: Fri, 3 Apr 2015 16:29:14 -0700
Subject: [PATCH] Fix the EVP_DigestVerifyInit, EVP_DigestVerifyUpdate,
EVP_CIPHER_param_to_asn1 and EVP_CIPHER_asn1_to_param documentation.
---
According to the manpage "-textopt ca_default" suppresses the signature:
ca_default
the value used by the ca utility, equivalent to no_issuer,
no_pubkey, no_header, no_version, no_sigdump and no_signame.
but "openssl x509 -noout -in file.pem -text -certopt ca_default" shows
bot
Steve has added documentation for this. Closing ticket.
Matt
___
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
There's no documentation available for the -no_explicit option of
"openssl ocsp":
https://www.openssl.org/docs/apps/ocsp.html
Dr. Henson explained the meaning of the option and of the corresponding
flag OCSP_NOEXPLICIT for OCSP_basic_verify() like this on the
openssl-users
Ok, change applied, see commit 7005eda3b6e4858233ec3d2a95ff3f5f28f8a484 in the
OpenSSL_1_0_2-stable branch.
Thanks for the heads up!
On Tue Nov 11 00:34:14 2014, hka...@redhat.com wrote:
> Current git OpenSSL_1_0_2-stable branch (39679d858) has errors related to
> hostname-, IP- and email-verific
> > https://github.com/richsalz/openssl/tree/master/apps
>
> the bad descriptions are gone, but the new ones are still missing
Yes. I have to resync against master. Of course I'll do that before the merge.
> https://github.com/richsalz/openssl/tree/master/apps
the bad descriptions are gone, but the new ones are still missing
--
Regards,
Hubert Kario
Quality Engineer, QE BaseOS Security team
Email: hka...@redhat.com
Web: www.cz.redhat.com
Red Hat Czech s.r.o., Purkyňova 99/71, 612 45, Brno, Czech Re
Please look at https://github.com/richsalz/openssl/tree/master/apps which will
be merged into master soon (I hope)
It's the same with s_server, I might add.
I'm looking into this.
On Tue Nov 11 00:34:14 2014, hka...@redhat.com wrote:
> Current git OpenSSL_1_0_2-stable branch (39679d858) has errors related to
> hostname-, IP- and email-verification options.
>
> openssl s_client -help lists following options:
>
Patch applied.
Many thanks,
Matt
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager m
There's a very useful -timeout option in the ocsp utility which is not
mentioned in the manpage or the help output.
diff --git a/apps/ocsp.c b/apps/ocsp.c
index 902546f..0c6579d 100644
--- a/apps/ocsp.c
+++ b/apps/ocsp.c
@@ -650,6 +650,7 @@ int MAIN(int argc, char **argv)
BIO_prin
In an interesting turn, I had emailed John Viega and asked him if there was a
chance of an updated and expanded edition of his book, and his response was:
Probably next year, yes.
so that’s something to look forward to.
-Philip
On Nov 15, 2014, at 2:04 PM, Philip Prindeville
wrote:
> I
I asked O’Reilly if it was going to be updated, but here’s the response I got:
Hello,
Thanks for you for your interest in Network Security with OpenSSL. I wish I
had better news for your, but unfortunately it appears as if there isn't a new
edition being planned.
Best regards,
> From: Krzysztof Kwiatkowski [mailto:krzys...@leeds.pl]
> Sent: Friday, November 14, 2014 7:00 PM
> To: Bush, Stephen F (GE Global Research)
> Cc: openssl-dev@openssl.org; owner-openssl-...@openssl.org
> Subject: Re: Improving Developer Documentation
>
> SRP is another
>
>
Global Research)
Cc: openssl-dev@openssl.org; owner-openssl-...@openssl.org
Subject: Re: Improving Developer Documentation
SRP is another
On Fri, 2014-11-14 at 22:42 +, Bush, Stephen F (GE Global Research)
wrote:
> Pre-Shared Keys might be one example of something that is hard to find in
ssl.org [mailto:owner-openssl-...@openssl.org] On
> Behalf Of david.ll...@fsmail.net
> Sent: Friday, November 14, 2014 4:16 PM
> To: openssl-dev@openssl.org; Krzysztof Kwiatkowski; openssl-dev@openssl.org
> Cc: owner-openssl-...@openssl.org
> Subject: Re: Improving Developer Documenta
-dev@openssl.org; Krzysztof Kwiatkowski; openssl-dev@openssl.org
Cc: owner-openssl-...@openssl.org
Subject: Re: Improving Developer Documentation
OpenSSL APIs haven't changed much in 10 years :)
> In looking for documentation regarding OpenSSL all I have found have
> been outdat
OpenSSL APIs haven't changed much in 10 years :)
> In looking for documentation regarding OpenSSL all I have found have been
> outdated examples. Even the rtfm link is unmaintained and has not been
> updated since 2002, according to this: http://www.rtfm.com/op
I would applaud the effort to create better (and more tutorial-style)
documentation.
It would also be great to bring the documentation and examples up to date.
[Description: cid:image001.jpg@01CFFF4A.CA221DD0]
-Original Message-
From: owner-openssl-...@openssl.org [mailto:owner
In looking for documentation regarding OpenSSL all I have found have been
outdated examples. Even the rtfm link is unmaintained and has not been
updated since 2002, according to this: http://www.rtfm.com/openssl-examples/
I think it would be great to link to these from a single source on the
wiki
http://www.amazon.co.uk/Network-Security-OpenSSL-Cryptography-Communications/dp/059600270X
I've found basics and even more advanced topics in this book, but please
notice that it is more than 10 years old, so doesn't cover new stuff and
I've found some information outdated. Still - good book.
ether they could all be better linked from the OpenSSL wiki is a different
question of course :)
Good luck!
> Message Received: Nov 14 2014, 01:58 AM
> From: "Casey Dunham"
> To: openssl-dev@openssl.org
> Cc:
> Subject: Improving Developer Documentation
>
> G
Greetings,
I have just subscribed and hopefully I am not breaking any list etiquette
here, but I wanted to respond to the thread that was started back in April
on Improving the Documentation for OpenSSL.
http://marc.info/?l=openssl-dev&m=139832883828644
I am a developer (BS CS, Minor in
Current git OpenSSL_1_0_2-stable branch (39679d858) has errors related to
hostname-, IP- and email-verification options.
openssl s_client -help lists following options:
-checkhost host - check peer certificate matches "host"
-checkemail email - check peer certificate matches "email"
-checkip i
On https://www.openssl.org/docs/apps/ciphers.html it lists "Pre shared keying
(PSK) cipheruites"
It should say "cipher suites."
__
OpenSSL Project http://www.openssl.org
Development Mailing List
fixed in head and 1.0.2
OpenSSL_1_0_2-stable 157c345 RT3511: doc fix; req default serial is random
HEAD 3aba132 RT3511: doc fix; req default serial is random
Author: Adam Williamson
Date: Sun Aug 31 18:22:09 2014 -0400
RT3511: doc fix; req default serial is random
RT842, closed back in 2004, ch
ec1 in 2004. Correct
the req documentation to reflect this.
---
doc/apps/req.pod | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/apps/req.pod b/doc/apps/req.pod
index ad538ca..ffede30 100644
--- a/doc/apps/req.pod
+++ b/doc/apps/req.pod
@@ -235,8 +235,8 @@ this option outp
Oops, thanks Rich.
On Tue, Aug 26, 2014 at 10:06 AM, Rich Salz via RT wrote:
> The key is not optional with the -hmac option.
> This is fixed in the rsalz-monolith branch of akamai/openssl on github, to be
> rpart of release after 1.0.2
> thanks.
> --
> Rich Salz, OpenSSL dev team; rs...@openssl.
Oops, thanks Rich.
On Tue, Aug 26, 2014 at 10:06 AM, Rich Salz via RT wrote:
> The key is not optional with the -hmac option.
> This is fixed in the rsalz-monolith branch of akamai/openssl on github, to be
> rpart of release after 1.0.2
> thanks.
> --
> Rich Salz, OpenSSL dev team; rs...@openssl.
The key is not optional with the -hmac option.
This is fixed in the rsalz-monolith branch of akamai/openssl on github, to be
rpart of release after 1.0.2
thanks.
--
Rich Salz, OpenSSL dev team; rs...@openssl.org
__
OpenSSL Project
>From Stack Overflow and "What key is used by openssl (command) for
HMAC if key is not passed in as argument",
https://stackoverflow.com/questions/25492833/what-key-is-used-by-openssl-command-for-hmac-if-key-is-not-passed-in-as-argume.
The docs don't specify the behavior for the following:
ech
On Sat, Jul 05, 2014 at 12:17:13AM +0200, Kurt Roeckx wrote:
> On Fri, Jul 04, 2014 at 10:50:47PM +0200, noloa...@gmail.com via RT wrote:
> > Updated text for the patch based on Viktor's reply to JW and JB on the list.
> >
> > The updated text includes the a statement that its not possible to
> >
On Fri, Jul 04, 2014 at 10:50:47PM +0200, noloa...@gmail.com via RT wrote:
> Updated text for the patch based on Viktor's reply to JW and JB on the list.
>
> The updted text includes the a statement that its not possible to
> determine which named matched (this may be added in the future); and
> t
48 AM, The default queue via RT
wrote:
>
> Greetings,
>
> This message has been automatically generated in response to the
> creation of a trouble ticket regarding:
> "PATCH: Update to X509_check_host documentation",
> a summary of which appears below.
>
> There is
Viktor graciously took the time to explain some of the finer details
of the new name matching API (see
http://www.mail-archive.com/openssl-users@openssl.org/msg74281.html).
The discussion was helpful to me, and would likely be helpful to
others.
The patch incorporates Viktor's comments, and includ
The failures will not be dependent on the input stream.
It could be allocation failures, for example.
But very unlikely.
__
OpenSSL Project http://www.openssl.org
Development Mailing List
Someone already made this fix, a long time ago in a galaxy far far away.
Or via git a few weeks ago.
I can't recall.
__
OpenSSL Project http://www.openssl.org
Development Mailing List
Thanks, fixed, to be commit'd shortly. (The update, not me :)
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
Fixed the typo, thanks.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager majord...@op
Someone already fixed it, and updated the sample code to use the right API.
Good for that nameless person.
__
OpenSSL Project http://www.openssl.org
Development Mailing List op
Integrated, thanks.
Will be put on main/master shortly.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
You are right the default is 100 not nine.
Thanks.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
Simple fix, thanks.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager majord...@openss
Wow, thanks for writing that. And especially the long example.
It points out various magic numbers; see RT ticket 3420 about that.
To be submitted to master head shortly.
__
OpenSSL Project http://w
To be commit'ed to head shortly, thanks.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
Fix will be checked in to master shortly; thanks.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager
Looks like fixed in the latest (2013) version; there is no cross-comipled
entry.
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Auto
Since BIO_push(a,b) returns a, I changed the code examples to ignore the return
value
and explicitly used "b64" Perhaps I should have introduced a new "BIO* top" and
used that?
If so open/re-open a ticket.
__
OpenSSL Project
1 - 100 of 342 matches
Mail list logo