Am 23.02.16 um 18:26 schrieb Dr. Stephen Henson:
On Tue, Feb 23, 2016, Stephan M?hlstrasser wrote:
...
So yes it's pretty broken.
Steve.
Thank you for taking the time to analyse this, Steve.
--
Stephan
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/op
Hi Steve,
Thanks. Yes I first built it using the standard way (./config fips shared)
and it went fine.
It's just when I switched to using the debian/ ubuntu build script (which
generated a slightly different Makefile compared to the standard one).
Not sure what could cause this problem.
I also r
>
> Hi Team,
>
> I am trying to build 'openssl-1.0.2f' on my Ubuntu 14.04 and I end up
> seeing the "
> Error: no such instruction: `vpclmulqdq $0,%xmm6,%xmm14,%xmm0'" errors on
> my machine(Please see the complete error at the end of this mail.).
>
> The o/p of uname is as below:
>
> ---
>
On Tue, Feb 23, 2016, cloud force wrote:
> Hi All:
>
> I built the FIPS modules on Ubuntu platform and was trying to build the
> FIPS capable OpenSSL library.
>
> The build went fine but when I ran the following test, the fingerprint
> error showed up:
>
> *OPENSSL_FIPS=1 openssl md5*
>
I sug
Hi All:
I built the FIPS modules on Ubuntu platform and was trying to build the
FIPS capable OpenSSL library.
The build went fine but when I ran the following test, the fingerprint
error showed up:
*OPENSSL_FIPS=1 openssl md5*
*139728296724128:error:2D06B06F:FIPS
routines:FIPS_check_incore_fi
On Tue, Feb 23, 2016, Stephan M?hlstrasser wrote:
> I tried again to map the structure of the CMS object to the
> definitions in RFC 5652 (comments added with a '%'):
>
> 1: SEQUENCE {
> 2: OBJECT IDENTIFIER envelopedData (1 2 840 113549 1 7 3)
>
All,
I toyed over the weekend with resurrecting CHIL: intermediate result here
https://github.com/sctemme/openssl/tree/rescue-chil and I AM NOT PROUD OF THIS
but have no cycles to clean it up for at least a couple of days to come. It
builds now but doesn't work: my privkey loading routine doesn
Apparently it is OpenSSL bug/ticket number 2288.
Hopefully fixed sometime...
Regards,
David
On 12 February 2016 at 18:09, David Balažic wrote:
> Hi!
>
> Tomcat released version 8.0.32 which bundles OpenSSL 1.0.2e (see below)
> The issue remains (with the change that now IE can not connect at all
Thanks. I'll try it then.
2016-02-23 14:15 GMT+01:00 Salz, Rich :
> It will probably work for your needs.
>
> --
> openssl-users mailing list
> To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
>
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/l
It will probably work for your needs.
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
I saw there are a couple of "pre" tags for the 1.1 version. I need those
cipher suites only to be able to interact with a specific device and the
security is not important since it is only for testing purposes, where the
transport is not the subject of testing. Will the "OpenSSL_1_1_0-pre3" be
enou
Am 23.02.16 um 14:04 schrieb Dr. Stephen Henson:
On Tue, Feb 23, 2016, Stephan M?hlstrasser wrote:
Am 09.02.16 um 16:39 schrieb Erwann Abalea:
Bonjour Stephan,
...
PKCS#7 and CMS are pretty much interchangeable.
Here, your file is strictly not a PKCS#7v1.5, because in this version,
Recipient
On Tue, Feb 23, 2016, Stephan M?hlstrasser wrote:
> Am 09.02.16 um 16:39 schrieb Erwann Abalea:
> >Bonjour Stephan,
> >
> >...
> >
> >PKCS#7 and CMS are pretty much interchangeable.
> >Here, your file is strictly not a PKCS#7v1.5, because in this version,
> >RecipientInfo wasn?t a CHOICE (see RFC2
> Please could you explain which stable code should I use to have those cipher
> suites?
Master, which will be 1.1 It's not done yet.
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Hi,
I looking for OpenSSL version that supports the following cipher suites:
ECDHE-PSK-AES128-CBC-SHA256
DHE-PSK-AES128-CCM8
I've looked through the history of the "include\openssl\tls1.h" file where
they are declared in the current master branch, and found out they were
introduced in commit ea6
Am 09.02.16 um 16:39 schrieb Erwann Abalea:
Bonjour Stephan,
...
PKCS#7 and CMS are pretty much interchangeable.
Here, your file is strictly not a PKCS#7v1.5, because in this version,
RecipientInfo wasn’t a CHOICE (see RFC2315 to see PKCS#7v1.5 definitions).
How did you generate this structure
16 matches
Mail list logo