You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Urh Srečnik (Jira)" <ji...@apache.org> on 2023/09/09 09:06:00 UTC

[jira] [Created] (WAGON-633) ssh-external issues with "ForceCommand internal-sftp"

Urh Srečnik created WAGON-633:
---------------------------------

             Summary: ssh-external issues with "ForceCommand internal-sftp"
                 Key: WAGON-633
                 URL: https://issues.apache.org/jira/browse/WAGON-633
             Project: Maven Wagon
          Issue Type: Improvement
          Components: wagon-ssh-external
    Affects Versions: 3.5.3
            Reporter: Urh Srečnik


Current implementation relies on "scp" and "ssh" external commands. I propose to only use "sftp" external command because if sshd config contains "ForceCommand internal-sftp" then:

1) "ssh" command cannot be used

2) "scp" command requires version >= 9.0 (this issue is also described here: [https://serverfault.com/questions/420457/openssh-anything-like-internal-sftp-but-for-scp] )

 

I have implemented such wagon provider (sftp only) and published it here (this is basically a proof of concept which solves my problem, but would need a bit more work to support Windows environments etc):
[https://github.com/usrecnik/maven-wagon-ssh-sftp]

 

Should i provide a pull request to current ssh-external project? I'm not sure if this should be considered as an improvement to existing ssh-external or should it be treated as another implementation of a wagon provider.

I'm happy to help and I would like official wagon to support "ForceCommand internal-sftp" configuration - how should we proceed?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)