Armory 0.93 testing release! (with 0.05 BTC bug bounty)

[zombieslayer9099]

I've got a question regarding the secure downloader. Exactly how secure is it? Does it download through encrypted connection? Does it verify signed or hashed files?

[TimS]

I've got a question regarding the secure downloader. Exactly how secure is it?

Very.

Does it download through encrypted connection? Does it verify signed or hashed files?

Yes and yes. announcefetch.py has hardcoded HTTPS URLs with an associated hardcoded public key (the private key to this is kept offline). This URL is a signed message and links to https://s3.amazonaws.com/bitcoinarmory-media/dllinks.txt (including a SHA256 hash), which is another signed message with links to other HTTPS addresses (including SHA256 hashes) that are the actual downloads.
It stores this signed dllinks.txt file in %appdata%\Armory\atisignedannounce\downloads.file.
It is, for all practical purposes (finding a SHA256 collision is not practical, for example), impossible for a man-in-the-middle without that private key to trick you into installing something incorrect/compromised. The HTTPS encryption is not even needed for this sort of setup to be secure (it does improve privacy, etc.), so it doesn't even really matter if you have some shady root certificates loaded.

The easiest way to break it is probably this: A super-user/administrator on your local box could replace your ArmoryQt executable with their own file pointing to their own URLs and public keys. But if they can do that, the main purpose of their replacement ArmoryQt will probably be to simply send your private keys to the creators of the app as soon as you unlock your wallet for a tx. And if you can do that, compromising the Secure Downloader would have limited value.

[goatpig]

TimS: I should have a fix for the missing txio issue sometimes today.

[zombieslayer9099]

I have some feature requests:

I'd like for Armory's coin control feature to display choices based on inputs rather than addresses, and I'd like for it to show more in-depth information regarding inputs, such as priority, source address, TX hash of the origin, and maybe the same thing when sending bitcoins, perhaps a display for the size and priority of the transaction for expert users.

[goatpig]

I have some feature requests:

I'd like for Armory's coin control feature to display choices based on inputs rather than addresses, and I'd like for it to show more in-depth information regarding inputs, such as priority, source address, TX hash of the origin, and maybe the same thing when sending bitcoins, perhaps a display for the size and priority of the transaction for expert users.

That has been on our list for a time, should be done in the coming months, I hope.

[goatpig]

Just pushed the missing txio fix. It will attempt to repair the DB but I don't think I can guarantee proper balance after the repair. It should prevent the issue from reoccurring on top of a clean DB, but again I'm not sure. I'm getting closer to finishing the DB changes so I'm trying to focus on that instead of coming up with a large fix for the current state of supernode.

[opentoe]

Edit: "Rebuild and Rescan Databases" from the Help menu fixed it.

Windows 8.1 x64
I have bitcoin core 0.10 installed and Armory 0.93.0.82 running. I sent a transaction to my Armory wallet from a web wallet. Originally it showed as having received the transaction and 0 confirmations but it never went above 0 confirmations even though online block explorers showed it as having been confirmed many times. Then I realized that Armory shows "connected" in the bottom right but the block count isn't increasing. It is still stuck on block 347509 while current block count shows 347813. But Armory shows as connected and Green.

I ran bitcoin-qt and it showed the correct number of blocks.

I tried "Rescan Databases" from the Help menu but that doesn't seem to have fixed it.

This happened to me to, freaked me out. Saw it in the blockchain, but not the Armory which would show up instantly with no confirmation and eventually turn green. Just never updated. I'll refrain from using the client since there are more bugs now than the previous version. I just hope I don't need to send any coin to anyone for something.

[zombieslayer9099]

There's something that's really started to bother me, and it's the print dialog freezing a split second after opening. I cannot make a backup of my wallet through my printer, I can't even save it as a PDF

I am on Mac OS X 10.10, running Armory 0.93.1

[b00mit]

There's something that's really started to bother me, and it's the print dialog freezing a split second after opening. I cannot make a backup of my wallet through my printer, I can't even save it as a PDF

I am on Mac OS X 10.10, running Armory 0.93.1

I had the same thing happen with the print dialog freezing instantly. However, I was able to print wallet backup.

