| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Daniel Ziegenberg <daniel@ziegenberg.at>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix the documentation by adding referenced-but-not-included functions and
some other small fixes.
The only warnings left are:
```
python-rsa/rsa/key.py:docstring of rsa.key.AbstractKey.load_pkcs1:: WARNING: py:class reference target not found: rsa.key.T
python-rsa/rsa/key.py:docstring of rsa.key.AbstractKey.load_pkcs1:: WARNING: py:class reference target not found: rsa.key.T
```
These are due to Sphynx not really understanding `typing` type references.
Not sure how to fix those.
|
|
|
|
| |
This option was shown quite useful in #199.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Strings need to be encoded into bytes before the RSA module can operate
on them.
|
|
|
|
| |
See commit d15a7f3 for the reason why.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Poetry breaks no-binary installations of the RSA library, which defeats
the purpose of this library.
See https://github.com/sybrenstuvel/python-rsa/issues/148
Among other changes, this reverts commit
fcf5b7457c70426a242b17db20dd4e34e1055f69.
I also added a workaround for an `ImportError` importing `zipp` on
Python 3.5.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This is based on https://github.com/sybrenstuvel/python-rsa/pull/96, with
a few improvements:
- The minimum of one use of SHA3 in a unit test, to at least touch it at
some point.
- Documented the support of SHA3.
- Only install the third-party library required by Python 3.5 when we're
running on Python 3.5. Newer Python versions support SHA3 natively.
|
|
|
|
|
| |
Poetry generates a setup.py as part of the building process. It's no longer
necessary to keep it in the Git repo.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some of our development dependencies, like Sphinx, have already dropped
support for Python 2. This makes it harder for this project to update
its dependencies. Since Python 2 only has a few more months to live, I
think it's fine to drop support now.
Python 3.4 has already reached its end-of-life date.
Python-RSA now only supports Python 3.5 and newer. Python 3.5 support is
intended to last until its end-of-life date of 2019-09-13:
https://devguide.python.org/#status-of-python-branches
|
| |
|
| |
|
|
|
|
|
|
| |
This library is probably not the right place to recommend key sizes
or have discussions about the relation between key sizes and hash
function outputs.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Split the hashing out of the sign method
This code change adds support to split the hashing of a message
and the actual signing of the message.
* Updating unit test and documentation
This commit updates the unit test and usage docs. In addition,
This change removes a redundant error check inside rsa.sign().
* Refactore unit tests and code comments
Removed the print statements from the unit test and refactored a
few code comments to improve readability.
* Rename hash function
The new hash function had the same name as a function in the
standard library. This commit changes the name to avoid conflicts.
* Rename hash function to compute_hash()
This commit renames the hash function to compute_hash().
|
|
|
|
|
|
| |
I've not used the name "find_method_hash" suggested in #78, as it's a bit
vague. It's ok-ish for a private function `_find_method_hash`, but I
thought `find_signature_hash` would be more descriptive.
|
|
|
|
| |
Also worded the use of 'sudo' a bit more carefully.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Also:
- changed http to https in the code
- changed header underlines in the documentation to match the header length
|
| |
|
| |
|
|
|
|
|
| |
Pickling is now possible, with the added note that one should never
unpickle from an untrusted or unauthenticated source.
|
|
|
|
|
| |
This deprecation is due to security issues; see
https://github.com/sybrenstuvel/python-rsa/issues/13 for more information.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- when verification passes verify() will return True, instead of
None. If verification fails the function will still raise a
rsa.pkcs1.VerificationError for legacy purposes.
- update the docs to note that the verify() function returns True
when successful
- write unit tests to verify this new behavior
This commit passes all build tests:
Ran 44 tests in 1.217s
OK
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|