Hodie V Id. Aug. MMX, Erwann ABALEA scripsit:
[...]
> This is not possible, as the ciphersuites defined by RFC5246 all
> use P_SHA256 as the PRF (paragraph 1.2).
> In paragraph 5, it is said "New cipher suites MUST explicitely specify
> a PRF and, in general, SHOULD use the TLS PRF with SHA-256 or
Hodie V Id. Aug. MMX, Jakob Bohm scripsit:
> On 08-08-2010 01:13, Dr. Stephen Henson wrote:
[...]
> >It depends on what you mean by "in". Support for SHA-2 algorithms is in
> >OpenSSL 0.9.8 and later. The algorithm can be used in certificates and CMS
> >for
> >example.
> >
> >Since OpenSSL doesn't
Jakob Bohm wrote:
I believe this is an unfortunate reading of the RFCs. Fundamentally,
the SSL3/TLS protocols do not tie the availability of a cipher suite to
the version of the protocol document which was current when it was
introduced. The fact that the most common cipher suites are defined in
Hi guys,
I have a software that needs to read a file. This file contains importantdata
and I need something to hide this data.I was thinking to use openssl
to cryptography this file but I don't know how to do this.
Do you have some examples of how to use openssl to do this?Software will run on
I think i found the answer to this. The responsibility is lied within
the application.
The app should setup its own list of locks, possibly above and beyond
the CRYPTO_NUM_LOCKS.
And then provide appropriate routines to pass to the following:
CRYPTO_set_locking_callback
CRYPTO_set_dynlock_
On 08-08-2010 01:13, Dr. Stephen Henson wrote:
On Fri, Aug 06, 2010, Alex Chen wrote:
Is SHA-2 supported in OpenSSL 1.0 or the latest version?
From my search in Google, I found the following entry in openssl-dev mailing
list:
List: openssl-dev
Subject:Re: SHA-2 support in openssl?
In my engine, i'd like to use a new lock for a set of operations. This
lock is not CRYPTO_LOCK_ENGINE or any other defined ones.
Is there any way in OpenSSL to define a say user lock (type) and then
use CRYPTO_Lock function on it?
What would happen to CRYPTO_NUM_LOCKS? would that increase by way o
On Mon, Aug 09, 2010, Bram Cymet wrote:
> Ok I see it now.
>
> The whole structure is there asn1parse just can't print out the
> GENERALSTRINGs I changed them to UTF8 and I was able to see everything.
>
Yes that's a current limitation/bug, I'll fix OpenSSL so it does print out
GENERALSTRINGS
Ok I see it now.
The whole structure is there asn1parse just can't print out the GENERALSTRINGs
I changed them to UTF8 and I was able to see everything.
Thanks again,
Bram
On 2010-08-09, at 6:51 AM, Bram Cymet wrote:
> Ok I was able to get openssl to generate a cert. Now when I got to asn1
Ok I was able to get openssl to generate a cert. Now when I got to asn1parse
-strparse the Subject Alternative Name I get:
0:d=0 hl=2 l= 47 cons: SEQUENCE
2:d=1 hl=2 l= 45 cons: cont [ 0 ]
4:d=2 hl=2 l= 6 prim: OBJECT:1.3.6.1.5.2.2
12:d=2 hl=2
Estaré ausente de la oficina desde el 09/08/2010 y no volveré hasta el
30/08/2010.
Para cualquier consulta, poneos en contacto con Rafael Martinez Ramon,
Sergio Castaños Rebollo o Álvaro Díaz González.
___
Este mensaje se
Hi all.I'm using OpenSSL 1.0.0a and I need to produce some different kinds of
signed PKCS7; in particular, I'm trying hard to change the signature algorithm
to sha256-with-rsa (sha256WithRSAEncryption, OID.1.2.840.113549.1.1.11).The
output (parsed with asn1parse command) shall be like in the fol
12 matches
Mail list logo
