One solution is to save a copy of the Armory source code. You should be able to install it on an old Linux version in a virtual machine in some remote future.
Or just forget about SecurePrint if you are using your own printer (i.e. not a shared office printer). After all, the threat of your printer being pwned with software recognizing an Armory backup and sending it to Mr. Evil is probably quite hypothetical. I like the idea that you can defend against it, but I really doubt that it has ever happened.
Topic: Importing Armory paper wallet backup (Secure Print) without Armory (Read 366 times)
June 19, 2017, 07:36:05 AM
The chain derivation code has not change. SecurePrint encrypts the root key, the derivation code applies on decrypted keys to begin with.
Printing the SecurePrint code is a bit more demanding. You would have to print out the key derivation function code as well as the parameters used and the code providing the initiation vector.
At this rate you are better off dodging SecurePrint and using the fragment backups instead, which just use Shamir's secret sharing to break down the root key into several pieces. You could also grab the raw key, apply some common encryption to it and write down those parameters on the backup (instead of relying on Armory's custom KDF and IV).
Printing the SecurePrint code is a bit more demanding. You would have to print out the key derivation function code as well as the parameters used and the code providing the initiation vector.
At this rate you are better off dodging SecurePrint and using the fragment backups instead, which just use Shamir's secret sharing to break down the root key into several pieces. You could also grab the raw key, apply some common encryption to it and write down those parameters on the backup (instead of relying on Armory's custom KDF and IV).
June 19, 2017, 07:14:20 AM
Hey,
I am currently working on my backup plan and was wondering...
...what if Armory isn't a thing anymore in like 20-30 years and I don't have access to any working version of it either.
I read in this thread that the algorythm is really easy and using regular Armory backups outside of Amory won't be an issue in the future. However, this thread is rather old and SecurePrint wasn't implemented back then.
I'd like to print out the algorythm source code alongside with my backups but I guess the snippet isn't up to date anymore, considering the recent addition of SecurePrint? Wouldn't it be neat to have an optional "print source code" feature built in?
Sure, I could just not use SecurePrint and write down the paper backups by hand. But where is the fun in that
I am currently working on my backup plan and was wondering...
...what if Armory isn't a thing anymore in like 20-30 years and I don't have access to any working version of it either.
I read in this thread that the algorythm is really easy and using regular Armory backups outside of Amory won't be an issue in the future. However, this thread is rather old and SecurePrint wasn't implemented back then.
I'd like to print out the algorythm source code alongside with my backups but I guess the snippet isn't up to date anymore, considering the recent addition of SecurePrint? Wouldn't it be neat to have an optional "print source code" feature built in?
Sure, I could just not use SecurePrint and write down the paper backups by hand. But where is the fun in that
Jump to: