Nonco-Organization/python-ecdsa

选用指南

AI 根据 README 整理 · 2026/10/14 16:26:01

使用方式

通过Python代码调用，提供SigningKey和VerifyingKey类进行密钥生成、签名和验证，支持多种序列化格式。

查看 README 依据

can be used to verify a signature, by passing it both the data string and the signature string: it either returns True or raises BadSignatureError. ```python from ecdsa import SigningKey sk = SigningKey.generate() # uses NIST192p vk = sk.get_verifying_key() signature = sk.sign("message") assert vk.verify(signature, "message") ``` Each SigningKey/VerifyingKey is associated with a specific curve, like NIST192p (the default one). Longer curves are more secure, but take longer to use, and result in longer keys and signatures. ```python from ecdsa import SigningKey, NIST384p

部署要求

需要Python 2.6至3.6版本，依赖'six'包，并需要系统安装GMP（通过fastecdsa）。

查看 README 依据

by Bitcoin, whose short name is secp256k1. No other curves are included, but it would not be too hard to add more. ## Dependencies This library uses Python and the 'six' package. It is compatible with Python 2.6, 2.7, 3.3, 3.4, 3.5, and 3.6. It relies on [fastecdsa][1], which requires [GMP][2] to be installed on the system. See fastecdsa's [README][3] for more information. To run the OpenSSL compatibility tests, the 'openssl' tool must be on your $PATH. This release has been tested successfully against both OpenSSL 0.9.8o and 1.0.0a . ## Speed

已知限制

作者明确说明不防护时序攻击，且依赖强随机数源，在os.urandom()较弱的环境下不应使用。

查看 README 依据

"del OpenSSL" to the end of test_pyecdsa.py). ## Security This library does not protect against timing attacks. Do not allow attackers to measure how long it takes you to generate a keypair or sign a message. This library depends upon a strong source of random numbers. Do not use it on a system where os.urandom() is weak. ## Usage You start by creating a SigningKey. You can use this to sign data, by passing in a data string and getting back the signature (also a string). You can also ask a SigningKey to give you the corresponding VerifyingKey. The VerifyingKey