Jeff Garzik linked to this article suggesting older (18.04) Ubuntu encrypted disks might be vulnerable to brute-force attacks:

https://mjg59.dreamwidth.org/66429.html

A fresh install of a later distro (22.04?) would seem to plug the possible vulnerability.

Does Armory offline run on Ubuntu 22.04?

In passing, this made me wonder if the Armory transaction-signing / key-exposing password has any anti brute-forcing mitigations? Could a 20+ mixed character password still survive today's attacks?

I've been using the low fees of the last few days to move some balances into new segwit addresses. I'm using 0.96.3.992 on Ubuntu 16.04 for both online and offline.

Usually the offline signer confirms that receiving address is indeed in one of my wallets, but this last time it didn't, just listing the 3... destination address. I thought this unusual. I haven't yet figured out how to get the offline to list the wallet segwit addresses ("preferred receive address type" has P2SH-P2WPKH greyed out) so I started up my mirror online machine (not great practice I know, but I like to have one working machine during upgrade procedures). On this "machine B", which is as far as I know identical to the "machine A" that generated the transaction, and has up to now has shown the same many transactions and addresses, the wallet's unused segwit addresses are completely different! I abandoned that tx. A test tx generated on machine B did have the offline machine recognise the segwit receiving address.

I'm worried that somehow machine A has had its receiving addresses replaced by external ones to which I do not have the keys. Surely this isn't possible?

Obviously I can delete and rebuild online machine A, but should I look into this further?

Happily running 96.2 on the online machine. I'd like to start using segwit addresses, but just want to check that my offline 93.3 can sign segwit transactions ok? or would the offline need upgrading as well? Thanks.

When sending coins from 0.96 (Ubuntu) there seems to be a bug in the fee options: if you opt to set your own fee/Byte (as opposed to the recommended), then the chosen amount seems to be reduced by a factor of 10 when actually applied to the transaction. That is, choose 300 sats/B and only 30 sats/B is applied.

Firstly, many thanks to goatpig and the team for continuing with Armory. I've happily been using it as my wallet since 0.88 and have quite enjoyed the tweaking needed to keep it running through the years. I'll be happy to donate when you're ready.

Now running 0.96 with 0.14.1 on unbuntu 14.04, 64bit, 8GB RAM.

When started from re-boot, Armory now always hangs on "Preparing Databases" (with the 2 orange progress bars). When Armory is quitted, it leaves ArmoryDB and bitcoind running. It can't then be re-started until I End Process ArmoryDB and (surprisingly) bitcoind using System Monitor. After that, it will start up fine and quickly be running properly.

After quitting Armory at this point it also properly closes both ArmoryDB and bitcoind.

So it's annoying rather than critical, and I'm really just reporting it rather than screaming for help. It does happen reproducibly, every time I start the machine. I should say that I have exactly (AFAIK) the same setup running in a (Parallels) virtual machine without any problems.