Return-Path: Delivered-To: apmail-directory-users-archive@www.apache.org Received: (qmail 3546 invoked from network); 17 Jun 2010 06:38:58 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 17 Jun 2010 06:38:58 -0000 Received: (qmail 16114 invoked by uid 500); 17 Jun 2010 06:38:58 -0000 Delivered-To: apmail-directory-users-archive@directory.apache.org Received: (qmail 15289 invoked by uid 500); 17 Jun 2010 06:38:55 -0000 Mailing-List: contact users-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@directory.apache.org Delivered-To: mailing list users@directory.apache.org Received: (qmail 15066 invoked by uid 99); 17 Jun 2010 06:38:54 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Jun 2010 06:38:54 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=AWL,FREEMAIL_FROM,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of elecharny@gmail.com designates 74.125.82.178 as permitted sender) Received: from [74.125.82.178] (HELO mail-wy0-f178.google.com) (74.125.82.178) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Jun 2010 06:38:47 +0000 Received: by wyj26 with SMTP id 26so3262743wyj.37 for ; Wed, 16 Jun 2010 23:38:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=fH+C0/y9yX67w7/Cqn1rUYotVTQ5G+yrqcmKd6hEN38=; b=dtSC5XMcgZVBhZsYo0Q6UMVuiFnQC2u1F7a7YmZozeP7Yuf+PCY07eWa76pnFal7dG g1+IxV3l+6A7ay0LBtmacmGL4KToZawrHfCLplwkn5W0z/HhOsP4cXlFUM0Xxok/47ow wLWfMDu/SCotARtxpp9vFkEJX7YmFAOP3B6mc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; b=fPWSnU2+ABONlf5mT2LOo2f9HqeXPdN9QY7ql5BEf+GEAj48wriCakWSyWAUpM1PYH 0BFKDboVmlvXnYgwxTL/af8flsOFDXT8pISq6L9KyvH/ARtG2d4/Pq3371BYfTSc7XEV jT4JsubK9SMHpjlFu3+rKDk1iWfzKKZo2fLJ8= Received: by 10.227.143.213 with SMTP id w21mr9706900wbu.63.1276756706547; Wed, 16 Jun 2010 23:38:26 -0700 (PDT) Received: from emmanuel-lecharnys-MacBook-Pro.local ([78.192.106.184]) by mx.google.com with ESMTPS id y31sm61595195wby.4.2010.06.16.23.38.24 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 16 Jun 2010 23:38:24 -0700 (PDT) Message-ID: <4C19C31E.4030502@gmail.com> Date: Thu, 17 Jun 2010 08:39:26 +0200 From: Emmanuel Lecharny Reply-To: elecharny@apache.org User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: users@directory.apache.org Subject: Re: Upgrading to Apache 1.5.7 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit On 6/16/10 11:09 AM, Sudheer Kumar wrote: > Hi > > We are upgrading to Apache 1.5.7 from Apache 1.5.4. We have some approval > issues for certain packages they are: > 1. bouncy castle : bcprov-jdk15-140.jar > > Is it okay to use bouncy castle 1.34 instead of 140? We have > approval for bcprov-jdk15-134 but not for bcprov-jdk15-140.jar. > AFAICR, there is a issue with 1.34 version with some patented encryption algorithm, so we switched to 140. I think you can safely use 1.34,/ > I replaced it with bcprov-jdk15-134 and changed the code > (javax.security.auth.x500.X500Principal.TlsKeyGenerator.java) :- > certGen.generate( privateKey, "BC" ) > to certGen.generateX509Certificate( privateKey, "BC" ); > Hope this is ok? Could you please let me know how to test > this? I mean a test case to test this feature? > I have no idea. Here, you are on your own. > > 2. Jetty: jetty-6.1.14.jar and jetty-util-6.1.14.jar. > I just removed these jars and commented the > org.apache.directory.server.Service.initHttpServer() and removed the > server.integration package. I hope this will not impact Apache DS as any > way Jetty server is not invoked by default and we have no plan to configure > http setting in server.xml. > That's OK. You don't have yo use Jetty if you don't need to, and we are not doing anything special with Jetty atm. It was just addedfor future usage. -- Regards, Cordialement, Emmanuel L�charny www.nextury.com