On Mon, 2014-06-16 at 19:08 +0200, Niels Möller wrote: > Maybe as a build option, but not for a normal installation.
That would be worse as there will be multiple ABIs and would require tweaking all the applications that use nettle in order to build one way or another. I'd prefer to have things as is if the only alternative is that. > But I think those applications should use nettle... Adding a gmp > dependency makes that less attractive. > > > In any embedded system using nettle+hogweed > > would require more memory and overhead than having a single library. > > Could you put some numbers to that overhead? I can't say if it's worth > trying to avoid. No, but is there a reason for having it in the first place? Are there really applications that need only symmetric crypto support and can afford linking to a shared library but really don't want to have the public key in that shared library? OpenSSL's libcrypto is used in embedded systems without any complain of the kind (and it includes all kind of crypto). regards, Nikos _______________________________________________ nettle-bugs mailing list [email protected] http://lists.lysator.liu.se/mailman/listinfo/nettle-bugs
