Thanks for your help. I prefer to err on the side of caution. Before I delete
my plaintext ca.key; I want to be absolutely sure that I get back the exact key
when I decrypt it. I'm a noob with this so I don't want to take any chances.
Thanks again.
> Date: Tue, 6 Jan 2015 23:39:04 +
> Fr
On Tue, Jan 06, 2015 at 05:25:21PM -0600, jack seth wrote:
> Well I ran the command
> openssl asn1parse -in ca.key
>
> I got a bunch of numbers, a hex dump, and something that says 'rsaEncryption'
In that case, this is a PKCS#8 file encoded in PEM. The first
line was probably:
-BE
Well I ran the command
openssl asn1parse -in ca.key
I got a bunch of numbers, a hex dump, and something that says 'rsaEncryption'
but I don't see anything that looks like ASN.1, DER or PEM. You were right
that I want the output to stay the same as the original.
My key is human readable. It do
On 06/01/15 18:29, Steve Marquess wrote:
> But I volunteer to drink it and tell my colleagues how good it was :-)
Its good to see the spirit of Open Source alive and well - with everyone
pitching in to do their bit. :-)
Matt
___
openssl-users mailing
I have implemented a H/W encryption driver and have integrated it with cryptodev. In eng_cryptodev.c there is an array digests[]. In that array it defines CRYPTO_MD5 to have a keylen of 16. In cryptodev, the xform.c file definedes MD5 to have a keylen of 0. Why is the keylen not zero for the
On 01/06/2015 01:21 PM, Jeffrey Walton wrote:
> On Mon, Jan 5, 2015 at 7:10 AM, Matt Caswell wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> We have previously announced our intention to reformat the entire
>> codebase into a more consistent style (see our roadmap document here:
>
On Mon, Jan 5, 2015 at 7:10 AM, Matt Caswell wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> We have previously announced our intention to reformat the entire
> codebase into a more consistent style (see our roadmap document here:
> https://www.openssl.org/about/roadmap.html)
> ...
B
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Matt,
first of all:
THANK YOU!
This has been overdue for ages!
Just a small tweak that would be nice I'd like to see would be to
always have block markers for loops and conditions. The lack of those
was one of the many pitfalls with the old sou
> Starting a few days ago, www.openssl.org when clicking on the Source tab,
> then selecting the GitWeb tab, redirects you to git.openssl.org (probably ok ?
> ) but that page returns the OpenSSL home page (same as www.openssl.org)
> so no web git access.
It wasn't a DNS problem, it was an Apache c
On Tue, Jan 06, 2015, Fred wrote:
> Hi,
>
> I need to decrypt some S/MIME content with an invalid key length
> for the AlgOID specified in the PCKS7 content.
>
> AES-256 is specified as the AlgOID, but a key length of 192 bits is
> being used.
>
> Is there anyway to get openssl to decrypt this
Hi,
I need to decrypt some S/MIME content with an invalid key length for
the AlgOID specified in the PCKS7 content.
AES-256 is specified as the AlgOID, but a key length of 192 bits is
being used.
Is there anyway to get openssl to decrypt this using the openssl smime
command? i.e. override
Just something to help others that use openSSL in Node.js add-ons with recent
Node builds (0.11.15); building node to use the system ssl library (rather than
it's built in copy) appears to make a significant difference to an add-on that
attempts to use the ssl library itself.
Doing this resolve
12 matches
Mail list logo
