It now works, thanks for your guidance!
Leon Brits
-Original Message-
From: owner-openssl-...@openssl.org [mailto:owner-openssl-...@openssl.org] On
Behalf Of Dr. Stephen Henson
Sent: 15 March 2013 12:42 AM
To: openssl-dev@openssl.org
Subject: Re: RSA sign and verify
On Thu, Mar 14,
Hi,
There are some recent research articles about attack against RC4 in TLS.
Some of these attacks were well known earlier, like biases in the first 256
numbers generated from the RC4 PRG, the newer research combines
this with statistical procedure to extract plaintext from ciphertext.
I
Le 15/03/2013 11:34, Huzaifa Sidhpurwala a écrit :
On Fri, Mar 15, 2013 at 3:39 PM, Erwann Abalea
erwann.aba...@keynectis.com wrote:
Bonjour,
In my understanding, after a fast read of RFC5246, this won't work.
If RC4 is finally considered weak (at last), just don't use it anymore. Do
you use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
The new server currently hosting the www, git, rt, ftp, and cvs
services is going to be moved within the installation of our hoster.
As a consequence, the system will be assigned a new IP address.
Old: 178.16.220.54
New: 185.9.166.106
The
On Fri, 15 Mar 2013 14:25:10 +0100
Erwann Abalea erwann.aba...@keynectis.com wrote:
Drop RC4 when possible, add AES-GCM with TLS1.1+ wherever you can,
upgrade software ASAP.
AES-GCM needs TLS 1.2 - supported by pretty much zero browsers (but at
least some activity recently in the mozilla
From: owner-openssl-us...@openssl.org On Behalf Of Dirk-Willem van Gulik
Sent: Wednesday, 06 March, 2013 06:01
-dev added as a possible minor bug/enhancement, see end
A simple
echo foo | openssl smime -encrypt/sign | openssl smime
-decrypt/verify
works dandy. But was surprized
