Return-Path: <bodewig@apache.org>
Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Delivered-To: mailing list dev@ant.apache.org
Received: (qmail 93024 invoked from network); 21 Feb 2003 16:47:40 -0000
Received: from bodewig.bost.de (195.227.98.11)
  by daedalus.apache.org with SMTP; 21 Feb 2003 16:47:40 -0000
Received: (from bodewig@localhost)
	by bodewig.bost.de (8.11.6/8.11.6) id h1LGlfi21589;
	Fri, 21 Feb 2003 17:47:41 +0100
X-Authentication-Warning: bodewig.bost.de: bodewig set sender to
 bodewig@apache.org using -f
To: dev@ant.apache.org
Subject: Re: SCP Ant Syntax (was Contributing to Optional Tasks)
References: 
 <51C603B9AB4696408D7273AA133734AC02B23884@ljcms002.prod.vectorscm.com>
From: Stefan Bodewig <bodewig@apache.org>
Date: 21 Feb 2003 17:47:41 +0100
In-Reply-To: 
 <51C603B9AB4696408D7273AA133734AC02B23884@ljcms002.prod.vectorscm.com>
Message-ID: <m3of55r36a.fsf@bodewig.bost.de>
Lines: 23
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Military Intelligence)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

On Fri, 21 Feb 2003, Rob H. Anderson <Anderson.Rob@vectorscm.com>
wrote:

> For ssh keys, when supported, what would the usage be?
> 
> Perhaps:
> 
> <scp todir="someuser:somepwd@somehost:/home/dude2/"
> keyfile="/home/dude/.ssh/id_dsa">
>     <fileset basedir="/home/dude/src">
>        <include value="**/*.java"/>
>     </fileset>
> </scp>

keyfile could be optional and default to ${user.home}/.ssh/id_dsa

I'd probably use separate attributes for password and passphrase.
Only one can be specified - passphrase implies key authentication.

Nothing set into stone here, it's not that hard to convince me
otherwise 8-)

Stefan