Bug#100081: amkCrypto/pycrypto packaging status?
On Mon, Aug 26, 2002 at 03:53:04PM +0200, Anders Hammarquist wrote:
> > Hi. I want to release a piece of software that
> > requires rc4 encryption. pycrypto/amkCrypto seems
> > like the sanest solution. As I have not heard
> > from you or your ITP for over three weeks, I'm
> > packaging it independently and uploading as soon
> > as I am finished. You can take the package over
> > later, if you want, but I need it in Debian now.
> Sorry, must have missed your mail (too much spam). I had forgotten
> about that ITP since we soon after switched to using pyOpenSSL instead.
But pyOpenSSL doesn't have MD4.
Oh, pycrypto contains lots of stuff that most likely
isn't DFSG free. I think it shouldn't be packaged
until these issues have been resolved with the upstream.
/********************************************************************\
* FILE: rmd160.c
* CONTENTS: A sample C-implementation of the RIPEMD-160 hash-function.
* TARGET: any computer with an ANSI C compiler
* AUTHOR: Antoon Bosselaers, Dept. Electrical Eng.-ESAT/COSIC
* DATE: 1 March 1996 VERSION: 1.0
**********************************************************************
* Copyright (c) Katholieke Universiteit Leuven 1996, All Rights Reserved
* The Katholieke Universiteit Leuven makes no representations concerning
* either the merchantability of this software or the suitability of this
* software for any particular purpose. It is provided "as is" without
* express or implied warranty of any kind. These notices must be retained
* in any copies of any part of this documentation and/or software.
\********************************************************************/
I'm seeing whether I can get MD4 added to PyOpenSSL,
and whether I can use that. I won't be uploading
pycrypto.
--
:(){ :|:&};:
Reply to: