Forum » Support and Bug Reports »

Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Username

Subject

Message body

Font colour:

Font size:

Options

Disable BBCode in this post

Notify me when a reply is posted (registered users only)

Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

Filename

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

File Comment

Options

Private file (available to author and site moderators only)

Topic review

martin

Re: WinSCP command line not accepting working options from UI

2023-10-05

The private key (ppk) goes to the /privatekey command-line parameter.
https://winscp.net/eng/docs/commandline#privatekey

There's no parameter for the detached certificate. So you either have to use raw session setting DetachedCertificate.
Or use PuTTYgen to add the certificate directly into the ppk file.
https://winscp.net/eng/docs/ui_puttygen#certificate

Guest

2023-10-02 22:01

If using scripts not GUI so then something like

winscp.com /command "open scp://ops@172.20.1.26/ -privatekey=C:\Users\automation\.ssh\generated_ed25519.ppk" "put localfile.txt /remote/path/" "exit"

sparkxy

WinSCP command line not accepting working options from UI

2023-10-02 18:33

I am trying to script out connecting to some Unix hosts via SCP. I have working public key (.ppk format) and auth certificate. If I put this info in the GUI it works perfectly.

Using the same information on the command line tells me it is refused. I have been searching for hours but have not found any useful answers. Can someone help me?

I am trying:

winscp scp://ops@172.20.1.26 /clientcert=C:\Users\automation\.ssh\generated_ed25519.ppk /privatekey=C:\Users\automation\.ssh\server_ed25519_cassh.pub

and I get back:

Searching for host...

Connecting to host...

Authenticating...

Using username "ops".

Server refused our key.

No supported authentication methods available (server sent: publickey)

Authentication log (see session log for details):

Using username "ops".

Server refused our key.



Authentication failed.

winscp>

If this is a simple answer, then I am sorry i didn't find whatever this answer is, google doesn't like me.

Post a reply

Topic review

Re: WinSCP command line not accepting working options from UI

WinSCP command line not accepting working options from UI

Documentation

Support

Associations

Follow Us