Re: [bug-gnulib] Crypto modules

[Paul Eggert]

Simon Josefsson <address@hidden> writes:

> However, if some copyright cannot be tracked down, I could work on
> adapting code from libgcrypt (which is assigned) that would be usable
> in gnulib.

That sounds reasonable to me.

> Savannah has a FAQ regarding crypto code:
> https://savannah.gnu.org/faq/?question=Is_there_any_restriction_on_cryptographic_software.txt
> I'm not sure how problematic the code would be in practice.
>
> What do you think of this?

It looks to me like crypto code won't be a problem, since we have an
exemption, at least for the US.  There might be problems in other
countries but I don't think it'll be an issue for gnulib.

> The package isn't small, about 6kloc.  The ASN.1 library has been
> assigned to the FSF.  Is there some point when a package become too
> large to usefully be included in gnulib?

I don't think the number of lines of code is a problem.  There will be
a problem as gnulib scales up (e.g., collision with existing names,
much as you've already seen for md5 and sha1), but adding one more
module shouldn't break things.