From: moabeat-berlin <moabeat-berlin@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] openssh: update to 9.6p1
Date: Tue, 19 Dec 2023 14:56:28 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47829@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 689 bytes --]
There is a new pull request by moabeat-berlin against master on the void-packages repository
https://github.com/moabeat-berlin/void-packages update/openssh-9.6p1
https://github.com/void-linux/void-packages/pull/47829
openssh: update to 9.6p1
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### Local build testing
- I built this PR locally for my native architecture, x86_64-musl.
#### Additional Info
- Fix for the just release [Terrapin Attack](https://terrapin-attack.com/).
A patch file from https://github.com/void-linux/void-packages/pull/47829.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update/openssh-9.6p1-47829.patch --]
[-- Type: text/x-diff, Size: 1129 bytes --]
From 907afd786093753878112e1ace7dc06103f20cb1 Mon Sep 17 00:00:00 2001
From: Moabeat <moabeat@berlin.de>
Date: Tue, 19 Dec 2023 14:52:08 +0100
Subject: [PATCH] openssh: update to 9.6p1
---
srcpkgs/openssh/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/openssh/template b/srcpkgs/openssh/template
index 875bd7d553675..cd2586738faa0 100644
--- a/srcpkgs/openssh/template
+++ b/srcpkgs/openssh/template
@@ -1,6 +1,6 @@
# Template file for 'openssh'
pkgname=openssh
-version=9.5p1
+version=9.6p1
revision=1
build_style=gnu-configure
configure_args="--datadir=/usr/share/openssh
@@ -25,7 +25,7 @@ maintainer="Leah Neukirchen <leah@vuxu.org>"
license="BSD-2-Clause, ISC"
homepage="https://www.openssh.com"
distfiles="https://ftp.openbsd.org/pub/OpenBSD/OpenSSH/portable/${pkgname}-${version}.tar.gz"
-checksum=f026e7b79ba7fb540f75182af96dc8a8f1db395f922bbc9f6ca603672686086b
+checksum=910211c07255a8c5ad654391b40ee59800710dd8119dd5362de09385aa7a777c
conf_files="/etc/ssh/moduli /etc/ssh/ssh_config /etc/ssh/sshd_config /etc/pam.d/sshd"
make_dirs="
/var/chroot/ssh 0755 root root
next reply other threads:[~2023-12-19 13:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 13:56 moabeat-berlin [this message]
2023-12-19 16:31 ` [PR PATCH] [Closed]: " moabeat-berlin
2023-12-19 15:32 [PR PATCH] " leahneukirchen
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47829@inbox.vuxu.org \
--to=moabeat-berlin@users.noreply.github.com \
--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).