Bitcoin Forum
May 01, 2024, 07:10:55 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Using the same EC key for both ECDSA and ECIES?  (Read 1066 times)
Atheros (OP)
Sr. Member
****
Offline Offline

Activity: 249
Merit: 251



View Profile WWW
October 22, 2014, 11:44:46 PM
 #1

I have begun mentally planning to add a new address format to Bitmessage which has the public key encoded right in the bitmessage address. This comes at the behest of gmaxwell. It's a good idea. It would allow a Bitmessage user who receives messages to remain completely passive, and thus anonymous, even against a global attacker who can listen and even modify traffic on any or all individual Internet connections.

But
This would require that the same EC key be used for both signing and encryption where ECIES is used for encryption. Is there currently sufficient reason to believe that this should be avoided? Or is there specific reason to believe that it is safe?
If there is only a small risk of it being insecure then it might be outweighed by the benefit of completely passive client operation.

-Atheros

BM-GteJMPqvHRUdUHHa1u7dtYnfDaH5ogeY
Bitmessage.org - Decentralized, trustless, encrypted, authenticated messaging protocol and client.
1714547455
Hero Member
*
Offline Offline

Posts: 1714547455

View Profile Personal Message (Offline)

Ignore
1714547455
Reply with quote  #2

1714547455
Report to moderator
1714547455
Hero Member
*
Offline Offline

Posts: 1714547455

View Profile Personal Message (Offline)

Ignore
1714547455
Reply with quote  #2

1714547455
Report to moderator
1714547455
Hero Member
*
Offline Offline

Posts: 1714547455

View Profile Personal Message (Offline)

Ignore
1714547455
Reply with quote  #2

1714547455
Report to moderator
"Your bitcoin is secured in a way that is physically impossible for others to access, no matter for what reason, no matter how good the excuse, no matter a majority of miners, no matter what." -- Greg Maxwell
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714547455
Hero Member
*
Offline Offline

Posts: 1714547455

View Profile Personal Message (Offline)

Ignore
1714547455
Reply with quote  #2

1714547455
Report to moderator
1714547455
Hero Member
*
Offline Offline

Posts: 1714547455

View Profile Personal Message (Offline)

Ignore
1714547455
Reply with quote  #2

1714547455
Report to moderator
1714547455
Hero Member
*
Offline Offline

Posts: 1714547455

View Profile Personal Message (Offline)

Ignore
1714547455
Reply with quote  #2

1714547455
Report to moderator
marcus_of_augustus
Legendary
*
Offline Offline

Activity: 3920
Merit: 2348


Eadem mutata resurgo


View Profile
November 02, 2014, 11:19:38 AM
 #2

Quote
This would require that the same EC key be used for both signing and encryption where ECIES is used for encryption. Is there currently sufficient reason to believe that this should be avoided? Or is there specific reason to believe that it is safe?
If there is only a small risk of it being insecure then it might be outweighed by the benefit of completely passive client operation.

Maybe better ask this specific question in Development and Technical. For RSA, the rule of thumb is NOT to use same key for signing and encryption but it depends on specific use and ECC could be different too.

Pages: [1]
  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!