geremy condra <debat...@gmail.com> added the comment: On Fri, Jun 18, 2010 at 5:37 AM, Antoine Pitrou <rep...@bugs.python.org> wrote: > > Antoine Pitrou <pit...@free.fr> added the comment: > >> I would suggest that we focus on defining and building a >> lower-level interface along the lines of the PEP noted earlier, >> integrating that with evpy, and getting it in shape to go into the >> stdlib. > > That sounds reasonable to me.
Great, I'm thinking more-or-less the API proposed in PEP 272- the exception I'm thinking of is that 'strings' should be substituted for 'bytes'- for AES and DES. It gets trickier when talking about public key crypto, though. Perhaps something along the lines of RSA.new(public_key=None, private_key=None,...), with the resulting object supporting encrypt/decrypt/sign/verify operations? > (although I would be also content with the lower-level interface > alone :-)) >> If somebody does, then perhaps a four-tiered >> model makes more sense, with the bottom one being the raw wrappers >> around the various libs, the second from the bottom being >> compatibility shims, and the top two matching the other proposal. > > That sounds much too complicated. If we're likely to have openssl taken out from under us it could save us a lot of hassle to plan for that up front. If not, then why worry, and ISTM we should go the simpler route. Geremy Condra ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8998> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
