Content pfp
Content
@
0 reply
0 recast
2 reactions

sudo rm -rf --no-preserve-root / pfp
sudo rm -rf --no-preserve-root /
@pcaversaccio
So, I've been messing around for a few months with private key leaks: I purposely pushed a _Base64-encoded_ private key (with a non-empty balance) into a public GitHub repo (don't worry, it's gone now) to see if the scrapers/drainers are slick enough to catch it. Turns out, they missed it (though they might get better after seeing this lol). Rule number one is still to never save your private keys in files. But if you want do it (DON'T DO IT THO!), throw some fancy encoding (and decoding) on it. It'll probably cover your back for a bit, at least.
3 replies
0 recast
12 reactions

Dean Pierce πŸ‘¨β€πŸ’»πŸŒŽπŸŒ pfp
Dean Pierce πŸ‘¨β€πŸ’»πŸŒŽπŸŒ
@deanpierce.eth
Base64 encryption is uncrackable, got it πŸ‘
0 reply
0 recast
1 reaction

Tim pfp
Tim
@cryptim.eth
So you should not save your keys within a service like last pass?
0 reply
0 recast
1 reaction

Dusman pfp
Dusman
@dusman
Lol, nice experiment dude!
0 reply
0 recast
1 reaction