jmg
/
pycryptowrap
1
0
Fork 0
Code Issues 0 Pull Requests 0 Releases 0 Wiki Activity
A wrapper to present a cryptography api but use the pycryptodome module.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
2 Commits
1 Branch
31 KiB
 
 
Tree: d1067aa6a5
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from 'd1067aa6a5'
${ noResults }
 ZIP  TAR.GZ
John-Mark Gurney d1067aa6a5 ignore build directory.. 1 year ago
cryptography first cut of the cryptography->pycryptodome compatibility/translation layer 1 year ago
.gitignore ignore build directory.. 1 year ago
Makefile first cut of the cryptography->pycryptodome compatibility/translation layer 1 year ago
README.md first cut of the cryptography->pycryptodome compatibility/translation layer 1 year ago
requirements.txt first cut of the cryptography->pycryptodome compatibility/translation layer 1 year ago
setup.py first cut of the cryptography->pycryptodome compatibility/translation layer 1 year ago

README.md

pycryptowrap

This is a translation layer to let software written for cryptography to used with pycryptodome.

It currently only implements a minimal interface to get pywebpush working.

Currently implemented, tested, and working:

  • AES-GCM
  • ECC SECP256R1 - DSS and ECDH

It shouldn’t be too hard to add some additional ciphers or curves.

Testing

The Makefile does the neccessary work to build an environment. To run the tests:

make test-noentr

This will first run the tests against the cryptography module, and then run the tests against this module. This makes sure that the tests are valid, and also makes it easier to add known answers to make sure you don’t end up only self compatible.

To make developing easier, the test target has one dependency, entr. This will watch for changes in the py files, and automatically rerun the test.