public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: OpenSSH client bug CVE-2016-0777
Date: Fri, 15 Jan 2016 17:44:58 +0100	[thread overview]
Message-ID: <5699220A.8040203@ipfire.org> (raw)
In-Reply-To: <1452794185.5665.68.camel@ipfire.org>

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

Hi,

On 14.01.2016 18:56, Michael Tremer wrote:
> could you please update OpenSSH to the latest version to fix the latest
> security bugs...

Done. ;-)

Best,
Matthias

  parent reply	other threads:[~2016-01-15 16:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-14 17:56 Michael Tremer
2016-01-14 19:44 ` Matthias Fischer
2016-01-15 16:44 ` Matthias Fischer [this message]
     [not found] <569B6B61.7050905@ipfire.org>
2016-01-17 19:16 ` Michael Tremer
2016-01-17 19:24   ` 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=5699220A.8040203@ipfire.org \
    --to=matthias.fischer@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