Hi all,
upon executing the command openssl speed -evp aes-256-cbc, I get the output
as:
Doing aes-256-cbc for 3s on 16 size blocks: 27106690 aes-256-cbc's in 2.94s
Doing aes-256-cbc for 3s on 64 size blocks: 8450205 aes-256-cbc's in 2.96s
Doing aes-256-cbc for 3s on 256 size blocks: 2252068
Hello everybody !
I’m working on a Qt lib, based on OpenSSL (QCA - QtCryptographicArchitecture),
actually I’m joining the last dev on it.
The lib was written in 2001, and there are some unit tests using many x509
certificates and combination of them (Good CA, Bad CA, Bad Chain, End cert
On Wed, Dec 04, 2013 at 01:29:09PM +0100, Fedor Brunner wrote:
The default cipher settings in OpenSSL prefer 3DES over AES-128. In
general, Triple DES with three independent keys has a key length of 168
bits, but due to the meet-in-the-middle attack, the effective security
it provides is
From: owner-openssl-users
Sent: Wednesday, December 04, 2013 18:32
On 4 December 2013 22:38, Dave Thompson dthomp...@prinpay.com
wrote:
In addition to the misplaced paren already noted, and also a surplus
paren,
which I'll assume were typos since they wouldn't have compiled,
I think it
On Thu, Dec 05, 2013 at 06:25:46PM +0100, Adnan RIHAN wrote:
I?m the the primary dev, I don?t have *the mysterious* script
which would generate all these cert, is there a way to expand the
validity of existing certificates?
Since I had most of the code lying around, enjoy!
Create a PEM file
Le jeudi 5 décembre 2013 à 21:03, Viktor Dukhovni a écrit :
Since I had most of the code lying around, enjoy!
Thanks :D
Then run the attached program with the pem file as argv[1].
What attachment ? :/
--
Cordialement, Adnan RIHAN.
Directeur-Gérant de Eolis-Software, société de services
On Fri, Dec 06, 2013 at 12:01:13AM +0100, Adnan RIHAN wrote:
Then run the attached program with the pem file as argv[1].
What attachment ?
The uuencoded compressed file in the message body. Some mail
clients recognize inline uuencoded content as an attachment.
Otherwise run the plain-text
I recently became aware of aes-ni and found the linked articles. My CPU
supports this, but it seems (assuming the advice in the linked pages is
accurate) that openssl does not have it enabled. What am I missing? I am
running Arch Linux x86_64 and an using the repo provided package for
Le jeudi 5 décembre 2013 à 18:25, Adnan RIHAN a écrit :
Is there a way to expand the validity of existing certificates?
Obviously, I don’t care if they become unstrusted, I have CAs and signed cert
by these CAs, so the tests will handle that part.
Actually, I’ve also asked on Stackoverflow.
On 5 December 2013 23:32, John da_audioph...@yahoo.com wrote:
I recently became aware of aes-ni and found the linked articles. My CPU
supports this, but it seems (assuming the advice in the linked pages is
accurate) that openssl does not have it enabled. What am I missing? I am
running
On Fri, Dec 06, 2013 at 12:46:35AM +0100, Adnan RIHAN wrote:
Actually, I've also asked on Stackoverflow.
Except that the answer is wrong if you have the private keys of
the issuing CA or you're willing to generate a similar new CA whose
private key you generate. A CA can resign an existing
As I know ,aesni is support after openssl 1.0.1? it is not an engine, and no
kernel module need. It will be enable automatically when you use evp api.
BR
Kane
-Original Message-
From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org]
On Behalf Of John
Sent:
Hello,
can someone give me an example of the certificate, that is used here:
http_port 3128 ssl-bump cert=/etc/squid/cert/cert.pem
I'm using the latest CentOS release (6.5) with squid 3.1.10
I generated one with this:
openssl req -new -newkey rsa:2048 -days 365 -nodes -x509 -subj
13 matches
Mail list logo
