From someone who does NOT understand the in's and out's of what people
(developers and users) have been using openSSL for.
My first reaction is: have developers been using openSSL, or has it gone to
abusing it?
For the sake of argument - let's say just use as it has always been
intended.
Many
On 06/02/15 21:46, Matt Caswell wrote:
On 06/02/15 15:48, Susan Hinrichs wrote:
Hello,
In Apache Traffic Server we are primarily using SSL_accept and
SSL_read/SSL_write with file descriptor bios.
But during the handshake, we need to feed in our own packets via
read-only buffers. We
On 3 February 2015 at 22:02, Rich Salz rs...@openssl.org wrote:
As we've already said, we are moving to making most OpenSSL data
structures opaque. We deliberately used a non-specific term. :)
As of Matt's commit of the other day, this is starting to happen
now. We know this will
On 07/02/15 14:41, Richard Moore wrote:
On 3 February 2015 at 22:02, Rich Salz rs...@openssl.org
mailto:rs...@openssl.org wrote:
As we've already said, we are moving to making most OpenSSL data
structures opaque. We deliberately used a non-specific term. :)
As of Matt's
Il 07/02/2015 15:41, Richard Moore ha scritto:
I've documented what got broken in Qt by the changes so far. I've listed
the functions I think we can use instead where they exist, and those
where there does not appear to be a replacement.
The other question would be: assuming there's no
On Sat, Feb 07, 2015, Richard Moore wrote:
I've documented what got broken in Qt by the changes so far. I've listed
the functions I think we can use instead where they exist, and those where
there does not appear to be a replacement.
For the DH case could you store the encoding of the
STOP FUCKING USING MY FUCKING EMAIL ADDRESS IN EMAILS. IF YOU WANT TO
SEND AN EMAIL, SEND IT FROM YOUR OWN ACCOUNT.
BELOW, I REPLIED TO AN EMAIL SENT BY OPENSRS. BUT BECAUSE OPENSRS IS
PRETENDING TO BE ME, IT WAS SENT TO ME INSTEAD OF OPENSRS.
I'VE CHANGED ALL THESE CONTACT POINTS TO OPENSRES,
On 7 February 2015 at 17:22, Dr. Stephen Henson st...@openssl.org wrote:
On Sat, Feb 07, 2015, Richard Moore wrote:
I've documented what got broken in Qt by the changes so far. I've listed
the functions I think we can use instead where they exist, and those
where
there does not appear
Please consider including other message digest algorithms like sha256
For example here: https://www.openssl.org/docs/apps/ca.html
Thank you!
Szépe Viktor
--
+36-20-4242498 s...@szepe.net skype: szepe.viktor
Budapest, XX. kerület
___
On 07/02/15 14:41, Richard Moore wrote:
On 3 February 2015 at 22:02, Rich Salz rs...@openssl.org
mailto:rs...@openssl.org wrote:
As we've already said, we are moving to making most OpenSSL data
structures opaque. We deliberately used a non-specific term. :)
As of Matt's
On 8 February 2015 at 00:19, Matt Caswell m...@openssl.org wrote:
On 07/02/15 14:41, Richard Moore wrote:
On 3 February 2015 at 22:02, Rich Salz rs...@openssl.org
mailto:rs...@openssl.org wrote:
As we've already said, we are moving to making most OpenSSL data
structures
11 matches
Mail list logo
