string?
Alternately, is there a process for taking an encrypted string, and
"backing in" to the details of how it was created? (ie what algorithm,
etc?)
Thanks,
Chris
On Mon, Jan 15, 2018 at 2:01 PM, Chris B
wrote:
> Hi Daniel,
>
> >Option #1 from the possibilities you m
Hi Daniel,
>Option #1 from the possibilities you mentioned below seems to be the most
logical to me.
Thank you, that's very helpful.
Thanks,
Chris
On Mon, Jan 15, 2018 at 1:29 PM, Sands, Daniel wrote:
> On Sun, 2018-01-14 at 18:26 -0500, Chris B wrote:
>
> Hi Matt,
>
&
s,
Chris
On Sun, Jan 14, 2018 at 6:03 PM, Matt Caswell wrote:
>
>
> 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 a
11:21 AM, Viktor Dukhovni <
openssl-us...@dukhovni.org> wrote:
>
>
> > 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
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_
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
