You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Brad Davis (JIRA)" <ji...@apache.org> on 2007/03/08 00:11:24 UTC

[jira] Updated: (VFS-115) Sftp should support keypairs and private keys in locations other than fies

     [ https://issues.apache.org/jira/browse/VFS-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brad Davis updated VFS-115:
---------------------------

    Attachment: patch.txt

this is a first pass patch that replaces the functionality of specifying identites by file objects with specifying them with VFS urls.  it breaks compatibility with existing code specifying files, but with some small amount of additional work back-incompatibly could likely be maintained by changing File specifications to local filesystems URLS on the fly in the internals of the session builder.  I'll try to work on a second patch implementing this later on.

> Sftp should support keypairs and private keys in locations other than fies
> --------------------------------------------------------------------------
>
>                 Key: VFS-115
>                 URL: https://issues.apache.org/jira/browse/VFS-115
>             Project: Commons VFS
>          Issue Type: Improvement
>            Reporter: Brad Davis
>            Priority: Minor
>         Attachments: patch.txt
>
>
> I am attempting to use jar based keypairs in several applications I am developing.  Unfortunately because the SFTP configuration only allows for a file to be specified for the private key, in order to use a key stored in a resource I have to first copy the resource to the local filesystem and then use that temporary file.  I'd much rather that I could specify the location of the location of private key as a VFS url.  Jsch supports using a byte array instead of a file to specify the private key, so VFS could be used to turn the URL into a byte array and pass that to JSCH instead.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org