essage-ID:
> <d0d55ec8a95b439ea54af80156934...@usma1ex-dag1mb1.msg.corp.
> akamai.com>
> Content-Type: text/plain; charset="utf-8"
>
> Yes, just put the entire chain in the server?s PEM file.
> -- next part --
> An HTML attach
Hi there,
how can i access the Mozilla NSS (shared) Database (cert8 or cert9d.db) /
PKCS#11-Modules via OpenSSL?
I need read & write access to the NSS User Cert Database (softokn3) and to the
Built-In Cert Database (nssckbi) under Windows.
I tried it with Libp11 this way:
int rc = 0;
Can this person be dropped from the list?
From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of
Hello Notelling
Sent: Tuesday, November 08, 2016 9:47 AM
To: openssl-users@openssl.org
Subject: Re: [openssl-users] openssl-users Digest, Vol 24, Issue 16
Your query is being
I sent them a warning yesterday and today dropped/banned them.
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
> On Nov 8, 2016, at 4:26 AM, Erwann Abalea wrote:
>
> The root certificate is not expected to be sent by the server, as it already
> needs to be known and trusted by the client.
> However, you’re free to configure your server to send it, for debugging or
>
On 11/08/2016 01:24 AM, Joachim Person wrote:
> Hi,
>
> It seems like the documentation for SSL_set_tlsext_host_name is gone.
> Does anyone know where I can find the documentation? I am interested
> in the return values right now.
>
>
Hi Joachim,
>> It seems like the documentation for SSL_set_tlsext_host_name is gone.
>> Does anyone know where I can find the documentation? I am interested
in the return values right now.
If I got it right:
1) ssl/tls1.h (line 334ff): # define SSL_set_tlsext_host_name(s,name) \
334
On Tue, Nov 8, 2016 at 3:05 PM, Jakob Bohm wrote:
> On 08/11/2016 14:44, Kim Gräsman wrote:
>>
>> On Tue, Nov 8, 2016 at 2:24 PM, Michael Wojcik
>> wrote:
>>>
>>> My advice, frankly, is to study the OpenSSL build process until you
>>>
In message <20161108.083722.982336643109774878.levi...@openssl.org> on Tue, 08
Nov 2016 08:37:22 +0100 (CET), Richard Levitte said:
levitte> In message
on Mon, 7
Nov 2016 21:50:13 +0300, Dmitry Belyavsky
Hi Kim.
Thanks for the reply.
On 8 Nov 2016 11:59 a.m., "Kim Gräsman" wrote:
>
> On Tue, Nov 8, 2016 at 6:26 AM, Ajay Garg wrote:
> >
> > Is compiling on windows always such a pain? :(
> > On Linux, it compiled perfectly the first time itself.
>
>
Hi,
I'm trying to use EVP_EncryptUpdate() with EVP_aes_256_cbc_hmac_sha256()
to speed up encryption.
This "stiched" version should be faster than first hashing and then
encrypt the data.
See also
https://software.intel.com/sites/default/files/open-ssl-performance-paper.pdf
for some background.
Bonjour,
The root certificate is not expected to be sent by the server, as it already
needs to be known and trusted by the client.
However, you’re free to configure your server to send it, for debugging or
informational purposes.
Cordialement,
Erwann Abalea
Le 8 nov. 2016 à 03:36, Mofassir Ul
On 08/11/2016 14:44, Kim Gräsman wrote:
On Tue, Nov 8, 2016 at 2:24 PM, Michael Wojcik
wrote:
My advice, frankly, is to study the OpenSSL build process until you understand
it. We've had
issues in the past with some Windows Perl implementations (currently we use
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,
[not quoting anything because Outlook can't quote HTML email properly]
I build OpenSSL for static linking (though using a hacked configuration, since
it's going to be linked into a DLL, and we do not want the C RTS linked
statically). I've not seen any of these problems. We build on a variety
Yes, just put the entire chain in the server’s PEM file.
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
On Tue, Nov 8, 2016 at 2:24 PM, Michael Wojcik
wrote:
>
> My advice, frankly, is to study the OpenSSL build process until you
> understand it. We've had
> issues in the past with some Windows Perl implementations (currently we use
> Cygwin Perl with
> a wrapper
17 matches
Mail list logo