From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Stefan Reiter <s.reiter@proxmox.com>
Subject: [pbs-devel] applied: [PATCH proxmox-backup] d/postinst: always fixup termproxy user id and for all users
Date: Tue, 1 Sep 2020 18:02:24 +0200 [thread overview]
Message-ID: <d29438d0-fa97-15e7-fc9e-0333b85249a2@proxmox.com> (raw)
In-Reply-To: <20200901145018.4557-1-s.reiter@proxmox.com>
On 01.09.20 16:50, Stefan Reiter wrote:
> Anyone with a PAM account and Sys.Console access could have started a
> termproxy session, adapt the regex.
>
> Always test for broken entries and run the sed expression to make sure
> eventually all occurences of the broken syntax are fixed.
>
> Signed-off-by: Stefan Reiter <s.reiter@proxmox.com>
> ---
> debian/postinst | 9 ++++-----
> 1 file changed, 4 insertions(+), 5 deletions(-)
>
>
applied, thanks!
prev parent reply other threads:[~2020-09-01 16:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 14:50 [pbs-devel] " Stefan Reiter
2020-09-01 16:02 ` Thomas Lamprecht [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:
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=d29438d0-fa97-15e7-fc9e-0333b85249a2@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=s.reiter@proxmox.com \
/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