public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Arne Fitzenreiter <arne_f@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] OpenSSH: update to 8.2p1
Date: Sun, 22 Mar 2020 16:52:08 +0100	[thread overview]
Message-ID: <906809a18b0c57d118d107065d6ec814@ipfire.org> (raw)
In-Reply-To: <307078a6-b2d9-a265-0b93-bcfa542b39ca@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2636 bytes --]

We need the patches for glibc-2.31 because this update is also planned.

Michael has already send the patches but I have not pushed this yet 
because
at least netsnmpd fails.

Arne


Am 2020-03-21 21:08, schrieb Peter Müller:
> Please refer to https://www.openssh.com/txt/release-8.2 for release
> announcements. Since glibc < 2.31 is used, no additional patching was
> required in order to restore correct login functionality.
> 
> Cc: Marcel Lorenz <marcel.lorenz(a)ipfire.org>
> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
> ---
>  config/rootfiles/common/openssh | 2 ++
>  lfs/openssh                     | 6 +++---
>  2 files changed, 5 insertions(+), 3 deletions(-)
> 
> diff --git a/config/rootfiles/common/openssh 
> b/config/rootfiles/common/openssh
> index b41190a47..f2f8ea6c5 100644
> --- a/config/rootfiles/common/openssh
> +++ b/config/rootfiles/common/openssh
> @@ -21,6 +21,7 @@ usr/bin/ssh-keyscan
>  usr/lib/openssh/sftp-server
>  usr/lib/openssh/ssh-keysign
>  usr/lib/openssh/ssh-pkcs11-helper
> +usr/lib/openssh/ssh-sk-helper
>  usr/sbin/sshd
>  #usr/share/man/man1/scp.1
>  #usr/share/man/man1/sftp.1
> @@ -35,4 +36,5 @@ usr/sbin/sshd
>  #usr/share/man/man8/sftp-server.8
>  #usr/share/man/man8/ssh-keysign.8
>  #usr/share/man/man8/ssh-pkcs11-helper.8
> +#usr/share/man/man8/ssh-sk-helper.8
>  #usr/share/man/man8/sshd.8
> diff --git a/lfs/openssh b/lfs/openssh
> index 64e72d654..68a7d63cd 100644
> --- a/lfs/openssh
> +++ b/lfs/openssh
> @@ -1,7 +1,7 @@
>  
> ###############################################################################
>  #                                                                      
>        #
>  # IPFire.org - A linux based firewall                                  
>        #
> -# Copyright (C) 2007-2019  IPFire Team  <info(a)ipfire.org>              
>        #
> +# Copyright (C) 2007-2020  IPFire Team  <info(a)ipfire.org>              
>        #
>  #                                                                      
>        #
>  # This program is free software: you can redistribute it and/or modify 
>        #
>  # it under the terms of the GNU General Public License as published by 
>        #
> @@ -24,7 +24,7 @@
> 
>  include Config
> 
> -VER        = 8.1p1
> +VER        = 8.2p1
> 
>  THISAPP    = openssh-$(VER)
>  DL_FILE    = $(THISAPP).tar.gz
> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
> 
>  $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
> 
> -$(DL_FILE)_MD5 = 513694343631a99841e815306806edf0
> +$(DL_FILE)_MD5 = 3076e6413e8dbe56d33848c1054ac091
> 
>  install : $(TARGET)

  parent reply	other threads:[~2020-03-22 15:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-21 20:08 Peter Müller
2020-03-22  9:24 ` Michael Tremer
2020-03-22 15:52 ` Arne Fitzenreiter [this message]
2020-03-24 13:18   ` Peter Müller
2020-03-24 14:29     ` Michael Tremer
2020-04-09 16:51     ` Arne Fitzenreiter
2020-04-09 20:58       ` Michael Tremer

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=906809a18b0c57d118d107065d6ec814@ipfire.org \
    --to=arne_f@ipfire.org \
    --cc=development@lists.ipfire.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