Re: [openssl-users] openssl 1.1.1 manuals

2018-12-27 Thread Jakob Bohm via openssl-users
On 27/12/2018 20:39, Dr. Matthias St. Pierre wrote: Particularly if you don't know exactly what one is looking for... { There is something amiss with BIO_addr_rawaddress... it's shift right. I don't see a problem in the HTML source though.. } Sure, google will find some things, but usually

[openssl-users] How can I compile nginx with openssl to support 0-rtt TLS1.3

2018-12-27 Thread ၾကည္စိုး သင္း
Dear Sirs, I have an nginx web server compiled with openssl that support TLS 1.3. But when I test with firefox Nightly browser, it does not send early data together with client hello packet. I test this test after waiting for about five minutes after accessing web server. I cannot find any source

[openssl-users] Decrypting an OpenSSL encrypt AES256-CBC data

2018-12-27 Thread Ertan Küçükoglu
Hello, First of all I am a newbie to this list and to cryptography, padding, and C language. Please, bear with me. I am trying to encrypt some data on an embedded Linux system using OpenSSL crypto library and decrypt it on a Windows system. I am following example at following link for C codes

Re: [openssl-users] openssl 1.1.1 manuals

2018-12-27 Thread Dr. Matthias St. Pierre
> The docs site is screwed up. Actually, it is screwed up for the older versions, not for 1.1.1: In OpenSSL 1.1.0 and before, the pod files (the manual page sources) would be located in /doc/crypto and /doc/ssl, and only during the installation would be placed in the proper manX subdirectory

[openssl-users] setting eContentType for CMS messages without CMS_PARTIAL

2018-12-27 Thread Michael Richardson
A major way in which PKCS7 and CMS signed artifacts differ is that the CMS artifacts include a content-type. RFC5652 has a decision tree to decide what version of SignedData structure to produce. The presence of a non-"id-data" content-type is among the decision tree, and so I understand why it

[openssl-users] setting eContentType for CMS messages without CMS_PARTIAL

2018-12-27 Thread Michael Richardson
A major way in which PKCS7 and CMS signed artifacts differ is that the CMS artifacts include a content-type. RFC5652 has a decision tree to decide what version of SignedData structure to produce. The presence of a non-"id-data" content-type is among the decision tree, and so I understand why it

Re: [openssl-users] openssl 1.1.1 manuals

2018-12-27 Thread Dr. Matthias St. Pierre
> Particularly if you don't know exactly what one is looking for... > { There is something amiss with BIO_addr_rawaddress... it's shift right. > I don't see a problem in the HTML source though.. } > > Sure, google will find some things, but usually it's the wrong version, and > one has to guess

Re: [openssl-users] openssl 1.1.1 manuals

2018-12-27 Thread Michael Richardson
Dr. Matthias St. Pierre wrote: >> Generally I find everything I need in the source tarball and after the >> install is done everything anyone could want is installed on the >> system. As for 'sidenav' that sounds like someone actually has to go >> tweak stuff manually on some

Re: [openssl-users] openssl 1.1.1 manuals

2018-12-27 Thread Blumenthal, Uri - 0553 - MITLL
The docs site is screwed up. CMS_sign is indeed documented for 1.1.1 - but you have to go there via https://www.openssl.org/docs/man1.1.1 -> Libraries -> CMS_sign.html, which would bring you to https://www.openssl.org/docs/man1.1.1/man3/CMS_sign.html On 12/27/18, 14:00, "openssl-users on

Re: [openssl-users] openssl 1.1.1 manuals

2018-12-27 Thread Michael Richardson
J. J. Farrell wrote: > man1.1.1 looks OK to me, the pages all appear to be there. What is > missing is a link to 1.1.1 in the little Manpages list of links on the > right hand side of the page https://www.openssl.org/docs/man1.1.0/crypto/CMS_sign.html exists, but

Re: [openssl-users] openssl 1.1.1 manuals

2018-12-27 Thread Dr. Matthias St. Pierre
> Generally I find everything I need in the source tarball and after the > install is done everything anyone could want is installed on the system. > As for 'sidenav' that sounds like someone actually has to go tweak stuff > manually on some website. Sadly. Anyways, the source tarballs have >

