Bitcoin Forum
January 20, 2019, 02:22:10 PM *
News: Latest Bitcoin Core release: 0.17.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: [Electrum 3.2.3] Why does it wish to use an at-risk package called libsecp256k1?  (Read 64 times)
tUnes3
Jr. Member
*
Offline Offline

Activity: 39
Merit: 2


View Profile
September 08, 2018, 01:39:57 PM
Last edit: September 08, 2018, 04:20:03 PM by tUnes3
 #1

I managed to launch Electrum 3.2.3 from its folder. However it comes with the following warning:

Quote
$ ./run_electrum
[ecc] info: libsecp256k1 library not available, falling back to python-ecdsa. This means signing operations will be slower.

According to Debian (url: https://packages.debian.org/stretch/libsecp256k1-0), it warns that

NB! This library is a work in progress and is being used to research best practices. Use at your own risk.

I wonder how many of you have been using libsecp256k1 since Electrum 3.2.2
1547994130
Hero Member
*
Offline Offline

Posts: 1547994130

View Profile Personal Message (Offline)

Ignore
1547994130
Reply with quote  #2

1547994130
Report to moderator
1547994130
Hero Member
*
Offline Offline

Posts: 1547994130

View Profile Personal Message (Offline)

Ignore
1547994130
Reply with quote  #2

1547994130
Report to moderator
"Bitcoin: mining our own business since 2009" -- Pieter Wuille
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1547994130
Hero Member
*
Offline Offline

Posts: 1547994130

View Profile Personal Message (Offline)

Ignore
1547994130
Reply with quote  #2

1547994130
Report to moderator
1547994130
Hero Member
*
Offline Offline

Posts: 1547994130

View Profile Personal Message (Offline)

Ignore
1547994130
Reply with quote  #2

1547994130
Report to moderator
achow101
Staff
Legendary
*
Offline Offline

Activity: 1652
Merit: 1981


bc1qshxkrpe4arppq89fpzm6c0tpdvx5cfkve2c8kl


View Profile WWW
September 08, 2018, 02:56:59 PM
 #2

Because there isn't really a risk to using libsecp256k1. That's just there as a disclaimer since some parts of the library are experimental, but those are also labeled clearly.

libsecp256k1 is what Bitcoin Core uses for all of its ECDSA operations for several years now. The library was created by some Bitcoin Core developers.

tUnes3
Jr. Member
*
Offline Offline

Activity: 39
Merit: 2


View Profile
September 08, 2018, 04:13:51 PM
 #3

Because there isn't really a risk to using libsecp256k1. That's just there as a disclaimer since some parts of the library are experimental, but those are also labeled clearly.

Has there been any reported hacks that took advantage of the fact that some parts of libsecp256k1 are experimental?

libsecp256k1 is what Bitcoin Core uses for all of its ECDSA operations for several years now. The library was created by some Bitcoin Core developers.

Thanks a lot for this piece of information.
achow101
Staff
Legendary
*
Offline Offline

Activity: 1652
Merit: 1981


bc1qshxkrpe4arppq89fpzm6c0tpdvx5cfkve2c8kl


View Profile WWW
September 08, 2018, 04:28:39 PM
 #4

Has there been any reported hacks that took advantage of the fact that some parts of libsecp256k1 are experimental?
No, because those things are not used in Bitcoin. Also, the library is heavily reviewed by cryptographers.

Even experimental things are generally safe to use as their cryptography is reviewed before it is implemented into libsecp256k1. The experimental mostly refers to the fact that APIs may change for those experimental things. Also, the experimental stuff is not enabled by default and must be explicitly enabled when compiling the library.

tUnes3
Jr. Member
*
Offline Offline

Activity: 39
Merit: 2


View Profile
September 08, 2018, 04:32:25 PM
 #5

Has there been any reported hacks that took advantage of the fact that some parts of libsecp256k1 are experimental?
No, because those things are not used in Bitcoin. Also, the library is heavily reviewed by cryptographers.

Even experimental things are generally safe to use as their cryptography is reviewed before it is implemented into libsecp256k1. The experimental mostly refers to the fact that APIs may change for those experimental things. Also, the experimental stuff is not enabled by default and must be explicitly enabled when compiling the library.

Thanks for your explanation. I've acquired some knowledge today Smiley
Pages: [1]
  Print  
 
Jump to:  

Bitcointalk.org is not available or authorized for sale. Do not believe any fake listings.
Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!