Return-Path: Delivered-To: apmail-xml-security-dev-archive@www.apache.org Received: (qmail 16183 invoked from network); 7 Sep 2005 15:18:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 7 Sep 2005 15:18:21 -0000 Received: (qmail 31073 invoked by uid 500); 7 Sep 2005 15:18:13 -0000 Delivered-To: apmail-xml-security-dev-archive@xml.apache.org Received: (qmail 30956 invoked by uid 500); 7 Sep 2005 15:18:12 -0000 Mailing-List: contact security-dev-help@xml.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: Reply-To: security-dev@xml.apache.org List-Id: Delivered-To: mailing list security-dev@xml.apache.org Received: (qmail 30806 invoked by uid 99); 7 Sep 2005 15:18:11 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Sep 2005 08:18:11 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [67.116.30.6] (HELO red.amberpoint.com) (67.116.30.6) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Sep 2005 08:18:23 -0700 Received: from [127.0.0.1] (jc.edgility.com [10.10.11.16] (may be forged)) by red.amberpoint.com (8.12.9/8.12.9) with ESMTP id j87FI3ph004862 for ; Wed, 7 Sep 2005 08:18:06 -0700 (PDT) Message-ID: <431F0542.3000708@amberpoint.com> Date: Wed, 07 Sep 2005 20:50:34 +0530 From: Vishal Mahajan User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: security-dev@xml.apache.org Subject: Re: Using hardware provider for signing References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Li�e, Jan (ext. Dienstleister) wrote: >Hallo, > >i have the requirement to sign data with a hardware provider (smart card). >According to posts on this mailing-list the recommended way to integrate >a hardware provider into xml-sec is by writing a SignatureAlgorithmSPI-Impl. >and configuring this in config.xml. But this approach lacks some >flexibility. >In my setup i want to be able to switch between a software and a hardware >provider for signing with rsa-sha1. >In a posting from 2004 i read about a patch by Vishal Mahajan that >eliminates the >need for configuring providers in config.xml. Is this patch already >integrated in >the current official release? > Yes it is. Vishal > > >Thanks in advance, >Jan > >