From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 1/7, v3] openssh: replace complete configuration files by patch
Date: Tue, 12 Mar 2024 15:06:38 +0100 [thread overview]
Message-ID: <ly7ci7bl3l.fsf@ensc-pc.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <CANNYZj9NGCR8-R5+9LaE-etEBmx2VnYE+ecQY_Jtq4DbT4mFYQ@mail.gmail.com> (Alexander Kanavin's message of "Tue, 12 Mar 2024 14:10:09 +0100")
Alexander Kanavin <alex.kanavin@gmail.com> writes:
> Why is the patch inappropriate for upstream submission? To me it looks
> like it should be at least proposed.
>
> ++Include /etc/ssh/sshd_config.d/*.conf
Underlying feature exists for 4 years and nearly every major linux
distribution (including OE) has such a line. So I assume there is a
reason that it is not upstream yet.
I added an upstream report
(https://bugzilla.mindrot.org/show_bug.cgi?id=3672) and will update
patch status when resubmitting.
Enrico
next prev parent reply other threads:[~2024-03-12 14:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 17:18 [PATCH 0/7] Replace sshd_config patching by snippets Enrico Scholz
2024-03-11 17:18 ` [PATCH 1/7] openssh: replace complete configuration files by patch Enrico Scholz
2024-03-11 17:41 ` Patchtest results for " patchtest
2024-03-11 18:16 ` [PATCH 1/7, v2] " Enrico Scholz
2024-03-11 18:33 ` Patchtest results for " patchtest
2024-03-12 11:00 ` [PATCH 1/7, v3] " Enrico Scholz
2024-03-12 13:10 ` [OE-core] " Alexander Kanavin
2024-03-12 14:06 ` Enrico Scholz [this message]
2024-03-16 23:58 ` Alexandre Belloni
2024-03-11 17:18 ` [PATCH 2/7] openssh-config: initial checkin Enrico Scholz
2024-03-11 17:41 ` Patchtest results for " patchtest
2024-03-11 18:12 ` Enrico Scholz
2024-03-12 13:14 ` [OE-core] " Trevor Gamblin
2024-03-11 17:18 ` [PATCH 3/7] openssh: move configuration tweaking in configuration recipe Enrico Scholz
2024-03-11 17:18 ` [PATCH 4/7] image: prepare openssh configuration Enrico Scholz
2024-03-11 17:18 ` [PATCH 5/7] openssh: replace 'allow-empty-password' rootfs scipt by configuration Enrico Scholz
2024-03-11 17:18 ` [PATCH 6/7] openssh: replace 'allow-root-login' " Enrico Scholz
2024-03-11 17:18 ` [PATCH 7/7] openssh: move read-only-rootfs setup in configuration snippet Enrico Scholz
2024-03-12 13:14 ` [OE-core] [PATCH 0/7] Replace sshd_config patching by snippets Alexander Kanavin
2024-03-14 11:00 ` Richard Purdie
2024-03-14 14:11 ` Enrico Scholz
2024-03-14 14:27 ` Richard Purdie
[not found] ` <17BC9C80577EA5C2.22340@lists.openembedded.org>
2024-03-14 13:40 ` Richard Purdie
2024-03-14 14:57 ` Enrico Scholz
2024-03-14 17:47 ` Alexander Kanavin
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=ly7ci7bl3l.fsf@ensc-pc.intern.sigma-chemnitz.de \
--to=enrico.scholz@sigma-chemnitz.de \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/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