Author [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] Topic: AGS potential security issue  (Read 1858 times)

0 Members and 1 Guest are viewing this topic.

Offline crazybit

  • Sr. Member
  • ****
  • Posts: 416
    • View Profile
AGS potential security issue
« on: May 26, 2014, 04:16:01 PM »

One thing sure is that more and more DAC will come out in future,but there is a potential security issue that the more times we import the AGS private key to claim the corresponding shares in the DAC,the more risk the private key might be exposed,under the current social contract without AGS Liquid,we even cannot transfer the AGS shares to other address if the private key exposed,is there any consideration or plan to improve the AGS security,please discuss.
« Last Edit: May 26, 2014, 11:40:24 PM by CrazyBit »

Offline santaclause102

  • Hero Member
  • *****
  • Posts: 2487
    • View Profile
Re: AGS potential security issue
« Reply #1 on: May 26, 2014, 04:24:48 PM »
I don't think you expose your private keys to anyone else in the network. You just verify on your local machine to the network that you own the address that is granted shares...

Offline toast

Re: AGS potential security issue
« Reply #2 on: May 26, 2014, 04:42:20 PM »
I think he means a malicious client stealing private keys. Of course this is a great reason to make AGS liquid.

You can always sign transactions offline and refuse to use a client that doesn't allow you to construct unsigned transactions.
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.

Offline crazybit

  • Sr. Member
  • ****
  • Posts: 416
    • View Profile
回复: Re: AGS potential security issue
« Reply #3 on: May 26, 2014, 04:45:33 PM »
I don't think you expose your private keys to anyone else in the network. You just verify on your local machine to the network that you own the address that is granted shares...
you have to admit that it is possible your private key might be exposed if it is imported to the customized or malicious DAC client with the purpose to steal your private key.we cannot review every DAC client source code(i think mainly the third party DAC) and build client by ourselves to make sure the client will not steal our private key.
« Last Edit: May 26, 2014, 11:36:23 PM by CrazyBit »

Offline crazybit

  • Sr. Member
  • ****
  • Posts: 416
    • View Profile
Re: AGS potential security issue
« Reply #4 on: May 26, 2014, 05:01:46 PM »
I think he means a malicious client stealing private keys. Of course this is a great reason to make AGS liquid.

You can always sign transactions offline and refuse to use a client that doesn't allow you to construct unsigned transactions.
Yes,you got my point of the security issue part,but i am not talking about liquid AGS,just concern for the AGS Security issue.
« Last Edit: May 26, 2014, 05:12:12 PM by CrazyBit »

Offline bitmeat

  • Hero Member
  • *****
  • Posts: 1116
    • View Profile
Re: AGS potential security issue
« Reply #5 on: May 26, 2014, 05:24:34 PM »
The more times a private key is used to sign, the easier it is to hack the address. That's why Satoshi in his original paper recommends creating a new change address every time a transaction is signed. Real security is achieved if you ONLY sign things ONCE per private key.

Offline Overthetop

Re: AGS potential security issue
« Reply #6 on: May 27, 2014, 07:11:28 AM »
个人微博账号: Overthetop_万里晴空
“块链创新与创业”交流群: 330378613

Offline toast

Re: AGS potential security issue
« Reply #7 on: May 27, 2014, 01:44:59 PM »
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.

Offline crazybit

  • Sr. Member
  • ****
  • Posts: 416
    • View Profile
Re: AGS potential security issue
« Reply #8 on: May 31, 2014, 05:04:20 AM »
Inspired by logxing's proposal, i come up with an idea which may completely solve this potential security issue.  if we could use the signature which sign on the specified text(e.g the donation address) with private key, to claim the corresponding shares in different DACs,then we would not worry about private key stolen,as we do NOT need to expose our private key and use different signature to claim the shares in different DAC. e.g signature to claim the XTS shares =sign(“XTS”+Pts/BTC donation address, PrivateKey), signature to claim the DNS shares =sign(“DNS”+Pts/BTC donation address, PrivateKey)
« Last Edit: May 31, 2014, 05:11:44 AM by CrazyBit »

