Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - blahblah7up

Pages: 1 ... 6 7 8 9 10 11 12 [13]
181
Technical Support / need help installing
« on: July 27, 2014, 12:14:01 pm »
Trying to get the Dacsunlimited release 0.2.3 running.

I have an OSX computer and a Linux computer
.dmg file crashes - doesn't open (don't even get to a splash screen or anything like that)

I made it pretty far with the Linux distribution but I don't have cmake v. 2.8.12
Downloaded a tar.gz of 2.8.12.2 and can't get it installed.

I'm only moderately technical and really a very new Linux user.

Any help?

182
General Discussion / Re: Demo Wallet
« on: July 24, 2014, 07:56:03 am »
Password to access the server (demo/demo) works fine.  Password to demo the wallet?

183
General Discussion / Re: Bytemaster (Dan Larimer) on Episode 129 of Let's Talk Bitcoin!
« on: July 23, 2014, 10:42:32 am »
Quote from: xeroc on July 23, 2014, 04:43:14 am
Quote from: changematey on July 23, 2014, 04:38:05 am
How about an option for "holding" ;) even though if it means zombie btsx accounts for year or two.
I you don't move you btsx once a year you might be forced to pay a 5% inactivity fee .. just FYI
http://wiki.bitshares.org/index.php/Inactivity_Fees

Would this also apply for unclaimed btsx?  For example AGS allocation not yet imported?

184
General Discussion / Re: How to protect AGS
« on: July 04, 2014, 02:31:02 pm »
The suggestions in that thread address avoiding the need to expose your private key while claiming new airdropped shares, but it is assumed that the original donation address private key is rock solid, 100% secure, and will never need to be changed. 

I really can't imagine that all the original AGS donation addresses were paper wallets created on air gapped computers with private keys that never touched the network.  In all likelihood they were normal wallets which continued to be used for other purposes after the donation.

Everyone keeps chiming in about how to keep private keys safe while claiming 3rd party DACs utilizing signed transactions, but this is completely missing the point in terms of security in my opinion.  The root of the problem is a locked down original address.

185
Technical Support / Re: AGS potential security issue
« on: June 03, 2014, 10:01:36 pm »
Quote from: asenski on June 03, 2014, 07:06:16 pm

Quote from: blahblah7up on June 03, 2014, 06:31:28 pm
As I understood the suggestion, the signed message was to be used to collect the shares of the new DAC instead of the private key.  But if the private key has already been exposed anyone who has it can create that signed message.

As far as private key already exposed there is no good way to solve that with the current system. I did like the idea of using derived individual private key per DAC so that if one DAC software steals it, it doesn't compromise the rest of your apps.

I also like this idea but it still relies on a single point of failure.  In that case you better be sure you made your AGS donation with a signed tx from a paper wallet created on an air gapped computer.

Do you think most people did?

186
Technical Support / Re: AGS potential security issue
« on: June 03, 2014, 06:38:47 pm »
That is how I interpreted CrazyBit's suggestion.

You seem to be suggesting that AGS will be liquid but I still haven't heard anything that suggests that from anyone within Invictus.

187
Technical Support / Re: AGS potential security issue
« on: June 03, 2014, 06:31:28 pm »
As I understood the suggestion, the signed message was to be used to collect the shares of the new DAC instead of the private key.  But if the private key has already been exposed anyone who has it can create that signed message.

188
Technical Support / Re: AGS potential security issue
« on: June 03, 2014, 05:12:11 pm »
I raised this question several months ago and still think it is very important to find a solution.

https://bitsharestalk.org/index.php?topic=3422.msg42965#msg42965

The idea about using a signed message to avoid exposing the private key doesn't solve the issue because of the ever present possibility of ERRANT HUMAN BEHAVIOR.  Once the keys are "accidentally" exposed, it should be possible to somehow correct the situation (like in any email program you can log in and change your password if for whatever reason you feel that you should).

Suppose for instance someone breaks into your house and you have your private keys stored somewhere.  Nothing is missing and you don't know if the keys were even discovered but you would just feel safer to change those private keys.  At the moment this isn't an option.

189
General Discussion / Re: Airdrop Ideas
« on: April 12, 2014, 12:48:20 pm »
I would suggest an inverse-proportional air-drop on BTC holders.  Then you would get all the people on board who have decided to risk their hard earned money on this whole crypto movement by buying in - the enthusiastic poor people!  That would be huge.

190
BitShares AGS / Re: AGS Security
« on: March 05, 2014, 07:21:57 pm »
jabba, I agree that people HAVE TO learn.  But then there has to be room to make mistakes because that is part of learning.

As it is there is no room for that.

I think this is really something to think about now because right now no one cares.  No one will hack because there's no real big money at stake at the moment.  But if this rapidly becomes big it will be target No. 1.

191
BitShares AGS / Re: AGS Security
« on: March 05, 2014, 06:27:24 pm »
Toast,

Ok, from your quoted response then I can revise my concern to read to every time a "parent" DAC is developed the race would be on...which from my perspective is even more dangerous and critical because everything else will ride on that.

The key phrase in your response is "eventually."  Eventually AGS might be completely liquid because everything is developed on key parent DACs like BTS X.  But what's the time frame on that?  How may days of AGS do we have left?  How many years until ALL those key parent DACs are created?  If you frequent Bitcoin reddit, people are being hacked almost daily.

And people will make mistakes too.  You can say, well that's their fault.  But everyone is just figuring out how this stuff works.  This is the very beginning and there will be mistakes.

As an example: Somewhere on this forum there was a 100 PTS bounty given for an explanation of how to move a Blockchain wallet.dat file to import it locally.  That explanation exposes the private key and that wallet is potentially compromised.

All one needs is a hacker taking screen shots.  If you manually enter your private keys and you've got a keylogger on your system...well...

192
BitShares AGS / AGS Security
« on: March 05, 2014, 05:42:54 pm »
One of the important security features in crypto is the the ability to make any number of addresses and throw them away at will.  This is often even encouraged by developers like with Bitmessage for instance - you make an address for a specific purpose, use it, then move on and never look back.

I see this as a problem for the security of AGS if the shares are to be indefinitely associated with one address.  If that address gets compromised (and address will certainly get compromised) that private key will forever be usable to get the next shares of whatever new DAC is about to come out.  Whoever compromised your wallet could just be quick and take the shares of the new DAC with your private key before you had the opportunity to.  Every time new shares would be released you would be racing against an adversary to download the new wallet and import your private key before you get hacked.

I think being able to move the AGS around is rather important.

Has anyone thought of this?

Pages: 1 ... 6 7 8 9 10 11 12 [13]

Page created in 0.178 seconds with 20 queries.