From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] openssh: restore upstream's default for PermitRootLogin
Date: Fri, 17 Jan 2020 16:36:05 +0100 [thread overview]
Message-ID: <20200117153605.DNn8b2cBjsc8dqH_69xwG-WTPa1Kta0lvck9jqkdBdI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-17596@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 535 bytes --]
There is an updated pull request by Piraty against master on the void-packages repository
https://github.com/Piraty/void-packages openssh-root-login
https://github.com/void-linux/void-packages/pull/17596
openssh: restore upstream's default for PermitRootLogin
restore upstream's default for PermitRootLogin, which currently is 'prohibt-password'.
Should be discussed in conjunction with https://github.com/void-linux/void-mklive/pull/100.
A patch file from https://github.com/void-linux/void-packages/pull/17596.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-openssh-root-login-17596.patch --]
[-- Type: text/x-diff, Size: 1289 bytes --]
From d9b72e43d3d3df23237d56a2381d6a2b0e722a1f Mon Sep 17 00:00:00 2001
From: Piraty <piraty1@inbox.ru>
Date: Wed, 18 Dec 2019 14:52:57 +0100
Subject: [PATCH] openssh: restore PermitRootLogin to default
which currently is 'prohibt-password'.
This reverts ca84fd0a9aea0dd94dde6fd1f9a6a509cec5a789.
---
srcpkgs/openssh/template | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/srcpkgs/openssh/template b/srcpkgs/openssh/template
index 5dc97b69ca4..6ac5ad0060c 100644
--- a/srcpkgs/openssh/template
+++ b/srcpkgs/openssh/template
@@ -1,7 +1,7 @@
# Template file for 'openssh'
pkgname=openssh
version=8.1p1
-revision=1
+revision=2
build_style=gnu-configure
configure_args="--datadir=/usr/share/openssh
--sysconfdir=/etc/ssh --without-selinux --with-privsep-user=nobody
@@ -53,12 +53,11 @@ post_install() {
vman contrib/ssh-copy-id.1
vlicense LICENCE
- sed -i \
+ # configure to use PAM
+ vsed -i ${DESTDIR}/etc/ssh/sshd_config \
-e 's|^#\(UsePAM\) no|\1 yes|g' \
- -e 's|^#\(PermitRootLogin\) .*|\1 yes|g' \
-e 's|^#\(ChallengeResponseAuthentication\) yes|\1 no|g' \
- -e 's|^#\(PrintMotd\) yes|\1 no|g' \
- ${DESTDIR}/etc/ssh/sshd_config
+ -e 's|^#\(PrintMotd\) yes|\1 no|g'
vinstall ${FILESDIR}/sshd.pam 644 etc/pam.d sshd
vsv sshd
parent reply other threads:[~2020-01-17 15:36 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-17596@inbox.vuxu.org>]
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=20200117153605.DNn8b2cBjsc8dqH_69xwG-WTPa1Kta0lvck9jqkdBdI@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).