Jonathan
Jonathan
The 240 byte file is the private key, and decrypted OK with the passphrase I had. I'm just curious what the second file 32.2Kb file is. Maybe it's some transaction...
Yes, as per your instructions, thanks! I tipped you some doge to that address in fact.
@louie333 What do you mean "that following spot" exactly?
That will be the name of the file that is the wallet you want to decrypt. For example, I had a file called "doge-wallet-bkp.dat" but yours might be called something...
OK sure. You just need to follow the instructions given here then: https://github.com/langerhans/dogecoin-wallet-new/issues/87#issuecomment-824173384
Yes, so you need to run than openssl command on your wallet file, basically. So if for example your wallet file is called "doge-backup.dat" then you'd run: `openssl enc -d...
Well, the key kinda *is* the wallet really, so you should be OK. Just try that command on the file you have and see if you get the decrypted plain...
Are you using Cygwin? There's some path problem. You're giving it `~/c/Users/Hasti/Desktop/key.txt` but openssl is getting `"C:/Users/Hasti/c/Users/Hasti/Desktop/key.txt"` so it can't find that. Maybe try `in ~/Users/Hasti/Desktop/key.txt ` or just cd...
And when you do an `ls` can you can see `key.txt` or `key2.txt` ? BTW if the command completed successfully you may not see any output - it just creates...
I got this too - but it's because they've changed the file names from `.lasso` to `.txt`: https://www.spamhaus.org/drop/drop.txt https://www.spamhaus.org/drop/edrop.txt Update the script and it works fine.