From mboxrd@z Thu Jan 1 00:00:00 1970 From: Junichi Uekawa Subject: Re: [PATCH] use gcrypt instead of libssl for hash Date: Mon, 18 Apr 2005 07:36:06 +0900 Message-ID: <87fyxp1161.dancerj@netfort.gr.jp> References: <87hdi5oet6.dancerj@netfort.gr.jp> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8BIT Cc: Junichi Uekawa , git@vger.kernel.org X-From: git-owner@vger.kernel.org Mon Apr 18 00:32:24 2005 Return-path: Received: from vger.kernel.org ([12.107.209.244]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DNIJP-00023g-7i for gcvg-git@gmane.org; Mon, 18 Apr 2005 00:32:19 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261531AbVDQWgL (ORCPT ); Sun, 17 Apr 2005 18:36:11 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261532AbVDQWgK (ORCPT ); Sun, 17 Apr 2005 18:36:10 -0400 Received: from 68.105.138.210.bn.2iij.net ([210.138.105.68]:1808 "HELO viper2.netfort.gr.jp") by vger.kernel.org with SMTP id S261531AbVDQWgI convert rfc822-to-8bit (ORCPT ); Sun, 17 Apr 2005 18:36:08 -0400 Received: (qmail 25438 invoked from network); 17 Apr 2005 22:36:06 -0000 Received: from unknown (HELO atoron.dancer.pr.jp.netfort.gr.jp) (127.0.0.1) by viper2.netfort.gr.jp with SMTP; 17 Apr 2005 22:36:06 -0000 To: Linus Torvalds In-Reply-To: User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.6 (Maruoka) FLIM/1.14.6 (Marutamachi) APEL/10.6 Emacs/21.4 (i386-pc-linux-gnu) MULE/5.0 (SAKAKI) Sender: git-owner@vger.kernel.org Precedence: bulk X-Mailing-List: git@vger.kernel.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/