Re: [openssl-users] FW: problem with missing STDINT.H file

2017-01-30 Thread Jeffrey Walton
> The attached text file is a snippet from attempting to install > openssl-1.1.0c on a Solaris 8 machine. As can be seen, failed when > could not be found. There is no such file anywhere on this > machine. As root, searched from the root directory for the file. Do have > in more than one location

Re: [openssl-users] FW: problem with missing STDINT.H file

2017-01-30 Thread Jakob Bohm
On 30/01/2017 21:44, Carter, James M. (MSFC-ES34) wrote: The attached text file is a snippet from attempting to install openssl-1.1.0c on a Solaris 8 machine. As can be seen, failed when could not be found. There is no such file anywhere on this machine. As root, searched from the root direc

[openssl-users] FW: problem with missing STDINT.H file

2017-01-30 Thread Carter, James M. (MSFC-ES34)
The attached text file is a snippet from attempting to install openssl-1.1.0c on a Solaris 8 machine. As can be seen, failed when could not be found. There is no such file anywhere on this machine. As root, searched from the root directory for the file. Do have in more than one location, /u

Re: [openssl-users] 'No client certificate CA names sent'

2017-01-30 Thread Viktor Dukhovni
> On Jan 30, 2017, at 11:44 AM, russellb...@gmail.com wrote: > >> it is often wise to send an empty list when requesting client certificates. > > How does one send an empty list? https://www.openssl.org/docs/man1.1.0/ssl/SSL_CTX_set_client_CA_list.html Just pass a NULL stack. -- Vikt

Re: [openssl-users] 'No client certificate CA names sent'

2017-01-30 Thread Benjamin Kaduk via openssl-users
On 01/30/2017 10:44 AM, russellb...@gmail.com wrote: > Quoth Mr Viktor Dukhovni, 'it is often wise to send an empty > list when requesting client certificates.' > How does one send an empty list? > That's generally the default server behavior when no CAs are configured for that purpose

Re: [openssl-users] 'No client certificate CA names sent'

2017-01-30 Thread russellbell
Quoth Mr Viktor Dukhovni, 'it is often wise to send an empty list when requesting client certificates.' How does one send an empty list? -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

Re: [openssl-users] Leading Zeros in ASN1_INTEGER?

2017-01-30 Thread Erwann Abalea
Why not? This serial number could also be displayed as 3203232750, or 000BEED73EE, or 03203232750. Cordialement, Erwann Abalea Le 30 janv. 2017 à 11:03, Matthias Ballreich mailto:matthias.ballre...@outlook.de>> a écrit : thanks for explanation. But why did Windows Cert Manager and Firefox Ce

Re: [openssl-users] Leading Zeros in ASN1_INTEGER?

2017-01-30 Thread Jeffrey Walton
On Mon, Jan 30, 2017 at 5:03 AM, Matthias Ballreich wrote: > thanks for explanation. > > But why did Windows Cert Manager and Firefox Cert Manager show 00BEED73EE as > serial number instead of BEED73EE (which openssl shows)? Its just a presentation detail. It appears Microsoft and Mozilla take th

Re: [openssl-users] Leading Zeros in ASN1_INTEGER?

2017-01-30 Thread Matthias Ballreich
thanks for explanation. But why did Windows Cert Manager and Firefox Cert Manager show 00BEED73EE as serial number instead of BEED73EE (which openssl shows)? Von: openssl-users im Auftrag von Viktor Dukhovni Gesendet: Samstag, 28. Januar 2017 17:00:53 An: op

[openssl-users] Does CVE-2016-7055 only impact x86_64 platform ?

2017-01-30 Thread Sandeep Umesh
Hi Can you please clarify if CVE-2016-7055 only impact x86_64 platform ? What about other platforms listed in crypto/bn/asm/ folder which has Montgomery multiplication procedure, is it impacted ? Thanks Regards Sandeep -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailm