Lost BTC access

You have a fox; you know what a coat looks like.

I provided as much of a manual as there is… it’s an odd problem to expect others to know the answer. Read the manual… https://github.com/bitcoin-wallet/bitcoin-wallet/blob/master/wallet/README.recover.md

What is the encr.txt
Did you try

openssl enc -d -aes-256-cbc -md md5 -a -in key.txt

where key.txt is the U2FsdGVkX1

that will ask you for the decryption password

can equally do

echo “U2FsdGVkX1restofkey” | openssl enc -d -aes-256-cbc -md md5 -a

(do not post any result that looks like a key)

If it works then do it again as

openssl enc -d -aes-256-cbc -md md5 -a -in key.txt > decrypted.txt

to store that result… then you’ll be a step forward.
then do

cat decrypted.txt | tr -cd “[:print:]” | awk ‘{print $1}’

3 Likes

I don’t “expect” anything from anybody. I know so little about this stuff that I didn’t even know it was a complex problem. I just posted a question thinking the answer might be self-evident so somebody more knowledgeable.

I do appreciate even just links to manuals. Please don’t feel offended or unappreciated. It just means I will have to do quite a bit of studying on my own before I can maybe get to the coins. That’s fine and I’ll try to find the time to do it at some point. I enjoy learning new things. Still, the coins are not even mine (at least not in a moral sense), and the value is not huge.

Thank you! I haven’t tried that yet. I will. Maybe tomorrow. Right now I’m pretty busy with other stuff.

(It has taken me quite a bit of time to learn about and practice skinning and tanning too, and I still consider myself a complete novice. I don’t even have a hat yet, just a bunch of practicing skins with missing tails and such hanging around the walls.)

2 Likes

Don’t be lazy. All I’m doing there is parroting what the manual for recovering keys suggests… there is no studying required. You can’t expect other people to put in effort if you will not try the obvious.

What’s obvious to one person isn’t necessarily obvious to another, I’d have thought that was obvious :wink:

2 Likes

Don’t be rude.

9 Likes

Some make out complexity where there is none… the manual is there, just a case of trying it.

Pretending every step is difficult, doesn’t encourage people to try what is possible.

Normalised expectations too are not good… we should expect the positive, willing to try, rather than requiring an industry of support.

1 Like

Well there is that, but in my experience techies are often very bad at explaining things and also assume a certain amount of knowledge that others don’t possess.

I do not have a technical background, but I liked the idea of Linux and open source and thought I’d have a try - this was back in the early 2000s. I was told the open source community was ‘really helpful’ but this was not my experience at all. I got so tired of being directed to impenetrable (to me) man pages that might as well have been written in Greek (I’m not Greek) for all the good they were to me, and if I asked for help I got arrogantly told to go and work it out. There seemed to be an ideological aversion to ‘hand holding’ despite the fact that worked examples and step-throughs are they way we all learn most things.

Pleased to say things have improved considerably since those days and to be a noob still suckling at the teat of M$ is no longer such a heinous crime.

5 Likes

Man pages are still impenetrable in many cases. Just try figuring out how to pull changes from an upstream repo using git man. I did that yesterday, and it wasn’t easy. I found the answer elsewhere.

With cryptography that’s 10x harder, so @davidpbrown IMO you are making unrealistic assumptions about what’s easy or obvious. You’re right that making things out to be hard can be discouraging, but @Sascha wasn’t doing that, he was asking for help, and a way to make this inviting is to provide whatever help is needed - if you are inclined to do so - and to not say anything if you aren’t willing to do that in a helpful and encouraging way.

Just my opinion. I used to be far less helpful than I am now. Receiving help from those who do this well has helped me enormously, so I’ve learned to offer help better and to shut up when I’m thinking exactly the kind of thing you’ve been saying - because it doesn’t help and is discouraging. It discourages the asker and those watching.

3 Likes

fallacy: not this case.

and don’t patronize.

We’re talking about a readme literally titled “Recovering Bitcoins”, for the case suggested.

Again fallacy - that is not the problem … just because bitcoin uses cryptography, doesn’t require the users understand the limits of it.

This is a “how do I recover” query, not more complex than that.

:roll_eyes:

1 Like

How many MAID for a finished shapka-style fox fur hat?

I used to have a genuine Red Army shapka but it got stolen years ago

1 Like

Late 90s- early 00s, I was incredibly fortunate to meet the wonderful guys (and gals) at ScotLUG Scottish Linux User Group who all had their own ways of explaining stuff - some better than others - but all with enthusiasm and a genuine desire to spread knowledge. A very active IRC channel that still exists ScotLUG was the rock on which many successful IT careers were launched.

1 Like

Did you make any headway here @Sascha

1 Like

I haven’t had the time to test even the direct script suggestions @davidpbrown gave me yet. It’s not that urgent, but I’ll try to get to it as soon as I can.

1 Like

A broader internet search wouldn’t be a bad idea either. There’s likely someone, somewhere with exactly your problem that posted the solution. I’m average with computer stuff and discovered that Microsoft laid a trap with Windows 10. You can create a system image, but they got rid of the restore feature. So, I had to manually mount the image to restore after a drive crash. I could have spent days or weeks studying the PowerShell manual. But I found what I was looking for on some message board where the user posted the dozen or so specific steps needed to manually mount the drive. It was not a trivial process by any means. Maybe not the best approach to learning, but it can potentially get you to your destination faster. I can sympathize with just wanting some lines to try entering.

4 Likes

Best way to learn IMNSHO

Break it despair - look on the intrawebs
Fix it
Footer with it
Break it
Fix it
Rinse and repeat

Best way to learn is watch others fail and don’t repeat…
Also, make backups!
but yeah, failing that, cycle through alsorts… the times I’ve broken stuff and found ways to fix, is testament only to how much technology is magic! Recovering broken hard drives is an amazing experience I cannot recommend. Also, make backups!

1 Like

I can - cos I charged some very good money for it on occaision :slight_smile:

I’m trying @davidpbrown’s suggestion, but I don’t understand the output about some arguments possibly being “better”, and I don’t know where to put them.

sascha@Knut:~/Maschas_BTC$ openssl enc -d -aes-256-cbc -md md5 -a -in key.txt
enter aes-256-cbc decryption password:
*** WARNING : deprecated key derivation used.
Using -iter or -pbkdf2 would be better.
bad decrypt

Google throws: encryption - How to solve: WARNING : deprecated key derivation used. Using -iter or -pbkdf2 would be better - Super User

The file was probably encrypted by LibreSSL (using Mac?) and you are decrypting it with OpenSSL (Linux).
You don’t face this problem if you encrypt and decrypt using LibreSSL for both.

also, I don’t know if the answers here can solve it: encryption - OpenSSL 1.1.1b warning: Using -iter or -pbkdf2 would be better while decrypting a file encrypted using OpenSSL 1.1.0g - Unix & Linux Stack Exchange as that might be for creating new and then decrypting rather than decrypting an old instance.

1 Like

And some here wonder why more people haven’t tried bitcoin. Jim Collinson - SAVE US!

7 Likes