On 05/13/2014 02:11 PM, Jeffrey Walton wrote:
> Hi All/Steve,
>
> "Tech giants, chastened by Heartbleed, finally agree to fund OpenSSL",
> http://arstechnica.com/information-technology/2014/04/tech-giants-chastened-by-heartbleed-finally-agree-to-fund-openssl/.
>
> Its been a few weeks since the a
Hi All/Steve,
"Tech giants, chastened by Heartbleed, finally agree to fund OpenSSL",
http://arstechnica.com/information-technology/2014/04/tech-giants-chastened-by-heartbleed-finally-agree-to-fund-openssl/.
Its been a few weeks since the article was written. According to the
article, the Linux Fo
On Tue, May 13, 2014, Tom stone wrote:
> Jeremy,
>
> Thank you for your quick response. I am definitely interested in
> additional details. If you know who I should contact that would be great.
> Do you know whether this only effects simple file encryption or is it
> general to the gcm mode, ie
Hopefully someone else on the list can speak to your further questions….
--Jeremy
On Tue, May 13, 2014 at 12:42 PM, Tom stone wrote:
> Jeremy,
>
> Thank you for your quick response. I am definitely interested in
> additional details. If you know who I should contact that would be great.
> Do
Jeremy,
Thank you for your quick response. I am definitely interested in
additional details. If you know who I should contact that would be great.
Do you know whether this only effects simple file encryption or is it
general to the gcm mode, ie. would it effect tcp/ip traffic?
Thanks
On Tue,
I had exactly this issue a few days ago. Turns out that there's a bug in
setting up the GCM cipher, so the enc part is not working correctly for
GCM. More than that, someone else will have to elaborate if you are
interested.
--Jeremy
On Tue, May 13, 2014 at 12:06 PM, Tom stone wrote:
> Using
Using openssl-1.0.1g command line for simple file encryption/decryption,
when I issue the commands
openssl enc -aes-256-cbc -k secret -in file.txt -out file.ssl
openssl enc -d -aes-256-cbc -k secret -in file.ssl
The contents of file.txt go to stdout as expected. However, when I issue
the commands
The OpenSSL project recently received a donation of US$500 from Nick
Shapley on behalf of Pen Test Partners (http://www.pentestpartners.com/).
Thank you Nick and Pen Test Partners!
-Steve M.
--
Steve Marquess
OpenSSL Software Foundation, Inc.
1829 Mount Ephraim Road
Adamstown, MD 21710
USA
+1
Hi,
Here is a related previous discussion with some more details :
http://openssl.6102.n7.nabble.com/FW-Negotiating-TLS-1-0-from-1-2-td39516.html
Le 13/05/2014 12:45, Gayathri Manoj a écrit :
Hi All,
I am planning to upgrade my tls connection from 1.0 to 1.2. I have
made changes from the cli
On Tue, May 13, 2014 at 6:45 AM, Gayathri Manoj
wrote:
> Hi All,
>
> I am planning to upgrade my tls connection from 1.0 to 1.2. I have made
> changes from the client side and am able to see the client hello with tls
> version 1.2. The server supports only 1.0 and the client is not falling back
>
Can you help me with changing the default MD from SHA1 to SHA256(for Hash
DRBG)? I could not find proper resource.
--
View this message in context:
http://openssl.6102.n7.nabble.com/What-is-the-underlying-algorithm-in-RAND-bytes-function-tp50089p50122.html
Sent from the OpenSSL - User mailing l
Hello.
I'm trying to use high level API provided by OpenSSL for cryptography work.
Here it works pretty well.
/**
* Instructions for generating private key file and self signed certificate
file.
*
* openssl genrsa -des3 -out keys.pem 2048
* openssl rsa -in keys.pem -out rsa.pem
* openssl re
On 05/13/2014 07:54 AM, Michel wrote:
> Hello Steve,
>
> Just for fun :
> And what about these two (attached) logos,
> one for those who donate a little and the other for those who donate a
> lot ?
>
> ;-)
>
Ha, those made me smile. I will pass those on, but I've just received
feedback from the
hi
this code should do the the trick on client side (for the "server" side, just
replace client by "server")
SSL_CTX* ctx = SSL_CTX_new(SSLv23_client_method());
SSL_CTX_set_options(ctx, SSL_OP_NO_SSLv2|SSL_OP_NO_SSLv3);
the SSLv23_client_method() method allows all protocols, then
SSL_CTX_set
Ø I am planning to upgrade my tls connection from 1.0 to 1.2. I have made
changes from the client side and am able to see the client hello with tls
version 1.2. The server supports only 1.0 and the client is not falling back to
1.0 and giving me a fatal that Protocol version alert.
You have t
Hi All,
I am planning to upgrade my tls connection from 1.0 to 1.2. I have made
changes from the client side and am able to see the client hello with tls
version 1.2. The server supports only 1.0 and the client is not falling
back to 1.0 and giving me a fatal that Protocol version alert.
Please
Hi,
I am wondering whether there is already some support for the Maximum
Fragment Length Negotiation TLS extension (as specified in RFC 6066). If
not, are there any plans (or is development work underway) for OpenSSL
to support this?
I note in January of last year that there was activity on the
o
17 matches
Mail list logo
