^ Interesting. So do you have a separate keyboard for the Pi? And doesn't it have a screen attached, you only interact via command line, or what?
Also, would you mind sharing that software? This sounds like something I could set up myself.
It is connected to my monitor, but it's not necessary to view the screen. The Pi server sends messages back to Armory which are then displayed in the UI. For instance "Enter passphrase to unlock wallet", "Invalid passphrase, please re-enter", "Unlocking wallet", etc. The only thing you really need is a separate keyboard plugged into the Pi in order for there to be no possible way your wallet passphrase can be captured by your online computer. What about making the code public? I'd also like to see it, and use it.
I think the idea is that it would become part of the Armory project, usable by anyone. I'm satisfied that it's secure, but before other people use it, it should really be reviewed by someone, ideally etotheipi.
|
|
|
Sure, I'll be in contact with you in the next couple of days. I have the changes committed to a local git branch, so I should be able to pull it out easily enough.
|
|
|
I do. I've got a Raspberry Pi connected to my computer via serial->USB cable. It's had its serial TTY disabled and is running a python script I wrote which listens for ProcolBuffer messages. When it receives a message asking it to sign a transaction, it accepts the wallet's passphrase on its own keyboard, then signs the transaction and passes it back in another PB message. Armory, meanwhile, is also listening for these messages and displays the now signed transaction once it is received and allows me to broadcast it to the network.
|
|
|
Did you see this other thread?
No, but I don't see how that explains the packaging material. I'll ask over there though.
|
|
|
Why did issue 7 come in a 324 cubic inch box and why did I have to pick it up from the post office?
|
|
|
When I try to use Armory with TOR, Armory stays in the Offline mode and says that Bitcoin isn't running--when in fact it is. BTW I'm using Armory 0.87 on a Windows 7 laptop with 8 gigs of RAM. Armory works fine when I use Bitcoin with a commercial VPN. I know this subject was discussed recently on this thread (pp 86-87) but I don't think a definite solution was proposed. Also I'm a real noob--can't write a line of code. Can anyone tell me how they've gotten Armory to work with TOR in a "For Dummies" format. Many thanks.
When you set Bitcoin up to run over Tor, it disables incoming connections, including those coming from localhost. I'm not sure how to fix this without potentially compromising your Tor connection.
|
|
|
Coin Publishing LLC:
What's up with the shipping of the February issue? Mine came in a 12" x 9" x 3" box, and I had to go pick it up at the post office.
|
|
|
Many of the people that paid with BTC last year have now paid multiples of the original purchase price due to this deception and the strength of BTC vs USDs.
And if bitcoin had gone down vs USD, we would have paid merely a fraction. This line of reasoning is not sound. Those who preordered with BTC (including myself) could have mitigated their risk by immediately going out and purchasing BTC to cover the amount at market rate.
|
|
|
Question about offline transactions... what are the system requirements for a computer that would ONLY hold private keys and sign transactions? Nothing special. I run it on a Raspberry Pi. And is there any special setup procedures for such an offline computer? Do I still have to install the Bitcoin-QT client?
Nope, no blockchain or network connection is necessary.
|
|
|
I do this by adding "connect=xxx.xxx.xxx.xxx" to my bitcoin.conf file. It prevents all connections except to the IP addresses specified.
FTFY. You can have as many connect= lines as you need. Adding connect=127.0.0.1 should do the trick. True, I actually have two local instances connected. I tried your suggestion and Armory would still not attempt to go into online mode. Thanks though! That's because listening is disabled with the connect option. I don't think there's any way to allow bitcoin to listen on localhost only, and also connect only to a specified node.
|
|
|
Well, looks like the scammer ran with it. We can still move on if someone sends some coins to this guy... ... If not, I'm out 1btc, but it was a fun experiment. Thanks to everyone who participated ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) Huh? A while ago I offered to give someone a loan while they repurchased the coins and you said that it went against the spirit of the experiment. Did that change? edit... Oh, it wasn't you, it was Fjordbit.
|
|
|
One suggestion and one "bug" report.
Suggestion... sign up for an issue tracking system and link it from the bottom of the page, instead of your support email. This way people reporting bugs or requesting features can see if that bug or feature has already been reported/requested.
Bug... after using the map picker, it changes my city to the name of the area I picked on the map (in this case, Tower Grove East). I see no way to change that back to the more generic St. Louis. It's just a little annoying.
|
|
|
the whole idea of locking in a price doesn't make sense as long as the deal is not binding, which it isn't (anyone can run at any time).
I suggested that the equation to determine the price should be locked in at the time of contact, but the price should fluctuate following that equation until such a time as the buyer and seller both agree on it.
|
|
|
P.S. What's to stop me exploiting this with other sellers, submitting a 'buy' order, then waiting several days to complete it, and getting the coins at an extreme discount vs the current market spot price? My morals and scruples say 'no, don't do that', but it would be good (I think) if your service codified it.
A contact is not a contract to buy at a set price. The seller is free to cancel the deal and make you create a new one.
|
|
|
To enable flashing feature you have to ultimately trust the computer you are performing flashing on. If there was such computer you would not need Trezor at all (speaking of average users not technical savvy people).
I think with the method Mike described, that's not the case. If a virus on the flashing computer attempted to flash a modified version of the firmware, the bootloader would reject it due to an invalid signature. The usual way to implement that is have the locked firmware just contain a bootloader that verifies the signature on the next part of the code, and have that code loaded from reflashable memory. Sometimes the firmware has features like rollback prevention so a bad guy/virus cannot downgrade code to a known vulnerable version.
|
|
|
Didn't the full Chrome extension make the verifier extension obsolete? Anyway, here's the Chrome web store link.
|
|
|
I'd like a traced vector image of this character (no background), in the rageface style. If you are interested, please reply here and also PM me. If someone has already replied, know that I will choose their work if it's completed in a timely manner and is satisfactory. Otherwise, I will choose the one that meets the criteria and has the first reply in the thread. When you are finished, post a thumbnail of the image here, and I will send payment, at which point you should PM me a link to the full image.
|
|
|
1) Do you agree this configuration is equally secure as a configuration in which a dedicated offline system? I'm not etotheipi, but no this is not as secure as an offline computer. You could have a virus on your computer that gathers your wallet information while you are offline and the wallet is unlocked, and then transmits it once the computer is back online. 2) The biggest risk here (but also in the proposed configuration with the dedicated offline system) is keeping the offline wallet files physically secure. Especially as you will want to keep backups (flash storage is frail). Do you agree? I think the scenario I outlined above is a bigger risk. At least with an offline wallet, you know that it cannot be attacked except by someone in the same physical location. 3) Why do you recommend making a paper backup? Personally I really do not trust paper (it decays even faster than any other sort of media). I would like to hear your thoughts because you have obviously put more thought into this than I. You can make archival quality prints, which is I think mostly a function of the paper used. The reason for backing up on paper is that digital media can always fail. Paper is long lasting and easily securable. 4) Finally, atm I already use Armory (although not yet for the majority of my funds) in a configuration with 1 (hot) wallet on a system connected to the internet. I have encrypted the wallet with a very long pass-phrase (>50 characters to give an indication). Will using a offline configuration with a real and watch only wallet really improve my security? What exact use cases do I protect myself against? If you have a virus, it can log your passphrase when you enter it, and then empty your wallet at its convenience. This is impossible with an offline computer keeping your wallet. I recommend the Raspberry Pi. It is cheap, low powered, and eminently hackable.
|
|
|
- Ability to re-negotiate a 'buy' or 'sell' contact after a period of time. Hypothetical example: I have a buyer from a month ago who didn't stay in touch, and now they want to buy. But the contact is fixed at the rate it was a month ago, and doesn't reflect market prices. I'd love to have the option to update the request without cancelling and having the buyer/seller re-send the request. I had a similar idea, but almost backwards from yours. When a contact is made, the rate equation should be locked in place, but the rate itself should keep fluctuating until the buyer and seller both choose to lock the price, at which point the escrow process begins.
|
|
|
you're using Bitcoin-Qt version 0.8, while it works only with older versions like 0.7
Would it be difficult for you to merge the changes from the development branch of Armory? It works perfectly with 0.8, and has a bunch of new features. I was going to try your branch, but didn't want to keep around two separate version of armory with different home directories/wallets.
|
|
|
|