From owner-freebsd-current@FreeBSD.ORG Fri Jun 18 18:03:08 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CD90A106564A; Fri, 18 Jun 2010 18:03:08 +0000 (UTC) (envelope-from oberman@es.net) Received: from mailgw.es.net (mail1.es.net [IPv6:2001:400:201:1::2]) by mx1.freebsd.org (Postfix) with ESMTP id 7C4838FC18; Fri, 18 Jun 2010 18:03:08 +0000 (UTC) Received: from ptavv.es.net (ptavv.es.net [IPv6:2001:400:910::29]) by mailgw.es.net (8.14.3/8.14.3) with ESMTP id o5II32Ds016434 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 18 Jun 2010 11:03:03 -0700 Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 99F5D1CC0D; Fri, 18 Jun 2010 11:03:02 -0700 (PDT) To: Doug Barton In-reply-to: Your message of "Thu, 17 Jun 2010 14:56:35 PDT." <4C1A9A13.7030206@FreeBSD.org> Date: Fri, 18 Jun 2010 11:03:02 -0700 From: "Kevin Oberman" Message-Id: <20100618180302.99F5D1CC0D@ptavv.es.net> X-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.8161:2.4.5, 1.2.40, 4.0.166 definitions=2010-06-18_03:2010-02-06, 2010-06-18, 2010-06-18 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=5.0.0-1005130000 definitions=main-1006180107 Cc: current Subject: Re: Having a problem with security/libassuan-1 when compiling gnupg. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jun 2010 18:03:09 -0000 > Date: Thu, 17 Jun 2010 14:56:35 -0700 > From: Doug Barton > > [ FYI, this message should have gone to freebsd-ports@FreeBSD.org ... ] > > On 06/17/10 11:20, Kevin Oberman wrote: > > 2.0.0 should be the preferred version, but its API is incompatible with > > the old one. Many ports using libassuan (listed in UPDATING) have not > > been updated to support V2, so the libassuan-1 port was created. > > > > As soon as deskutils/kdepim4 and security/{dirmngr|gnupg|gpa|opensc} are > > updated, there will be a need to move to 2.0.0. > > Well, I just made it a lot worse. :) As Kevin points out here, the new > version of libassuan is not compatible with the old. This decision on > the part of the gnupg folks has its merits, but is unarguably > inconvenient during the transition. > > On May 11th I approached the authors of the ports that depend on > libassuan asking about their plans for updating (minus ale@ > unfortunately, opensc's dependency is conditional, thus I missed it > until I grep'ed the tree instead of relying on INDEX). The status of the > affected ports is as follows: > 1. gnupg Already handled because 2.0.15 required the update > 2. dirmngr They had an RC ready to go, which they released after I poked > them a bit. :) > > So these first 2 are now done. > > 3. kdepim4 My understanding is that the version currently under > development has support for libassuan 2.0.0, and will be released in > August. The kde@ folks have indicated that if there is a need to update > it sooner they can most likely do that based on patches that are > currently available. > 4. gpa The svn version supports assuan 2.0.0, but the release of this > new version has not yet been scheduled. > 5. opensc ale@ has indicated that he would prefer to wait to update his > port until a new version that supports assuan 2.0.0 is released. > > > I am unsure what happens when some ports want v1 and others want v2. > > This may not be an issue if the updated ports can be deal with either > > API, but I have no idea whether that is the case. > > The current situation is that having both versions installed is > incompatible. My preference would be that the maintainers of the > affected ports upgrade to depend on assuan 2.0.0 and then we can remove > libassuan-1. If it becomes necessary to support having both versions > installed then "Plan C" at this point would be to modify libassuan-1 to > support this. OK. I see dirmgr and gnupg are now ready for libausaan V2.0.0, but I also have opensc installed and MUST have it working. If I upgrade to libassuan-2.0.0, will that break opensc? I assume, since it was not a shared library, that this will not be a problem, but I wanted to be sure. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751