edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Dominique Martinet <asmadeus@codewreck.org>
To: Karl Dahlke <eklhad@comcast.net>
Cc: edbrowse-dev@edbrowse.org
Subject: Re: ftp scp uploads
Date: Mon, 11 Jul 2022 15:18:10 +0900	[thread overview]
Message-ID: <YsvAouCNMp2iDNwh@codewreck.org> (raw)
In-Reply-To: <20220611011118.eklhad@comcast.net>


Karl Dahlke wrote on Mon, Jul 11, 2022 at 01:11:18AM -0400:
> But scp is pretty cool. Give it a try.

Just a warning here: scp the command won't go away, but it switched to
using sftp as underlying protocol in the latest openssh version (8.9)

I'm assuming scp (the protocol) will eventually get disabled, and we
should probably support sftp:// instead -- curl also has support so it
should be the same

> 1. I can't use keys to ssh in; I have to specify login and password,
> which is kind of a pain. Is that a limitation of curl, or is there
> some other way to tell it to use public keys? Some sites only allow
> for ssh with keys.

That should be possible, curl the command has --key / --pubkey to
provide the keypair
(since 7.16.2 according to the documentation)

From a quick grep it looks like the curlopt equivalents are
which should be usable with file path? I haven't tried.

> 2. I have to specify the absolute path, it starts from / not from my
> home directory. This is different I think from how ftp works. Also
> different from the shell scp command, so is confusing.

Not sure but that might be different with sftp as well, might be worth


      reply	other threads:[~2022-07-11  6:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11  5:11 Karl Dahlke
2022-07-11  6:18 ` Dominique Martinet [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YsvAouCNMp2iDNwh@codewreck.org \
    --to=asmadeus@codewreck.org \
    --cc=edbrowse-dev@edbrowse.org \
    --cc=eklhad@comcast.net \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).