proposal of new packages: libmhash and libmcrypt

[Stefan Hetzl]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday 27 September 2003 12:13, Corinna Vinschen wrote:
> On Sat, Sep 27, 2003 at 11:34:13AM +0200, Stefan Hetzl wrote:
> > libmcrypt:
> > # setup.hint for libmcrypt-2.5.7-1
> > sdesc:  "a library that provides access to several encryption algorithms"
> > ldesc:  "A library that provides access to several symmetric block and
> > stream encryption algorithms.
> > The following algorithms are implemented: 3-Way, Arcfour, Blowfish,
> > Cast-128 (known as Cast5),
> > Cast-256, DES, Enigma, Gost, Loki97, Panama, RC2, Rijndael-128 (AES),
> > Rijndael-192, Rijndael-256,
> > Safer-sk64, Safer-sk128, Safer+, Serpent, TripleDES, Twofish, Wake, XTea.
> > The block algorithms
> > can be used in the modes CBC, CFB, CTR, ECB, OFB, NOFB, NCFB."
> > category:   Libs
> > requires:   cygwin libltdl3
>
> Isn't that covered by the OpenSSL crypto lib?  Do we need two crypto libs?
> I'm not exactly against inclusion, just curious what the advantage is.
OpenSSL does only implement 7 of the above mentioned algorithms. AES (Advanced 
Encryption Standard - dedicated successor of DES) is not among them.

My personal reason for packaging libmcrypt is that I maintain a program 
(http://steghide.sourceforge.net) that uses libmcrypt and has a lot of users 
that run Windows. Having a libmcrypt package for cygwin would make life 
easier for all who want to compile steghide on Windows.

There is also a libmcrypt php module that has some users, some of them on 
Windows. They could probably also make use of a libmcrypt dll.

> Do you pack them up as dynamically linked libs?
Yes.

Greetings,
Stefan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)

iD8DBQE/dWqbKN/5Ocgn19gRAu/PAJ42mN9q7NRbo/t3QUVY5A280aCAcACffcjA
iXBqVhWmhb5VcbAceWTB0go=
=+B63
-----END PGP SIGNATURE-----