[openssl-users] OpenSSL public repository, bug tracker ?

2015-10-28 Thread jonetsu
Sorry if this is answered elsewhere ... Is the version control repository as well as the bug tracker of public read access ? Is it possible to find a specific commit in the OpenSSL repository that would hopefully fix a single discovered/reported bug ? We have hit the

Re: [openssl-users] OpenSSL public repository, bug tracker ?

2015-10-28 Thread Salz, Rich
> Is the version control repository as well as the bug tracker of public read > access ? https://www.openssl.org/source/ ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

Re: [openssl-users] OCSP_sendreq_bio()

2015-10-28 Thread Walter H.
On 28.10.2015 17:27, Steve Marquess wrote: There are environments where https must be used for OCSP, due to policy fiat and/or firewall restrictions. -Steve M. OCSP works through proxies; there is no reason for having such strange setups ... Walter smime.p7s Description: S/MIME

Re: [openssl-users] Where to find the OCSP response signer cert if the OCSP response does not contain one?

2015-10-28 Thread Jakob Bohm
On 28/10/2015 10:24, M K Saravanan wrote: Hi, Upon checking the wireshark capture, I found the OCSP response does not send signer cert, but only the responderID (byKey). In such scenario, where do I find the OCSP response signer cert? Clarifying my own question.

Re: [openssl-users] OCSP_sendreq_bio()

2015-10-28 Thread Walter H.
On 28.10.2015 16:44, Jakob Bohm wrote: On 27/10/2015 21:21, Walter H. wrote: On 26.10.2015 21:42, rosect...@yahoo.com wrote: Hi, I need some help on this call. I am building an OCSP client following guide in openssl and compile the code in Cygwin environment. My openssl version is 1.0.1h.

Re: [openssl-users] OCSP_sendreq_bio()

2015-10-28 Thread Steve Marquess
On 10/28/2015 11:44 AM, Jakob Bohm wrote: > On 27/10/2015 21:21, Walter H. wrote: >> ... >>> >> OCSP must not be https ... >> the same with CRL download ... > Really, I thought that was only a recent cop out rule to > cater to clients with inferior SSL libraries that can't > handle the recursion.

Re: [openssl-users] OCSP_sendreq_bio()

2015-10-28 Thread Jakob Bohm
On 27/10/2015 21:21, Walter H. wrote: On 26.10.2015 21:42, rosect...@yahoo.com wrote: Hi, I need some help on this call. I am building an OCSP client following guide in openssl and compile the code in Cygwin environment. My openssl version is 1.0.1h. With HTTP based OCSP, the code works

Re: [openssl-users] OCSP_sendreq_bio()

2015-10-28 Thread Jakob Bohm
On 28/10/2015 17:36, Walter H. wrote: On 28.10.2015 16:44, Jakob Bohm wrote: On 27/10/2015 21:21, Walter H. wrote: On 26.10.2015 21:42, rosect...@yahoo.com wrote: Hi, I need some help on this call. I am building an OCSP client following guide in openssl and compile the code in Cygwin

Re: [openssl-users] Freeing of const char * fields in ASN1_OBJECT

2015-10-28 Thread Michael Wojcik
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf > Of Reinier Torenbeek > Sent: Wednesday, October 28, 2015 16:55 > > In asn1/asn1.h, the fields sn and ln in ASN1_OBJECT are defined as const > char *: > > 211 typedef struct asn1_object_st > 212 { > 213

[openssl-users] Const qualifier for EVP_PKEY parameters in pub_encode method

2015-10-28 Thread Reinier Torenbeek
Hi, While implementing an engine, I run into the following prototype that I need to implement: struct evp_pkey_asn1_method_st { int (*pub_encode)(X509_PUBKEY *pub, *const* EVP_PKEY *pk); } /* EVP_PKEY_ASN1_METHOD */; Inside this function, I want to assign pk to pub->pkey (and do the

[openssl-users] Freeing of const char * fields in ASN1_OBJECT

2015-10-28 Thread Reinier Torenbeek
Hi, The following looks wrong and actually resulted in a crash for me before I decided to do things differently: In asn1/asn1.h, the fields sn and ln in ASN1_OBJECT are defined as const char *: 211 typedef struct asn1_object_st 212 { 213 const char *sn,*ln; 214 int nid;

Re: [openssl-users] Where to find the OCSP response signer cert if the OCSP response does not contain one?

2015-10-28 Thread M K Saravanan
Hi, > Upon checking the wireshark capture, I found the OCSP response does not send > signer cert, but only the responderID (byKey). > > In such scenario, where do I find the OCSP response signer cert? Clarifying my own question. https://tools.ietf.org/html/rfc6960#section-4.2.2.3 says: