Thanks Alan for responding, OK I get your points. But if I had Admin privileges and could turn on/off or limit user functions based on login it would be even more useful. Certainly someone compromising the machine as Admin is still a threat (HSM etc would help that as you say).
Here's my scenario: I want a User to be able to create, import, sign, and broadcast multi-sig txns, but not be able to import new public addresses, and not be able to spend single sig from his wallet, or at least only be able to spend to whitelist addresses maintained by Admin. Only Admin can import new public addresses, change whitelist etc. Even better would be daily spending or txn number limits.
Am I missing something? Will pay BTC to someone who wants to consult and figure this out, thx
Going forward, this kind of thing makes sense for us to do. In fact, your comments inspired
this thread, and I think that will be one of the first things we implement when we start figuring out how to better satisfy small-business type use cases. I hadn't considered the idea before that you could make sure the key is encrypted with multiple passwords, thus enabling better access control on consumer hardware as long as there is operational security to back it up.
@PRab
Just fixed the repeated-public-key issue. Will release an update this week that will enable you to sign your transactions back to the faucet
@helgabutters
Thanks so much for the feedback! Especially for all the useful videos showing the bugs! It's been extremely helpful.
I think I fixed most of the issues you identified, except for some of the longstanding sizing issues and quirks running Armory on Linux. Mostly what I've done is I've imposed a maximum character size on all the free-form entry fields (like prom note labels, etc), or limited the number of characters displayed.
With the new lockbox dashboard and a bunch of these quirks fixed, I'll have a new version for you to test midweek and you can collect more bounties.