hous
Member
Offline
Activity: 98
Merit: 10
|
|
May 19, 2013, 09:52:41 PM |
|
Armory has stopped working for me.
|
|
|
|
K1773R
Legendary
Offline
Activity: 1792
Merit: 1008
/dev/null
|
|
May 19, 2013, 09:56:48 PM |
|
Never done this before so I may be missing something, but I'm getting this error: seth@LockBox:~$ git tag -v v0.88.1-beta fatal: Not a git repository (or any of the parent directories): .git seth@LockBox:~$ Even after successfully importing your public key: seth@LockBox:~$ gpg --recv-keys --keyserver keyserver.ubuntu.com 98832223 gpg: requesting key 98832223 from hkp server keyserver.ubuntu.com gpg: key 98832223: public key "Alan C. Reiner (Offline Signing Key) < alan@bitcoinarmory.com>" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) seth@LockBox:~$ your fault. do it in the Armroy git folder and not in your $HOME!
|
[GPG Public Key]BTC/DVC/TRC/FRC: 1 K1773RbXRZVRQSSXe9N6N2MUFERvrdu6y ANC/XPM A K1773RTmRKtvbKBCrUu95UQg5iegrqyeA NMC: N K1773Rzv8b4ugmCgX789PbjewA9fL9Dy1 LTC: L Ki773RBuPepQH8E6Zb1ponoCvgbU7hHmd EMC: E K1773RxUes1HX1YAGMZ1xVYBBRUCqfDoF BQC: b K1773R1APJz4yTgRkmdKQhjhiMyQpJgfN
|
|
|
Daily Anarchist
|
|
May 19, 2013, 10:17:47 PM |
|
Never done this before so I may be missing something, but I'm getting this error: seth@LockBox:~$ git tag -v v0.88.1-beta fatal: Not a git repository (or any of the parent directories): .git seth@LockBox:~$ Even after successfully importing your public key: seth@LockBox:~$ gpg --recv-keys --keyserver keyserver.ubuntu.com 98832223 gpg: requesting key 98832223 from hkp server keyserver.ubuntu.com gpg: key 98832223: public key "Alan C. Reiner (Offline Signing Key) < alan@bitcoinarmory.com>" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) seth@LockBox:~$ your fault. do it in the Armroy git folder and not in your $HOME! Doh! That would make sense. Thank you. I got it to work, but not for the newest version. seth@LockBox:~/BitcoinArmory$ git tag -v v0.87.2-beta object 38fc3a0e805400de987abc32432c64a355dedb2d type commit tag v0.87.2-beta tagger Alan C. Reiner < alan.reiner@gmail.com> 1359008238 -0500 Includes some stability updates on top of v0.87 gpg: Signature made Thu 24 Jan 2013 01:17:38 AM EST using RSA key ID 98832223 gpg: Good signature from "Alan C. Reiner (Offline Signing Key) < alan@bitcoinarmory.com>" gpg: aka "Alan C. Reiner (Armory Signing Key) < etotheipi@gmail.com>" gpg: aka "Alan C. Reiner (Armory Signing Key) < alan.reiner@gmail.com>" gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 821F 1229 36BD D565 366A C36A 4AB1 6AEA 9883 2223 seth@LockBox:~/BitcoinArmory$ git tag -v v0.88.1-beta error: tag 'v0.88.1-beta' not found. seth@LockBox:~/BitcoinArmory$
|
|
|
|
K1773R
Legendary
Offline
Activity: 1792
Merit: 1008
/dev/null
|
|
May 19, 2013, 10:23:56 PM |
|
Never done this before so I may be missing something, but I'm getting this error: seth@LockBox:~$ git tag -v v0.88.1-beta fatal: Not a git repository (or any of the parent directories): .git seth@LockBox:~$ Even after successfully importing your public key: seth@LockBox:~$ gpg --recv-keys --keyserver keyserver.ubuntu.com 98832223 gpg: requesting key 98832223 from hkp server keyserver.ubuntu.com gpg: key 98832223: public key "Alan C. Reiner (Offline Signing Key) < alan@bitcoinarmory.com>" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) seth@LockBox:~$ your fault. do it in the Armroy git folder and not in your $HOME! Doh! That would make sense. Thank you. I got it to work, but not for the newest version. seth@LockBox:~/BitcoinArmory$ git tag -v v0.87.2-beta object 38fc3a0e805400de987abc32432c64a355dedb2d type commit tag v0.87.2-beta tagger Alan C. Reiner < alan.reiner@gmail.com> 1359008238 -0500 Includes some stability updates on top of v0.87 gpg: Signature made Thu 24 Jan 2013 01:17:38 AM EST using RSA key ID 98832223 gpg: Good signature from "Alan C. Reiner (Offline Signing Key) < alan@bitcoinarmory.com>" gpg: aka "Alan C. Reiner (Armory Signing Key) < etotheipi@gmail.com>" gpg: aka "Alan C. Reiner (Armory Signing Key) < alan.reiner@gmail.com>" gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 821F 1229 36BD D565 366A C36A 4AB1 6AEA 9883 2223 seth@LockBox:~/BitcoinArmory$ git tag -v v0.88.1-beta error: tag 'v0.88.1-beta' not found. seth@LockBox:~/BitcoinArmory$ its working! gpg: WARNING: This key is not certified with a trusted signature! is just saying you didnt trust this key
|
[GPG Public Key]BTC/DVC/TRC/FRC: 1 K1773RbXRZVRQSSXe9N6N2MUFERvrdu6y ANC/XPM A K1773RTmRKtvbKBCrUu95UQg5iegrqyeA NMC: N K1773Rzv8b4ugmCgX789PbjewA9fL9Dy1 LTC: L Ki773RBuPepQH8E6Zb1ponoCvgbU7hHmd EMC: E K1773RxUes1HX1YAGMZ1xVYBBRUCqfDoF BQC: b K1773R1APJz4yTgRkmdKQhjhiMyQpJgfN
|
|
|
Daily Anarchist
|
|
May 19, 2013, 10:25:00 PM |
|
Never done this before so I may be missing something, but I'm getting this error: seth@LockBox:~$ git tag -v v0.88.1-beta fatal: Not a git repository (or any of the parent directories): .git seth@LockBox:~$ Even after successfully importing your public key: seth@LockBox:~$ gpg --recv-keys --keyserver keyserver.ubuntu.com 98832223 gpg: requesting key 98832223 from hkp server keyserver.ubuntu.com gpg: key 98832223: public key "Alan C. Reiner (Offline Signing Key) < alan@bitcoinarmory.com>" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) seth@LockBox:~$ your fault. do it in the Armroy git folder and not in your $HOME! Doh! That would make sense. Thank you. I got it to work, but not for the newest version. seth@LockBox:~/BitcoinArmory$ git tag -v v0.87.2-beta object 38fc3a0e805400de987abc32432c64a355dedb2d type commit tag v0.87.2-beta tagger Alan C. Reiner < alan.reiner@gmail.com> 1359008238 -0500 Includes some stability updates on top of v0.87 gpg: Signature made Thu 24 Jan 2013 01:17:38 AM EST using RSA key ID 98832223 gpg: Good signature from "Alan C. Reiner (Offline Signing Key) < alan@bitcoinarmory.com>" gpg: aka "Alan C. Reiner (Armory Signing Key) < etotheipi@gmail.com>" gpg: aka "Alan C. Reiner (Armory Signing Key) < alan.reiner@gmail.com>" gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 821F 1229 36BD D565 366A C36A 4AB1 6AEA 9883 2223 seth@LockBox:~/BitcoinArmory$ git tag -v v0.88.1-beta error: tag 'v0.88.1-beta' not found. seth@LockBox:~/BitcoinArmory$ its working! gpg: WARNING: This key is not certified with a trusted signature! is just saying you didnt trust this key This is the part I'm talking about: seth@LockBox:~/BitcoinArmory$ git tag -v v0.88.1-beta error: tag 'v0.88.1-beta' not found. seth@LockBox:~/BitcoinArmory$
|
|
|
|
K1773R
Legendary
Offline
Activity: 1792
Merit: 1008
/dev/null
|
|
May 19, 2013, 11:01:53 PM |
|
Never done this before so I may be missing something, but I'm getting this error: seth@LockBox:~$ git tag -v v0.88.1-beta fatal: Not a git repository (or any of the parent directories): .git seth@LockBox:~$ Even after successfully importing your public key: seth@LockBox:~$ gpg --recv-keys --keyserver keyserver.ubuntu.com 98832223 gpg: requesting key 98832223 from hkp server keyserver.ubuntu.com gpg: key 98832223: public key "Alan C. Reiner (Offline Signing Key) < alan@bitcoinarmory.com>" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) seth@LockBox:~$ your fault. do it in the Armroy git folder and not in your $HOME! Doh! That would make sense. Thank you. I got it to work, but not for the newest version. seth@LockBox:~/BitcoinArmory$ git tag -v v0.87.2-beta object 38fc3a0e805400de987abc32432c64a355dedb2d type commit tag v0.87.2-beta tagger Alan C. Reiner < alan.reiner@gmail.com> 1359008238 -0500 Includes some stability updates on top of v0.87 gpg: Signature made Thu 24 Jan 2013 01:17:38 AM EST using RSA key ID 98832223 gpg: Good signature from "Alan C. Reiner (Offline Signing Key) < alan@bitcoinarmory.com>" gpg: aka "Alan C. Reiner (Armory Signing Key) < etotheipi@gmail.com>" gpg: aka "Alan C. Reiner (Armory Signing Key) < alan.reiner@gmail.com>" gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 821F 1229 36BD D565 366A C36A 4AB1 6AEA 9883 2223 seth@LockBox:~/BitcoinArmory$ git tag -v v0.88.1-beta error: tag 'v0.88.1-beta' not found. seth@LockBox:~/BitcoinArmory$ its working! gpg: WARNING: This key is not certified with a trusted signature! is just saying you didnt trust this key This is the part I'm talking about: seth@LockBox:~/BitcoinArmory$ git tag -v v0.88.1-beta error: tag 'v0.88.1-beta' not found. seth@LockBox:~/BitcoinArmory$ thats because no such tag exists
|
[GPG Public Key]BTC/DVC/TRC/FRC: 1 K1773RbXRZVRQSSXe9N6N2MUFERvrdu6y ANC/XPM A K1773RTmRKtvbKBCrUu95UQg5iegrqyeA NMC: N K1773Rzv8b4ugmCgX789PbjewA9fL9Dy1 LTC: L Ki773RBuPepQH8E6Zb1ponoCvgbU7hHmd EMC: E K1773RxUes1HX1YAGMZ1xVYBBRUCqfDoF BQC: b K1773R1APJz4yTgRkmdKQhjhiMyQpJgfN
|
|
|
Rave
|
|
May 20, 2013, 03:37:38 AM |
|
This damn wallet doesn't work anymore! It was running fine last week but now it crashes before it even start's up. I already went to the website and downloaded the latest 64Bit version (Windows). Same problem. I need access to my coins. This sucks!!!!!!!!!!!!!!!!!!
Edit: I've installed the Linux version in a VM and loaded the backups. Got my coins back...it still sucks -.-
|
|
|
|
K1773R
Legendary
Offline
Activity: 1792
Merit: 1008
/dev/null
|
|
May 20, 2013, 03:45:24 AM |
|
This damn wallet doesn't work anymore! It was running fine last week but now it crashes before it even start's up. I already went to the website and downloaded the latest 64Bit version (Windows). Same problem. I need access to my coins. This sucks!!!!!!!!!!!!!!!!!!
Edit: I've installed the Linux version in a VM and loaded the backups. Got my coins back...it still sucks -.-
there you go, its a good solution to DITCH a deprecated OS.
|
[GPG Public Key]BTC/DVC/TRC/FRC: 1 K1773RbXRZVRQSSXe9N6N2MUFERvrdu6y ANC/XPM A K1773RTmRKtvbKBCrUu95UQg5iegrqyeA NMC: N K1773Rzv8b4ugmCgX789PbjewA9fL9Dy1 LTC: L Ki773RBuPepQH8E6Zb1ponoCvgbU7hHmd EMC: E K1773RxUes1HX1YAGMZ1xVYBBRUCqfDoF BQC: b K1773R1APJz4yTgRkmdKQhjhiMyQpJgfN
|
|
|
Daily Anarchist
|
|
May 21, 2013, 03:07:33 AM |
|
I switched from Ubuntu to Debian this weekend and tried to recompile Armory. It failed, of course. I didn't need to install any extra packages this time but I did need to edit line 15 to:
PYVER += 2.7
I got rid of all that other junk because it just wasn't working, and I know what python version I'm running, so I can just plug it in manually.
|
|
|
|
etotheipi (OP)
Legendary
Offline
Activity: 1428
Merit: 1093
Core Armory Developer
|
|
May 21, 2013, 01:37:56 PM |
|
I switched from Ubuntu to Debian this weekend and tried to recompile Armory. It failed, of course. I didn't need to install any extra packages this time but I did need to edit line 15 to:
PYVER += 2.7
I got rid of all that other junk because it just wasn't working, and I know what python version I'm running, so I can just plug it in manually.
I should start a bounty to have someone with real Makefile experience rework that Makefile. I know it sucks. It works on Ubuntu 12.10-, and requires only small deviations for other OS, but I don't know how to do it "right". The only issue appears to be python-dev. In Ubuntu 13.04, the files end up somewhere unexpected. In other OS, the static library is not available. But I need it to compile the static library when available, for distribution purposes (or else it fails to start on many systems when installed from my .deb). If it doesn't do that by default, I'll inevitably create non-working .deb packages and go through the whole release process not realizing I did it. So, anyone want 0.5 BTC? This can't possibly take a long time to do, it just needs someone who has any experience with Makefiles. If the python-dev library is already installed, it should (1) Try to compile using the static library (.a), (2) If the static library is not available, just use the dynamic (.so) library, and (3) Do so in the "correct" manner to find these things, not hardcoding paths as I have basically done.
|
|
|
|
chrisrico
|
|
May 21, 2013, 03:58:13 PM |
|
I should start a bounty to have someone with real Makefile experience rework that Makefile. I know it sucks. It works on Ubuntu 12.10-, and requires only small deviations for other OS, but I don't know how to do it "right". Instead of a bounty, how about the model Gavin (or was it Jeff) mentioned during one of the panels... find someone who can do it and contract directly with them. If you give a price that it's worth for you, I'm sure someone around here knows a makefile expert who would be interested. Maybe you could offer a tiny bounty for the first person to get you in contact with a makefile developer who contracts with you. At least that's a simple and well defined requirement. Or maybe I'm over thinking this and a bounty would work fine for this purpose.
|
|
|
|
etotheipi (OP)
Legendary
Offline
Activity: 1428
Merit: 1093
Core Armory Developer
|
|
May 21, 2013, 04:07:23 PM |
|
I should start a bounty to have someone with real Makefile experience rework that Makefile. I know it sucks. It works on Ubuntu 12.10-, and requires only small deviations for other OS, but I don't know how to do it "right". Instead of a bounty, how about the model Gavin (or was it Jeff) mentioned during one of the panels... find someone who can do it and contract directly with them. If you give a price that it's worth for you, I'm sure someone around here knows a makefile expert who would be interested. Maybe you could offer a tiny bounty for the first person to get you in contact with a makefile developer who contracts with you. At least that's a simple and well defined requirement. I am in total agreement with Gavin about this. For anything substantial, bounties are a really terrible way to get work done. However, I have actually had great success with bounties for things like this, which are (1) Extremely well-defined (2) A trivial amount of effort for someone knowledgeable (1-3 days) (3) I'm the only one offering the bounty and I decide (not by consensus) who gets it, and I'm not a stickler about it. For anything that is more than a couple day's work and without well-defined exit criteria, bounties are a terrible way to go. Especially when it's a long project and project direction could change mid-way, etc. In this case, it's clear what needs to happen, and if I end up with something that's not exactly right, I'll still pay the 0.5 BTC.
|
|
|
|
Rampion
Legendary
Offline
Activity: 1148
Merit: 1018
|
|
May 21, 2013, 04:36:34 PM |
|
Sorry for this off-topic question.
I use Armory offline in Ubuntu 10.04, and I did not update my offline bundle to the latest version - is this a problem? What benefits would I get from upgrading?
Thanks
|
|
|
|
etotheipi (OP)
Legendary
Offline
Activity: 1428
Merit: 1093
Core Armory Developer
|
|
May 21, 2013, 04:39:37 PM |
|
Sorry for this off-topic question.
I use Armory offline in Ubuntu 10.04, and I did not update my offline bundle to the latest version - is this a problem? What benefits would I get from upgrading?
Thanks
The subset of features used in offline mode are rarely updated. I change some of the flow (try to remove unnecessary question boxes), and add a couple convenience features, but nothing you need. There won't be a "required" update of the offline computer until the new wallet format is implemented, but that may actually still work fine with old wallets -- only needed for new wallets.
|
|
|
|
Rampion
Legendary
Offline
Activity: 1148
Merit: 1018
|
|
May 21, 2013, 04:44:31 PM |
|
Sorry for this off-topic question.
I use Armory offline in Ubuntu 10.04, and I did not update my offline bundle to the latest version - is this a problem? What benefits would I get from upgrading?
Thanks
The subset of features used in offline mode are rarely updated. I change some of the flow (try to remove unnecessary question boxes), and add a couple convenience features, but nothing you need. There won't be a "required" update of the offline computer until the new wallet format is implemented, but that may actually still work fine with old wallets -- only needed for new wallets. I know we all tell you this every day, but thank you very much for the awesome work you are doing. Armory is the absolute best piece of software to manage Bitcoins, and the support you provide is 10000000000 times better than the support provided for 99% of commercial software. I procrastinated a very much deserved donation to Armory too long - I'm doing it ASAP!
|
|
|
|
cypherdoc
Legendary
Offline
Activity: 1764
Merit: 1002
|
|
May 21, 2013, 04:46:12 PM |
|
Sorry for this off-topic question.
I use Armory offline in Ubuntu 10.04, and I did not update my offline bundle to the latest version - is this a problem? What benefits would I get from upgrading?
Thanks
The subset of features used in offline mode are rarely updated. I change some of the flow (try to remove unnecessary question boxes), and add a couple convenience features, but nothing you need. There won't be a "required" update of the offline computer until the new wallet format is implemented, but that may actually still work fine with old wallets -- only needed for new wallets. I know we all tell you this every day, but thank you very much for the awesome work you are doing. Armory is the absolute best piece of software to manage Bitcoins, and the support you provide is 10000000000 times better than the support provided for 99% of commercial software. I procrastinated a very much deserved donation to Armory too long - I'm doing it ASAP! totally agree. i also met Alan over the weekend for the first time and he's as nice in person as he is here. totally expected.
|
|
|
|
drrussellshane
|
|
May 21, 2013, 07:08:03 PM |
|
I would also like to pass along my gratitude!
Armory is great!
|
Buy a TREZOR! Premier BTC hardware wallet. If you're reading this, you should probably buy one if you don't already have one. You'll thank me later.
|
|
|
LvM
|
|
May 21, 2013, 07:43:44 PM |
|
That kind of 2-factor auth requires a centralized server. Anything that I implement using, say, google-auth, would be purely security theatre. It would add 2-factor auth for you using Armory, but someone who steals your wallet file wouldn't need it. It's because the network doesn't care about google-auth.
However, if I ever get back to the new wallets, I will be implementing two-factor auth using multi-sig network scripts. Then your phone would also have a bitcoin wallet, and the network would expect to see a signature from both.
Welcome back! In BTC the usage of "private keys" only (PINs) is a severe security hole indeed. That's why normal banks demand PIN and TAN for each transaction (2-factor). The TAN is often transmitted by SMS: mTAN = mobile TransActionNumber. This method is fast, due to its second way extremely secure and easy to use. No "google-auth". Some BTC markets (Bitcoin.de) provide the same (PIN + mTAN) for the online wallets of their costumers. Easy and efficient. Enough to enter a SMS-capable phone number and we are quite sure there. You might call it a centralized server. For local wallets this cannot be done by changing the blockchain adding the phone somehow to the private keys. Impossible for the so called peers/nodes/clients/miners to call such a number if needed to validate a tx. And a thief of private keys (stolen wallet) might be able to change a changeable phone number... So SMS-mTAN or other 2-factor-auth seems not possible in the public p2p blockchain case. I looked at etotheipis BIP draft #10 Multi-Sig Transaction Distribution, created: 28-10-2011 https://en.bitcoin.it/wiki/BIP_0010Since (also in the example) writing there only about transactions "with more than one recipient address" I did not understand it. IMHO one or more signatures are needed for disposals of the owner/sender only and always, regardless which and how many recipients/transactions. What we could do insofar with Armorys online/offline wallets is within the private sphere quite another thing. Could be provided by any user-client-app. Blockchain not involved.
|
|
|
|
Daily Anarchist
|
|
May 21, 2013, 10:24:22 PM |
|
I switched from Ubuntu to Debian this weekend and tried to recompile Armory. It failed, of course. I didn't need to install any extra packages this time but I did need to edit line 15 to:
PYVER += 2.7
I got rid of all that other junk because it just wasn't working, and I know what python version I'm running, so I can just plug it in manually.
I should start a bounty to have someone with real Makefile experience rework that Makefile. I know it sucks. It works on Ubuntu 12.10-, and requires only small deviations for other OS, but I don't know how to do it "right". The only issue appears to be python-dev. In Ubuntu 13.04, the files end up somewhere unexpected. In other OS, the static library is not available. But I need it to compile the static library when available, for distribution purposes (or else it fails to start on many systems when installed from my .deb). If it doesn't do that by default, I'll inevitably create non-working .deb packages and go through the whole release process not realizing I did it. So, anyone want 0.5 BTC? This can't possibly take a long time to do, it just needs someone who has any experience with Makefiles. If the python-dev library is already installed, it should (1) Try to compile using the static library (.a), (2) If the static library is not available, just use the dynamic (.so) library, and (3) Do so in the "correct" manner to find these things, not hardcoding paths as I have basically done. I really like the way bounties are handled at i2p project: http://www.i2p2.de/bounties.htmlMaybe a page like that would be cool. You could make a list of things that need to get done. Users like myself can donate to the bounties they are most interested in. Devs currently working on the project get listed, including collaborative projects. And once it makes it to the client the devs get paid. Seems very efficient to me.
|
|
|
|
marcus_of_augustus
Legendary
Offline
Activity: 3920
Merit: 2349
Eadem mutata resurgo
|
|
May 21, 2013, 11:31:38 PM |
|
I can do makefile stuff ...
|
|
|
|
|