mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alexander Dahl <ada@thorsis.com>
To: Ian Abbott <abbotti@mev.co.uk>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] dropbear and sftp-server mismatch
Date: Fri, 29 Apr 2022 07:33:14 +0200	[thread overview]
Message-ID: <Ymt4mnfUwue1Dd9D@ada-deb-carambola.ifak-system.com> (raw)
In-Reply-To: <bd93a0e8-f4eb-15ca-4078-9fdc28f89336@mev.co.uk>

Hello Ian,

Am Thu, Apr 28, 2022 at 07:23:09PM +0100 schrieb Ian Abbott:
> Hi there,
> 
> Since scp now defaults to using the SFTP protocol which is not built in to
> dropbear, I thought I'd configure my platform to enable OPENSSH_SFTP_SERVER,
> but I ran into a 'gotcha'.  The server gets installed as
> "/usr/sbin/sftp-server" (and `--libexecdir` is configured as "/usr/sbin"),

This happens in the OpenSSH package, where libexecdir is configured as
/usr/sbin since 2003 … wow.

> but dropbear looks for it at "/usr/libexec/sftp-server".

Yes.

> The path to the sftp-server can be set in dropbear by defining the
> `SFTPSERVER_PATH` macro in "localoptions.h" file (constructed by
> "rules/dropbear.make").  That is not currently done, but is easy enough to
> add.  I was wondering whether it should be made configurable by a new option
> in "rules/dropbear.in" or not (using "/usr/sbin/sftp-server" as the default
> value).

I would tend to hardcode it into rules/dropbear.make … I don't see a
reason to have that as configurable menu option, do you?  Because we
probably won't change the path in openssh package, and to my knowledge
there's no alternative to the one from openssh?

Care to send a patch?

Greets
Alex




  reply	other threads:[~2022-04-29  5:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28 18:23 Ian Abbott
2022-04-29  5:33 ` Alexander Dahl [this message]
2022-04-29  6:48   ` Michael Olbrich

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=Ymt4mnfUwue1Dd9D@ada-deb-carambola.ifak-system.com \
    --to=ada@thorsis.com \
    --cc=abbotti@mev.co.uk \
    --cc=ptxdist@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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