Hi Matt,
>If you *are* using 1.1.0 then the default digest was changed between 1.0.2
and 1.1.0.
Awesome thought, but I'm also using 1.0.2:
$ openssl version
OpenSSL 1.0.2k-fips 26 Jan 2017
(I also tried adding -md md5 to the previous command, but I got the same
error message).
Thanks,
Chris
On 14/01/18 15:26, Chris B wrote:
> I'm trying to help someone recover his password for an older format
> ethereum encrypted private key (EPK). My plan has been to use his best
> guess at the password to brute force the actual password.
>
> The EPK is a 132 character string, and it looks somethi
>Any chance this is data corruption?
Brilliant! You caught me. Although this key is encrypted I wasn't
comfortable making it public on the interwebs. So, I randomly changed
several of the characters. If I run openssl base64 -d... on the *actual*
key it does indeed begin with Salted__:
$ opens
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf
> Of Michael Richardson
> Sent: Saturday, January 13, 2018 16:34
>
> > On 12-Jan-2018, at 6:45 PM, Michael Wojcik
> > wrote:
> >> Don't create the BIO immediately. Use getpeername on the socket
> >> descript
> On Jan 14, 2018, at 10:26 AM, Chris B wrote:
>
> I'm trying to help someone recover his password for an older format ethereum
> encrypted private key (EPK). My plan has been to use his best guess at the
> password to brute force the actual password.
>
> The EPK is a 132 character string, a
Hi Rich,
Thank you very much for the reply.
I get the same error message using -aes256 as -aes-256-cbc
/usr/bin/openssl enc -d -aes256 -a -in enc_private_key.txt -out
recovered.key -pass pass:TheBig7ebowski
bad decrypt
140383648536480:error:0606506D:digital envelope
routines:EVP_DecryptFinal_
For CBC the encrypted text will be a multiple of the cipher size. So your use
of CBC is wrong. The quoted post uses aes256; you were using aes-cbc
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
I'm trying to help someone recover his password for an older format
ethereum encrypted private key (EPK). My plan has been to use his best
guess at the password to brute force the actual password.
The EPK is a 132 character string, and it looks something like this:
U2FsdGV0X185M9YAa/27pmEvFzC5pqLI
The combination of (issuer,serial#) is the only way to get a unique identifier
for a certificate. Lots of software depends on certs being uniquely
identifiable. What happens if that assertion is not true? Some things will
break. What? Well, it depends on the software, and which certs are
“
On 01/14/2018 12:07 PM, pratyush parimal wrote:
> I read from several sources that the serial number of a cert MUST be
> unique within a CA. But could someone explain what would happen if the
> serial number was not unique?
Certificate Revocation Lists (CRLs) identify invalid certificates by
mean
Hi everyone,
I read from several sources that the serial number of a cert MUST be
unique within a CA. But could someone explain what would happen if the
serial number was not unique?
Would it cause SSL connections to fail in some manner? I think I'm a little
unclear about the "purpose" of the se
11 matches
Mail list logo
