From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: OpenSSH client bug CVE-2016-0777
Date: Sun, 17 Jan 2016 19:16:15 +0000 [thread overview]
Message-ID: <1453058175.5665.110.camel@ipfire.org> (raw)
In-Reply-To: <569B6B61.7050905@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1257 bytes --]
Hi,
On Sun, 2016-01-17 at 11:22 +0100, Matthias Fischer wrote:
> Hi Michael,
>
> On 14.01.2016 18:56, Michael Tremer wrote:
> > could you please update OpenSSH to the latest version to fix the
> > latest
> > security bugs:
> >
> > http://www.undeadly.org/cgi?action=article&sid=20160114142733
> >
> > It should not be anything difficult, but should be patched in
> > IPFire
> > today if we can.
>
> Since there was no further feedback on this and because I don't know
> exactly, when the next update will be ready (or if the patch came too
> late?):
Nah the patch is alright. Also merged.
> Would it make sense, if I offer an update on the list - to those
> which
> are interested in testing it - the same way as 'dnsmasq 2.75'?
An update to what? Like binary? Probably not because we want to have a
defined state of the machines. So when people install Core Update X, we
should be sure that there is actually the full set of software
installed and running.
>
> Its running without seen problems here since 15.01.2016 / ~6pm. ;-)
>
> Package is at the usual place:
> http://people.ipfire.org/~mfischer/openssh-7.1p2-for-ipfire.tar.gz
> MD5: 6b8d0a7abd429014a942bad6371f2cf4
>
> Best,
> Matthias
-Michael
P.S. Don't forget to CC the list.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next parent reply other threads:[~2016-01-17 19:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <569B6B61.7050905@ipfire.org>
2016-01-17 19:16 ` Michael Tremer [this message]
2016-01-17 19:24 ` Matthias Fischer
2016-01-14 17:56 Michael Tremer
2016-01-14 19:44 ` Matthias Fischer
2016-01-15 16:44 ` Matthias Fischer
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=1453058175.5665.110.camel@ipfire.org \
--to=michael.tremer@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