From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] added package sftpserver
Date: Wed, 6 Jun 2012 22:11:13 +0200 [thread overview]
Message-ID: <20120606221113.63a66610@skate> (raw)
In-Reply-To: <CABJxTWFdYodgaKy3vG03aJrxnerCrxTsjRPWm1q8U_XkQukz0w@mail.gmail.com>
Le Mon, 4 Jun 2012 09:26:39 +0200,
Kiril Maler <kiril.maler@gmail.com> a ?crit :
> I see one (possible) reason to add sftp-server as part of openssh
> configuration and directory -
> if in the future there is any security patch, concerning also
> sftp-server source code file,
> then the security fix patch must be added in .../packages/openssh
> only. Most probably this will be fixed by
> moving to next openssh version.
That's the problem I have with your approach: when we want to upgrade
openssh, we will have to upgrade in two different places.
I would very much prefer to see a contribution made to openssh to get
the capability of building / installing only sftp-server, but I'm not
the Buildroot maintainer, so my opinion is just one amongst many
others :)
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-06-06 20:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 7:26 [Buildroot] [PATCH] added package sftpserver Kiril Maler
2012-06-06 20:11 ` Thomas Petazzoni [this message]
2012-06-06 20:13 ` Peter Korsgaard
2012-06-11 21:22 ` Arnout Vandecappelle
2012-06-12 12:12 ` Thomas Petazzoni
2012-06-12 16:24 ` Arnout Vandecappelle
-- strict thread matches above, loose matches on Subject: below --
2012-06-01 14:35 Kiril Maler
2012-06-01 14:57 ` Thomas Petazzoni
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=20120606221113.63a66610@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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