Message107868
I've taken a quick look at the source tree (there doesn't seem to be any separate docs) and here is my opinion:
- the evp.py API is too low-level (it's a one-to-one mapping to the OpenSSL C API); we would want at least some kind of object-oriented abstraction around the basic concepts (such as in the hashlib and ssl modules) rather than passing opaque pointers around
- the other APIs (cipher.py, envelope.py, signature.py) look conversely too high-level, since they focus on specific use cases and make some arbitrary choices for the user (for example, envelope.py imposes AES-192)
By the way, the use of function signature annotations to mirror C APIs as Python APIs through ctypes is nice, perhaps you should upload it as a separate library on PyPI :) |
|
Date |
User |
Action |
Args |
2010-06-15 13:21:14 | pitrou | set | recipients:
+ pitrou, loewis, gregory.p.smith, exarkun, giampaolo.rodola, heikki, eric.araujo, debatem1, daniel.urban, mcrute |
2010-06-15 13:21:13 | pitrou | set | messageid: <1276608073.65.0.599603228222.issue8998@psf.upfronthosting.co.za> |
2010-06-15 13:21:12 | pitrou | link | issue8998 messages |
2010-06-15 13:21:11 | pitrou | create | |
|