Re: [openssl-dev] Fwd: Re: [openssl-users] Duplicating const X509_NAME

No, thanks, that looks good! -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

Re: [openssl-dev] Fwd: Re: [openssl-users] Duplicating const X509_NAME

Hi Rich, >> Just go ahead a file a pull request anyway...that's the best way of getting >> comments. If changes are needed you can update the PR as required. > > Like, for example, documenting this new function. :) Sure, I did mention it alongside its get0 counterpart in doc/man3/OCSP_resp_find_

Re: [openssl-dev] [openssl.org #4504] Openssl cms encrypt bug.

Hi Andrew, I seem to recall that depending of the OpenSSL version, there was issue with CFB1 mode. Michel. -Message d'origine- De : openssl-dev [mailto:openssl-dev-boun...@openssl.org] De la part de ?? ? via RT Envoyé : lundi 7 novembre 2016 11:40 Cc : openssl-dev@openssl.o

Re: [openssl-dev] Missing access to ex_nscert data

> Unless I overlooked something the new OpenSSL-1.1.0 does not allow access > to the ex_nscert data of the X509 object. Would it be possible to add such > function to the API? Yes. Missing accessors are bugfixes and can go into a 1.1.0 update. Please open an issue or even better a PR. -- opens

[openssl-dev] Missing access to ex_nscert data

Hi, I'm trying to port OpenVPN to OpenSSL-1.1.0 API. Unless I overlooked something the new OpenSSL-1.1.0 does not allow access to the ex_nscert data of the X509 object. Would it be possible to add such function to the API? Regards, -- Tomas Mraz No matter how far down the wrong road you've gone

Re: [openssl-dev] Fwd: Re: [openssl-users] Duplicating const X509_NAME

> Just go ahead a file a pull request anyway...that's the best way of getting > comments. If changes are needed you can update the PR as required. Like, for example, documenting this new function. :) -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

Re: [openssl-dev] Fwd: Re: [openssl-users] Duplicating const X509_NAME

Hi Matt, thanks for your quick reply. >> Please also see my commit >> https://github.com/satta/openssl/commit/4392b12a0caa8f8e7df0bb6e1c94de7f744407ba >> implementing this. Looking forward to some comments -- if you are OK >> with it I would be happy to file a pull request. My CLA has been signed

Re: [openssl-dev] Backporting opaque struct getter/setter functions

IANAL, but: 1. Some people see GPL or even LGPL and run away screaming. 1a. Using this means that the using the OpenSSL library requires accepting the LGPL. 1b. Some interpretations of the LGPL permit use when the code is in a dynamically-linked library. Since this is a header file, any code wit

Re: [openssl-dev] Fwd: Re: [openssl-users] Duplicating const X509_NAME

On 08/11/16 12:41, Sascha Steinbiss wrote: > Dear OpenSSL developer team, > > following up on the discussion quoted below on the openssl-users ML I > would like to ask your opinions on adding a OCSP_resp_get1_id() function: > > int OCSP_resp_get1_id(const OCSP_BASICRESP *bs, >

[openssl-dev] Fwd: Re: [openssl-users] Duplicating const X509_NAME

Dear OpenSSL developer team, following up on the discussion quoted below on the openssl-users ML I would like to ask your opinions on adding a OCSP_resp_get1_id() function: int OCSP_resp_get1_id(const OCSP_BASICRESP *bs, ASN1_OCTET_STRING **pid, X509_NA

Re: [openssl-dev] Backporting opaque struct getter/setter functions

On Monday, 7 November 2016 21:26:16 CET Short, Todd wrote: > The file below is LPGL 2.1, and may not be compatible with various projects. > Can it be changed to use the OpenSSL license or equivalent? how LGPL may not be compatible with any project? > -- > -Todd Short > // tsh...@akamai.com