Bitcoin Forum
March 19, 2024, 02:20:03 AM *
News: Latest Bitcoin Core release: 26.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 [180] 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 »
  Print  
Author Topic: Armory - Discussion Thread  (Read 521670 times)
etotheipi (OP)
Legendary
*
Offline Offline

Activity: 1428
Merit: 1093


Core Armory Developer


View Profile WWW
April 27, 2014, 11:45:53 PM
 #3581

I have been cross-compiling it for Pi on one of my Ubuntu VMs. 

I compiled it using the pi itself.  That is very slow Smiley, but less hassle than cross compiling.

Depends what you mean by "less hassle".  Doing it my way requires more "down payment" to get it setup, but then it's trivial to compile new versions.  Once I push my latest changes to the repo, I can just switch to the RPi directory, pull, and run "make CXX=<pathtocxcompile-g++>".  3 minutes later I have an RPi release Smiley

In fact, I think I don't even have to switch directories!  But I do it anyway to be clean.


Founder and CEO of Armory Technologies, Inc.
Armory Bitcoin Wallet: Bringing cold storage to the average user!
Only use Armory software signed by the Armory Offline Signing Key (0x98832223)

Please donate to the Armory project by clicking here!    (or donate directly via 1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX -- yes, it's a real address!)
Transactions must be included in a block to be properly completed. When you send a transaction, it is broadcast to miners. Miners can then optionally include it in their next blocks. Miners will be more inclined to include your transaction if it has a higher transaction fee.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
TierNolan
Legendary
*
Offline Offline

Activity: 1232
Merit: 1077


View Profile
April 28, 2014, 11:05:30 AM
Last edit: April 28, 2014, 01:58:56 PM by TierNolan
 #3582

Depends what you mean by "less hassle".  Doing it my way requires more "down payment" to get it setup, but then it's trivial to compile new versions.  Once I push my latest changes to the repo, I can just switch to the RPi directory, pull, and run "make CXX=<pathtocxcompile-g++>".  3 minutes later I have an RPi release Smiley

In fact, I think I don't even have to switch directories!  But I do it anyway to be clean.

Heh, true.  I guess it is the difference between a user and a developer.  

Being able to download the pre-compiled files is easier for everyone.

For multi-sig, are you planning to have watch only wallet capability?  

This would be where you could have 3 watching only wallets installed and it would tell you that a multi-sig payment could be redeemed by 2 of 3 of them.

You could also allow creation of a spending transaction that each private key owner could sign in turn.

This is better for "boards" that have N of M spending requirements.  Each member would have a watching-only wallet for all keys associated with the cold store and one set of private keys.

You could also create 2 level shamir sharing.  For example, you could have 2 of 3 sharing, but each share is then split up into 2 of 3 as well.  This means that each share is protected against loss too by sharing.

1LxbG5cKXzTwZg9mjL3gaRE835uNQEteWF
etotheipi (OP)
Legendary
*
Offline Offline

Activity: 1428
Merit: 1093


Core Armory Developer


View Profile WWW
April 28, 2014, 03:43:17 PM
 #3583

For multi-sig, are you planning to have watch only wallet capability? 

This would be where you could have 3 watching only wallets installed and it would tell you that a multi-sig payment could be redeemed by 2 of 3 of them.

You could also allow creation of a spending transaction that each private key owner could sign in turn.

This is better for "boards" that have N of M spending requirements.  Each member would have a watching-only wallet for all keys associated with the cold store and one set of private keys.

You could also create 2 level shamir sharing.  For example, you could have 2 of 3 sharing, but each share is then split up into 2 of 3 as well.  This means that each share is protected against loss too by sharing.


This is already supported by the lockboxes!  All parties in a lockbox can be offline keys, created separately and independently.   Each party individually manages their own wallet holding that key, including all the regular methods we have backups... yes you can do a 2-of-4 lockbox between 4 parties, and each party can do a 3-of-5 fragmented backup of their individual wallets (which hold the key).

Speaking of that, we're working on multisig lockboxes on the "devel" branch -- anyone can check it out and play with it.  It's actually looking really good.  Got P2SH working, so you should be able to go above 3-of-3 on mainnet now... but of course I don't recommend using any money you can't afford to lose (yet)!

The lockboxes and all the data passed between devices/parties assumes that all keys are offline, and thus always contain all information needed to sign offline.  The downside to this is that all these message formats have changed, even for regular offline transactions, so all online & offline devices will need to be updated to use this.  But once you do, it does work! 

Will have the last couple pieces of it implemented soon and put out an experimental build to get people playing with.

Founder and CEO of Armory Technologies, Inc.
Armory Bitcoin Wallet: Bringing cold storage to the average user!
Only use Armory software signed by the Armory Offline Signing Key (0x98832223)

Please donate to the Armory project by clicking here!    (or donate directly via 1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX -- yes, it's a real address!)
TierNolan
Legendary
*
Offline Offline

Activity: 1232
Merit: 1077


View Profile
April 28, 2014, 03:52:48 PM
 #3584

This is already supported by the lockboxes!  All parties in a lockbox can be offline keys, created separately and independently.   Each party individually manages their own wallet holding that key, including all the regular methods we have backups... yes you can do a 2-of-4 lockbox between 4 parties, and each party can do a 3-of-5 fragmented backup of their individual wallets (which hold the key).

Cool, I need to do some forum searching.

1LxbG5cKXzTwZg9mjL3gaRE835uNQEteWF
etotheipi (OP)
Legendary
*
Offline Offline

Activity: 1428
Merit: 1093


Core Armory Developer


View Profile WWW
April 28, 2014, 03:55:44 PM
 #3585

This is already supported by the lockboxes!  All parties in a lockbox can be offline keys, created separately and independently.   Each party individually manages their own wallet holding that key, including all the regular methods we have backups... yes you can do a 2-of-4 lockbox between 4 parties, and each party can do a 3-of-5 fragmented backup of their individual wallets (which hold the key).

Cool, I need to do some forum searching.

https://bitcointalk.org/index.php?topic=559776.0

Founder and CEO of Armory Technologies, Inc.
Armory Bitcoin Wallet: Bringing cold storage to the average user!
Only use Armory software signed by the Armory Offline Signing Key (0x98832223)

Please donate to the Armory project by clicking here!    (or donate directly via 1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX -- yes, it's a real address!)
RoadStress
Legendary
*
Offline Offline

Activity: 1904
Merit: 1007


View Profile
May 01, 2014, 06:59:42 PM
 #3586

Quote
It is not necessary to upgrade any offline computers just to check wallet consistency.

How do we do that from the Armory menus? Or just restart Armory?

I have upgraded to 0.91.1 and it checked for my wallet consistency when i started it. Guess i don't have to do anything else.

etotheipi (OP)
Legendary
*
Offline Offline

Activity: 1428
Merit: 1093


Core Armory Developer


View Profile WWW
May 01, 2014, 07:17:23 PM
 #3587

Quote
It is not necessary to upgrade any offline computers just to check wallet consistency.

How do we do that from the Armory menus? Or just restart Armory?

I have upgraded to 0.91.1 and it checked for my wallet consistency when i started it. Guess i don't have to do anything else.

Notice it says not necessary Smiley  If all your hot wallets and watching-only wallets have been loaded on 0.91 or 0.91.1 before, and no notification popped up, no further action is required.  I would guess that 99%+ users will pass this check without issue.  And of those cases with consistency issues, the recovery tool can fix most of them.

Will post more information about this soon.   Working on getting an announcement page up and distributing notifications to older versions.

Founder and CEO of Armory Technologies, Inc.
Armory Bitcoin Wallet: Bringing cold storage to the average user!
Only use Armory software signed by the Armory Offline Signing Key (0x98832223)

Please donate to the Armory project by clicking here!    (or donate directly via 1QBDLYTDFHHZAABYSKGKPWKLSXZWCCJQBX -- yes, it's a real address!)
RoadStress
Legendary
*
Offline Offline

Activity: 1904
Merit: 1007


View Profile
May 02, 2014, 12:19:42 AM
 #3588

Quote
It is not necessary to upgrade any offline computers just to check wallet consistency.

How do we do that from the Armory menus? Or just restart Armory?

I have upgraded to 0.91.1 and it checked for my wallet consistency when i started it. Guess i don't have to do anything else.

Notice it says not necessary Smiley  If all your hot wallets and watching-only wallets have been loaded on 0.91 or 0.91.1 before, and no notification popped up, no further action is required.  I would guess that 99%+ users will pass this check without issue.  And of those cases with consistency issues, the recovery tool can fix most of them.

Will post more information about this soon.   Working on getting an announcement page up and distributing notifications to older versions.

Somehow I understood that an upgrade isn't necessary, but we still needed to check the wallet consistency. I got it now. Thank you.

bitpop
Legendary
*
Offline Offline

Activity: 2912
Merit: 1060



View Profile WWW
May 02, 2014, 01:11:22 AM
 #3589

Basically there's an attack they can't talk about yet, just get updated. The attack makes armory generate addresses from the virus.

superbit
Hero Member
*****
Offline Offline

Activity: 763
Merit: 500



View Profile
May 02, 2014, 06:12:47 AM
 #3590

What am I doing wrong to verify the file?

It looks like the key file is right?


https://bitfinex.com/?refcode=UInJLQ5KpA <-- leveraged trading of BTCUSD, LTCUSD and LTCBTC (long and short) - 10% discount on fees for the first 30 days with the refcode
My feedback thread: Forum thread
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 3640
Merit: 1345

Armory Developer


View Profile
May 02, 2014, 08:15:36 PM
 #3591

Which key are you verifying against? You should have Alan's offline signing public key in your key ring before doing this.

superbit
Hero Member
*****
Offline Offline

Activity: 763
Merit: 500



View Profile
May 02, 2014, 08:19:54 PM
 #3592

Which key are you verifying against? You should have Alan's offline signing public key in your key ring before doing this.

The one hosted at MIT?  I do and it is marked as trusted.

https://bitfinex.com/?refcode=UInJLQ5KpA <-- leveraged trading of BTCUSD, LTCUSD and LTCBTC (long and short) - 10% discount on fees for the first 30 days with the refcode
My feedback thread: Forum thread
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 3640
Merit: 1345

Armory Developer


View Profile
May 02, 2014, 09:17:39 PM
 #3593

He has 2 of these. One that is "online", used for email signing and encryption, one marked as "offline" used for release signing. Also you could try to verify the bitcoin signature.

marcus_of_augustus
Legendary
*
Offline Offline

Activity: 3920
Merit: 2347


Eadem mutata resurgo


View Profile
May 03, 2014, 05:17:28 AM
 #3594

Basically there's an attack they can't talk about yet, just get updated. The attack makes armory generate addresses from the virus.

 Shocked

superbit
Hero Member
*****
Offline Offline

Activity: 763
Merit: 500



View Profile
May 03, 2014, 05:21:00 AM
 #3595

He has 2 of these. One that is "online", used for email signing and encryption, one marked as "offline" used for release signing. Also you could try to verify the bitcoin signature.

How would I get an "offline" key?

https://bitfinex.com/?refcode=UInJLQ5KpA <-- leveraged trading of BTCUSD, LTCUSD and LTCBTC (long and short) - 10% discount on fees for the first 30 days with the refcode
My feedback thread: Forum thread
bitpop
Legendary
*
Offline Offline

Activity: 2912
Merit: 1060



View Profile WWW
May 03, 2014, 05:59:50 AM
 #3596

Basically there's an attack they can't talk about yet, just get updated. The attack makes armory generate addresses from the virus.

 Shocked

This also means new best practice is sending to offline wallet using an address created on there. Previously I got an address from the watch only copy.

bitpop
Legendary
*
Offline Offline

Activity: 2912
Merit: 1060



View Profile WWW
May 03, 2014, 06:00:06 AM
 #3597

He has 2 of these. One that is "online", used for email signing and encryption, one marked as "offline" used for release signing. Also you could try to verify the bitcoin signature.

How would I get an "offline" key?

http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x4AB16AEA98832223


flipperfish
Sr. Member
****
Offline Offline

Activity: 350
Merit: 251


Dolphie Selfie


View Profile
May 03, 2014, 11:05:25 AM
 #3598

This also means new best practice is sending to offline wallet using an address created on there. Previously I got an address from the watch only copy.

Can you explain this a little further? AFAIK, the addresses generated on the offline wallet and the watch only copy are the same? Wouldn't be of much use otherwise...
bitpop
Legendary
*
Offline Offline

Activity: 2912
Merit: 1060



View Profile WWW
May 03, 2014, 11:12:39 AM
 #3599

This also means new best practice is sending to offline wallet using an address created on there. Previously I got an address from the watch only copy.

Can you explain this a little further? AFAIK, the addresses generated on the offline wallet and the watch only copy are the same? Wouldn't be of much use otherwise...

A virus can compromise your watch only copy to generate addresses that aren't yours. This completely bypasses all security.

You could generate it then glance at the cold storage copy to make sure it's in the list. You may have to generate extra ones to get the number of addresses the same.

jl2012
Legendary
*
Offline Offline

Activity: 1792
Merit: 1087


View Profile
May 03, 2014, 01:38:44 PM
 #3600

This also means new best practice is sending to offline wallet using an address created on there. Previously I got an address from the watch only copy.

Can you explain this a little further? AFAIK, the addresses generated on the offline wallet and the watch only copy are the same? Wouldn't be of much use otherwise...

A virus can compromise your watch only copy to generate addresses that aren't yours. This completely bypasses all security.

You could generate it then glance at the cold storage copy to make sure it's in the list. You may have to generate extra ones to get the number of addresses the same.

Is that a malware, or a bug in Armory?

Donation address: 374iXxS4BuqFHsEwwxUuH3nvJ69Y7Hqur3 (Bitcoin ONLY)
LRDGENPLYrcTRssGoZrsCT1hngaH3BVkM4 (LTC)
PGP: D3CC 1772 8600 5BB8 FF67 3294 C524 2A1A B393 6517
Pages: « 1 ... 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 [180] 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!