From: Junichi Uekawa <dancer@netfort.gr.jp>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Junichi Uekawa <dancer@netfort.gr.jp>, git@vger.kernel.org
Subject: Re: [PATCH] use gcrypt instead of libssl for hash
Date: Mon, 18 Apr 2005 07:36:06 +0900 [thread overview]
Message-ID: <87fyxp1161.dancerj@netfort.gr.jp> (raw)
In-Reply-To: <Pine.LNX.4.58.0504171039460.7211@ppc970.osdl.org>
Hi,
Thanks for your comments.
> > This is the first time for me to send you a patch; be gentle.
> > the following patch allows for use of gcrypt.
>
> Well, libgcrypt seems to be pretty rare out there - I certainly don't have
> it installed on my machine.
Hmm... okay. Might be the case if you don't use much of GNOME and other
apps.
> > libssl seems to have a restrictive licensing wrt GPL applications.
>
> The GPL makes explicit mention of the system libraries (which openssl
> definitely is by now), so it's ok by the GPL . And I don't see how you'd
> claim that the openssl license doesn't allow it. So it all looks ok by me.
>From a standpoint of Debian Developer; it feels not-so-clear;
since Debian will be distributing openssl and git.
openssl guys seem to recommend adding a quote, which might be sufficient.
"This program is released under the GPL with the additional exemption that compiling, linking, and/or using OpenSSL is allowed."
http://www.openssl.org/support/faq.html#LEGAL2
> But requiring libgcrypt seems silly. Especially as the libgcrypt
> interfaces are horribly ugly, much more so than the openssl ones - so even
> if you use libgcrypt, you don't actually want to use it directly, you want
> to have much nicer wrappers around it.
I'll consider wrappers approach.
regards,
junichi
--
Junichi Uekawa, Debian Developer
17D6 120E 4455 1832 9423 7447 3059 BF92 CD37 56F4
http://www.netfort.gr.jp/~dancer/
next prev parent reply other threads:[~2005-04-17 22:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-17 10:52 [PATCH] use gcrypt instead of libssl for hash Junichi Uekawa
2005-04-17 17:52 ` Linus Torvalds
2005-04-17 22:36 ` Junichi Uekawa [this message]
2005-04-18 3:58 ` Edgar Toernig
2005-04-21 19:48 ` Mozilla SHA1 implementation Linus Torvalds
2005-04-21 22:59 ` Edgar Toernig
2005-04-22 6:49 ` Paul Mackerras
2005-04-22 7:35 ` Paul Mackerras
2005-04-22 15:31 ` Linus Torvalds
2005-04-22 15:40 ` Linus Torvalds
2005-04-22 15:58 ` (anal) Q: Are there any coding styles or development guidelines? Klaus Robert Suetterlin
2005-04-22 17:50 ` Linus Torvalds
2005-04-22 20:29 ` Mozilla SHA1 implementation Daniel Barkalow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fyxp1161.dancerj@netfort.gr.jp \
--to=dancer@netfort.gr.jp \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.