I wouldn't care, but the problem is I have about 40 accounts with different people all sending coins to specific addresses of mine, and tracking them all down individually and getting them to switch to a new address would be way too much work to prove useful for me.
Fair enough. I just want to make sure that requests are justified for the risks involved. I think a lot of users want to "import" their Bitcoin-Qt wallets because they don't realize the risks, and don't realize that transferring coins is frequently the safest way to transition to a new wallet, especially for experimenting with Armory.
My own experience is that I have a few payout addresses for my miners. If I have to change those addresses, oh well. I didn't realize so many people had such hardened accounts...
Say you open a window that lists all of your private keys (export keys function.) Will Armory record those keys in the log-file? If you send BTC to someone, will it log the transaction amount/etc. in the log-file?
I'm making sure that any variable that ever holds private key data is never written to the log-file, even when there's an error. However, I will serialize all transactions (signed and unsigned) into the logfile. I was kind of concerned about logging that information, but anyone who has access to your system (and thus the log file) already has access to all the transaction information, so it's redundant information.
If this logic doesn't sound right, please let me know. I can still adjust the behavior, or at least make it configurable. I will have a --nologging option to disable it completely..