Re: [openssl-users] openssl 1.1.1 manuals

2018-12-27 Thread Dennis Clarke
On 12/27/18 11:48 AM, Salz, Rich via openssl-users wrote: They are there, but the sidenav needs to be updated. Generally I find everything I need in the source tarball and after the install is done everything anyone could want is installed on the system. As for 'sidenav' that sounds like

Re: [openssl-users] PerlASM for x64

2018-12-27 Thread Richard Levitte
In message <98f571de-f47e-6259-f1ac-792ebed3e...@wisemo.com> on Thu, 27 Dec 2018 10:12:34 +0100, Jakob Bohm said: > On 24/12/2018 19:08, Richard Levitte wrote: > > In message <3fc4d543-d71a-8c22-566a-d902c4f7d...@gmail.com> on Mon, 24 > > Dec 2018 13:17:51 +0100, Gisle Vanem said: > > > >>

Re: [openssl-users] openssl 1.1.1 manuals

2018-12-27 Thread Salz, Rich via openssl-users
They are there, but the sidenav needs to be updated. On 12/27/18, 11:31 AM, "Michael Richardson" wrote: If manual pages for 1.1.1 aren't going to be posted/generated: could https://www.openssl.org/docs/man1.1.1 redirect to https://www.openssl.org/docs/man1.1.0? (I

Re: [openssl-users] openssl 1.1.1 manuals

2018-12-27 Thread J. J. Farrell
man1.1.1 looks OK to me, the pages all appear to be there. What is missing is a link to 1.1.1 in the little Manpages list of links on the right hand side of the page On 27/12/2018 16:31, Michael Richardson wrote: If manual pages for 1.1.1 aren't going to be posted/generated: could

[openssl-users] openssl 1.1.1 manuals

2018-12-27 Thread Michael Richardson
If manual pages for 1.1.1 aren't going to be posted/generated: could https://www.openssl.org/docs/man1.1.1 redirect to https://www.openssl.org/docs/man1.1.0? (I think that 1.1.1 ought to be generated) -- ] Never tell me the odds! | ipv6 mesh networks [ ]

Re: [openssl-users] Openssl async support

2018-12-27 Thread ASHIQUE CK
Hi all, Thanks for the earlier reply. But still Iam facing issue regarding the asynchronous job operation. I have implemented asynchronous job operation partially. I am now getting requests asynchronously ie. getting the next request after calling ASYNC_pause_job from the

Re: [openssl-users] Delay in converting CRL to binary data

2018-12-27 Thread Salz, Rich via openssl-users
* Please let me know if we have any update on this. This is a volunteer effort. :) My *GUESS* is that the CRL data isn’t sorted, and it’s doing a linear search. You should profile the code to find out where, exactly, all the time is being spent. -- openssl-users mailing list To

Re: [openssl-users] OpenSSL v1.1.1 static library size reduction

2018-12-27 Thread Salz, Rich via openssl-users
* Please find the above previous mail. I am not sure what this means. I guess you are referring to earlier email in the thread. I gave you my suggestion, good luck. -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

Re: [openssl-users] PerlASM for x64

2018-12-27 Thread Jakob Bohm via openssl-users
On 24/12/2018 19:08, Richard Levitte wrote: In message <3fc4d543-d71a-8c22-566a-d902c4f7d...@gmail.com> on Mon, 24 Dec 2018 13:17:51 +0100, Gisle Vanem said: Richard Levitte wrote: I experimented some more. I figured the "auto" does not work. But this works: perl

Re: [openssl-users] OpenSSL v1.1.1 static library size reduction

2018-12-27 Thread Devadas kk
This sounds the simple and optimal approach for the problem stated. On Tue, 25 Dec 2018, 12:59 am Salz, Rich via openssl-users < openssl-users@openssl.org wrote: > If all you need is RSA then you will probably find it easier to write a > makefile of your own. You will have to do multiple builds

[openssl-users] tls1_change_cipher_state

2018-12-27 Thread Dmitry Belyavsky
Hello, Am I right supposing that local variables tmp1, tmp2, iv1, and iv2 are unused in this function? -- SY, Dmitry Belyavsky -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users