Offline toast

Re: AGS potential security issue
« Reply #9 on: May 31, 2014, 06:00:06 AM »
Inspired by logxing's proposal, i come up with an idea which may completely solve this potential security issue.  if we could use the signature which sign on the specified text(e.g the donation address) with private key, to claim the corresponding shares in different DACs,then we would not worry about private key stolen,as we do NOT need to expose our private key and use different signature to claim the shares in different DAC. e.g signature to claim the XTS shares =sign(“XTS”+Pts/BTC donation address, PrivateKey), signature to claim the DNS shares =sign(“DNS”+Pts/BTC donation address, PrivateKey)

Yep, we can have a dedicated tool just for this
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12339
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BTS: xeroc
  • GitHub: xeroc
Re: AGS potential security issue
« Reply #10 on: May 31, 2014, 06:58:13 AM »
We disscused sth similar in the "Mirrorchain" thread .. you should take a look
Give BitShares a try! Use the http://testnet.bitshares.eu provided by http://bitshares.eu powered by ChainSquad GmbH

Offline crazybit

  • Sr. Member
  • ****
  • Posts: 416
    • View Profile
Re: AGS potential security issue
« Reply #11 on: May 31, 2014, 07:08:18 AM »
We disscused sth similar in the "Mirrorchain" thread .. you should take a look
Thx,i would take a look

Offline bitmeat

  • Hero Member
  • *****
  • Posts: 1116
    • View Profile
Re: AGS potential security issue
« Reply #12 on: May 31, 2014, 07:38:13 AM »
Inspired by logxing's proposal, i come up with an idea which may completely solve this potential security issue.  if we could use the signature which sign on the specified text(e.g the donation address) with private key, to claim the corresponding shares in different DACs,then we would not worry about private key stolen,as we do NOT need to expose our private key and use different signature to claim the shares in different DAC. e.g signature to claim the XTS shares =sign(“XTS”+Pts/BTC donation address, PrivateKey), signature to claim the DNS shares =sign(“DNS”+Pts/BTC donation address, PrivateKey)

Awesome! I strongly prefer this method. This should be a standard tool in the toolkit. I would imagine we already have a tool that generates the genesis block.

One problem I see with this method however, is that it generates a signature, not a public address. i.e. only holders of AGS could generate the public address for each DAC.

Unless the DAC itself has a method of claiming by signature, but that may complicate the protocol.

Does the Bitshares framework support the same transaction OP_ codes as Bitcoin?

Offline toast

Re: AGS potential security issue
« Reply #13 on: May 31, 2014, 02:08:48 PM »
Inspired by logxing's proposal, i come up with an idea which may completely solve this potential security issue.  if we could use the signature which sign on the specified text(e.g the donation address) with private key, to claim the corresponding shares in different DACs,then we would not worry about private key stolen,as we do NOT need to expose our private key and use different signature to claim the shares in different DAC. e.g signature to claim the XTS shares =sign(“XTS”+Pts/BTC donation address, PrivateKey), signature to claim the DNS shares =sign(“DNS”+Pts/BTC donation address, PrivateKey)

Awesome! I strongly prefer this method. This should be a standard tool in the toolkit. I would imagine we already have a tool that generates the genesis block.

One problem I see with this method however, is that it generates a signature, not a public address. i.e. only holders of AGS could generate the public address for each DAC.

Unless the DAC itself has a method of claiming by signature, but that may complicate the protocol.

Does the Bitshares framework support the same transaction OP_ codes as Bitcoin?

>  only holders of AGS could generate the public address for each DAC.

Not true - you put the public keys in the genesis block like you do now, but to claim them you check the SIG(pubkey, "BTSX") instead of just SIG(pubkey).

We don't use OP_, we hard-code all needed transaction types for each DAC
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.

Offline bitmeat

  • Hero Member
  • *****
  • Posts: 1116
    • View Profile
Re: AGS potential security issue
« Reply #14 on: May 31, 2014, 03:37:35 PM »
I see, then all the addresses use the SIG(pubkey, "BTSX"), right?

 

Google+