After the initial print dialog opens and freezes click back on the the "print wallet backup" window and click print again. A new print dialog opened and that allowed me to successfully print my wallet backup. The initial print dialog appears to remain frozen.

[zombieslayer9099]

Transaction details are still broken

[Carlton Banks]

Transaction details are still broken

Yeah, that one's known. Last word from goatpig was that he'd fix most/all of the tx details issues as a part of delivering the complete Database upgrade (we've only had the foundations of that work so far)

[zombieslayer9099]

What's in this database upgrade?

[Carlton Banks]

What's in this database upgrade?

Less database. 120 MB of Armory database per every 35 GB of bitcoin database (i.e. blockchain)

It's an extension of the previous work (apparently).

[goatpig]

It's an extension of the previous work (apparently).

It is. It will also be faster and more stable thanks to some simplification in the architecture.

[Carlton Banks]

It's an extension of the previous work (apparently).

It is. It will also be faster and more stable thanks to some simplification in the architecture.

Hope it makes it into 0.94, looks like there's alot to get into that release.

[goatpig]

It's an extension of the previous work (apparently).

It is. It will also be faster and more stable thanks to some simplification in the architecture.

Hope it makes it into 0.94, looks like there's alot to get into that release.

It's the basis for that release actually.

[Carlton Banks]

And not the new wallet format? You guys are doing a lot of releases soon by the looks of it. I thought python 3 and qt 5 (and gitian...) were also on the table?

[goatpig]

And not the new wallet format? You guys are doing a lot of releases soon by the looks of it. I thought python 3 and qt 5 (and gitian...) were also on the table?

Each one these features is developed in parallel and will have its own separate release version. They are all significant changes under the hood and we won't be releasing them together in order to minimize the bug search effort that follows a new version. As for the release order, it's a matter of which major change is ready first.

I think I'm ahead of the race with the DB changes but that may not hold true in the upcoming weeks. Doug is on Gitian, and Alan is on the new wallets, our new guy (he doesn't have a forum handle yet I think) is on Py3/Qt5. He's got other priorities though, so he's kinda out of the race for now. Place your bets =P

[doug_armory]

And not the new wallet format? You guys are doing a lot of releases soon by the looks of it. I thought python 3 and qt 5 (and gitian...) were also on the table?

Each one these features is developed in parallel and will have its own separate release version. They are all significant changes under the hood and we won't be releasing them together in order to minimize the bug search effort that follows a new version. As for the release order, it's a matter of which major change is ready first.

I think I'm ahead of the race with the DB changes but that may not hold true in the upcoming weeks. Doug is on Gitian, and Alan is on the new wallets, our new guy (he doesn't have a forum handle yet I think) is on Py3/Qt5. He's got other priorities though, so he's kinda out of the race for now. Place your bets =P

Close. I'm working with our new intern on Gitian and Ubuntu 12.04 support, and also doing a bit of Py3/Qt5 work. Here's a quick update regarding how I see things. Keep in mind that we're still scheduling various tasks, so please don't make any assumptions regarding when any of this is coming.

Gitian: Coming along nicely. Been working with theuni to shape a few things and devrandom to squash some bugs in the Gitian code. (We're using Ubuntu 14.04 as the base, which is a bit bleeding edge for Gitian.) I think we're close to having a functional Linux build, if we're not there already. For now, Gitian would only work for Linux. Quite a bit of work remains to be done if we're going to add OS X and/or Windows.
Ubuntu 12.04: After pursuing every possible option, our wonderful intern finally found a reasonable solution that was just pushed. (I forgot to credit him when I pushed it. Sorry, Joseph!) We're discussing our next move right now.
Py3/Qt5: Seems mostly functional on Linux, although there are still some bugs. OS X is kinda functional but needs more TLC, and possibly some attention from the Qt team. (A patch I submitted eight months ago is finally getting traction now that I've confirmed it affects Qt5.) Don't know about Windows. Will get integrated eventually.
Wallet 2.0: Haven't really touched this much recently, although I do have a bit of work to do here eventually. It is coming, I assure all of you!

Never a dull day around here!

[Carlton Banks]

Sounds like you're all doing well. Just wish gitian had a config for Xen, but I guess that's asking alot for such a tool. I'd be interested to hear if it's similar to KVM and/or easy to figure out config for.