-
Notifications
You must be signed in to change notification settings - Fork 19
Open
Description
I'm trying to get jeeq to work for the first time.
I've generated a throw away address with bitcoind:
$ bitcoind getnewaddress
1k2LVG8jXmRU1Hxjto8UFuKbfYPCJT9oE
$ bitcoind dumpprivkey 1k2LVG8jXmRU1Hxjto8UFuKbfYPCJT9oE
L3BsiJ5LzwrKF7ZLGZBjhaSqMzAMFi4fBBC7RnxRW7xj9kmakGiR
$ bitcoind validateaddress 1k2LVG8jXmRU1Hxjto8UFuKbfYPCJT9oE
{
"isvalid" : true,
"address" : "1k2LVG8jXmRU1Hxjto8UFuKbfYPCJT9oE",
"ismine" : true,
"isscript" : false,
"pubkey" : "038bd796cc06e1c11c8adc5aba0df5a9344b935c5b9165405d63461e79078c7aef",
"iscompressed" : true,
"account" : ""
}
Encryption seems to work OK:
$ ./jeeq.py -e -i ./test.txt -o ./test.enc -k 038bd796cc06e1c11c8adc5aba0df5a9344b935c5b9165405d63461e79078c7aef
Encrypted message to 1k2LVG8jXmRU1Hxjto8UFuKbfYPCJT9oE:
amoAAAICzAN+M/+48D5sDc+xyEp+LW/Mhy+dv2xbfCY6ZFAyUcIyHgN1geIlcapxIQhzp+5Uug8Xl8X9Re7uz+7qtg90E8b6WA==
But decryption fails:
$ ./jeeq.py -d -i ./test.enc -o ./test.dec -k L3BsiJ5LzwrKF7ZLGZBjhaSqMzAMFi4fBBC7RnxRW7xj9kmakGiR
Traceback (most recent call last):
File "./jeeq.py", line 466, in <module>
assert len(private_key)==32, 'Bad private key'
AssertionError: Bad private key
I vaguely feel that I should be using a 'raw' private key in some form, rather than the base58 encoded version.
Is this this case?
If so, how would I get a raw private key from bitcoind?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels