[PYTHON-CRYPTO] Requirements
Dan Parisien
dan at eevolved.com
Wed Feb 14 01:18:27 CET 2001
On Terça 13 Fevereiro 2001 02:05, you wrote:
> For me it's the main motivation for discussing such an API.
Of course it is. This is what you need for your product. I would like to see
more proof of concept and less abtract suggestions...
If the directory tree is free of clutter or 'helper' python scripts/binary
python modules, then a search algorithm can be as trivial as a directory
search. Helper scripts or libs could be placed in a vanilla python path,
while only standard compliant modules would be placed in the python crypto/
dir tree.
> > * Handle key exchanges and have a key "ring"
> - key stores
I'm a big fan of a key ring. It could be written with shelve. I am not
certain about the specifics and would not want to reinvent the wheel on this
one. Any links anyone? (why am I asking? I'll search google.com. Has anyone
else noticed google is like humanity's motherbrain?)
> Well, that's your point of view. I agree that producing correct code
> is the main goal. But I agree with the people who are in favour with
> OpenSSL: It's already a very good implementation (although written
> in C ;-) and the code was reviewed and fully understood by many
> people. If I would have to choose something for secure production
> use I would stick to this.
It would be trivial to code API standard adhering implementations of specific
algorithms that in turn use OpenSSL's API. Anyone up to it?
Dan
More information about the python-crypto
mailing list