Thanks for the information Matt.
Regards
Sandeep
From: Matt Caswell
To: openssl-users@openssl.org
Date: 04/12/2016 12:44 AM
Subject:Re: [openssl-users] Need more information on CVE-2016-2842
Sent by:"openssl-users"
On 11/04/16 19:12, Sandeep Umesh wrote:
> Hello
On 11/04/2016 18:57, Salz, Rich wrote:
You can merge the two files into one. As long as they are in PEM format, it
will just work.
Except when you want more people (usually everybody) access to
the CRT, but few people (usually one or two trusted server
processes) access to the private KEY.
My point was that the -text output would *show* you if
the missing certs were included in the time stamp response
somewhere, and where.
If they are indeed inside the response, then the question
would be why the "openssl ts -verify" command didn't find
them automatically.
If they are not inside t
On 11/04/16 19:12, Sandeep Umesh wrote:
> Hello
>
> Can someone please provide more information on CVE-2016-2842? Is this
> different from CVE-2016-0799 ? Looks like this CVE information is not
> captured in the advisory -
> _http://openssl.org/news/secadv/20160301.txt_
>
> Also, does this belo
Hello
Can someone please provide more information on CVE-2016-2842? Is this
different from CVE-2016-0799 ? Looks like this CVE information is not
captured in the advisory -
http://openssl.org/news/secadv/20160301.txt
Also, does this below patch fixes both CVE-2016-2842 and CVE-2016-0799 -
ht
You can merge the two files into one. As long as they are in PEM format, it
will just work.
--
Senior Architect, Akamai Technologies
IM: richs...@jabber.at Twitter: RichSalz
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Hi All.
Thanks for the help.
The certificate is a ".crt.pem".
Key is a ".key".
Anyhow, earlier I was thinking of saving the certificate+key in a
file, where double-quotes were delimiters.
But, I have rejected that idea; instead saving them in their respective files :)
So, the question becomes o
If you neither know nor care what FIPS 140-2 is, this is your lucky day.
Avert your eyes and move on, nothing to see here.
The entry for the ancestral OpenSSL FIPS Object Module v2.0 validation,
#1747, on the NIST CMVP web site appears to be the victim of some sort
of clerical error:
http://csr
Afternoon,
I have been running some speed tests of openssl 1.0.1, 1.0.2 and 1.1.0
versions against various compiler optimisations. Special interest was given
to the more commonly used primitives, rsa's, aes's etc.
I noticed that SHA1's have some significant performance improvements.
However the m
On Mon, Apr 11, 2016 at 10:01:33AM +0530, Ajay Garg wrote:
[ Subject: Are double-quotes valid characters in certifcates/keys? ]
> Could not find a definitive answer on google, so thought it would be
> best to ask the experts :)
The question is ill-formed. Are you asking about allowed characters
Hi,
It looks like there is issue in handling crypto locks. I encountered
segmentation fault in CRYPTO_add_lock() function referencing NULL pointer.
Please find GDB output below,
(gdb) run ftp://x.x.x.x:sample.txt
Starting program: /App/vikftp ftp://x.x.x.x:sample.txt
Missing separate debuginfo
It's because of the form of the group order for the curves you list.
They look roughly like 2**n + 2**(n/2). So while technically possible
to end up with 161 bits, with overwhelming probability you end up with
less.
BBB
On Wed, Apr 6, 2016 at 9:22 PM, Frode Nilsen wrote:
> Hi,
>
> When printing
Thank you for the responses.
I have implemented encryption that adds a secret key, and secret key id
using:
CMS_add0_recipient_key,
CMS_EncryptData_encrypt,
SMIME_write_CMS
The output file looks correct, but I need to decrypt it back to be sure.
I would like to be able to get the secret key id fr
13 matches
Mail list logo
