Zeronet: [Feature] User identy using quantum resistant addresses (QRL addresses)

Created on 6 Oct 2018  路  9Comments  路  Source: HelloZeroNet/ZeroNet

Description

"There's a straightforward mitigation though: double the key size. In a post-quantum world, AES-256 is still comfortably secure. PGP and GPG are programs that use a variety of cryptographic algorithms. All of their asymmetric operations use algorithms (such as RSA and ECDSA) that are vulnerable to quantum computing".12 de fev de 2016

"In early 2014 it was reported, based on documents provided by former NSA contractor Edward Snowden, that the U.S. National Security Agency (NSA) is running a $79.7 million research program (titled "Penetrating Hard Targets") to develop a quantum computer capable of breaking vulnerable encryption.[101]"

"In late 2017 and early 2018 IBM,[120] Intel,[121] and Google[122] each reported testing quantum processors containing 50, 49, and 72 qubits, respectively, all realized using superconducting circuits. By number of qubits, these circuits are approaching the range in which simulating their quantum dynamics is expected to become prohibitive on classical computers, although it has been argued that further improvements in error rates are needed to put classical simulation out of reach.[123]"

Quantum Resistant Ledger: https://theqrl.org/

Tasks

  • [ ] On ZeroHello, create the simplest (fastest) QRL identy address or more advanced depending on device's power (https://api.theqrl.org/?python#addnewaddress)

    • [ ] User receives its address' private key

    • [ ] User have option to get rid of this new address in order to create a stronger one

    • [ ] User can choose to login with its Bitcoin or QRL address

    • [ ] ZeroID/certificate system supports creation of certificates for identies that uses QRL address and logins

  • [ ] Can sign files
  • [ ] Can verify files (https://github.com/theQRL/QRL/blob/master/src/qrl/core/txs/Transaction.py#L276)

Most helpful comment

From the faq

QRL implements one of a series of peer-reviewed post-quantum secure algorithms: XMSS (eXtended Merkle Signature Scheme) XMSS uses a OTS (One Time Signature Scheme) that can only sign one message with one key.

It means this is not suitable for us, as it would mean the user files and the sites are only updateable once/limited time.

But I think we are far from when it became a problem. And if it do, then I'm pretty sure we will have time to fix/react to it.

All 9 comments

@HelloZeroNet @shortcutme @tangdou1 @trenta3 @anoadragon453

Assuming we do consider quantum computing a threat, it probably wouldn't be too difficult to move over. "v2 sites" would have new addresses, some users would have new addresses too, and clients would just support both. A method for converting from less secure address types to the other would be ideal. One should just have to sign the site with their new quantum-resistent keys.

I don't, however, see this being high priority at the moment, but something to keep around for later. Please don't mention everyone for something non-urgent however.

Assuming we do consider quantum computing a threat, it probably wouldn't be too difficult to move over. "v2 sites" would have new addresses, some users would have new addresses too, and clients would just support both. A method for converting from less secure address types to the other would be ideal. One should just have to sign the site with their new quantum-resistent keys.

No need to "v2" sites for now. We can begin it for user identies.
v2 sites needs more than quantum resistant addresses.

I don't, however, see this being high priority at the moment, but something to keep around for later.

You're sure that there is no quantum computer made by a government, that is more powerful than D-Wave/IBM/Google's ones?

From the faq

QRL implements one of a series of peer-reviewed post-quantum secure algorithms: XMSS (eXtended Merkle Signature Scheme) XMSS uses a OTS (One Time Signature Scheme) that can only sign one message with one key.

It means this is not suitable for us, as it would mean the user files and the sites are only updateable once/limited time.

But I think we are far from when it became a problem. And if it do, then I'm pretty sure we will have time to fix/react to it.

The detail is that will never be disclosed what the most powerful computers can do

@shortcutme

It means this is not suitable for us, as it would mean the user files and the sites are only updateable once/limited time.

An QRL developer replied:

"you can sign nearly infinite times
you just need to generate slave trees off of your root xmss tree
and sign with leaf nodes on those
our wallet api for example does this out of the box
it sounds just like a lack of understanding"
"but you could always point him to the XMSS whitepaper, and explain that a leaf node in the tree can sign another tree - which can be used to essentially generate infinite signatures from one root seed"

Was this page helpful?
0 / 5 - 0 ratings