mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Andreas Pretzsch <apr@cn-eng.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [ANNOUNCE] PTXdist 2019.10.0 released
Date: Tue, 15 Oct 2019 14:38:42 +0200	[thread overview]
Message-ID: <9bfc88cc425f530c2c345af5d637f9455c817f76.camel@cn-eng.de> (raw)
In-Reply-To: <20191015104143.lovvutyopugvkvlg@pengutronix.de>

On Tue, 2019-10-15 at 12:41 +0200, Michael Olbrich wrote:
> On Tue, Oct 15, 2019 at 08:11:10AM +0200, Michael Olbrich wrote:
> > I'm happy to announce that I've just released ptxdist-2019.10.0.
> 
> Right, and 'ptxdist images' is broken in most cases, unless '-q --
> progress'
> is used :-/. There will be a 2019.10.1 release in the near future...

In this case, todays patch "sudo: version bump 1.8.22 -> 1.8.28" from
Roland Hieber should probably also sneek in.
With 1.8.28, a quite relevant security fix is included, see:
https://www.sudo.ws/alerts/minus_1_uid.html

About the "mosquitto: version bump 1.6.4 -> 1.6.7" change, well, there
is one security fix (mosquitto mainline 1.6.6, their ticket #1412) for
an outside triggerable segv / stack overflow. So while debatable if
this qualifies for inclusion in a ptxdist point release, I'd suggest
every user to at least include this one locally...

Best regards,
  Andreas

-- 

carpe noctem engineering
Ingenieurbuero fuer Hard- & Software-Entwicklung Andreas Pretzsch
Dipl.-Ing. (FH) Andreas Pretzsch        Tel. +49-(0)7307-936088-1
Lange Strasse 28a                       Fax: +49-(0)7307-936088-9
89250 Senden, Germany                   email: apr@cn-eng.de


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2019-10-15 12:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-15  6:11 Michael Olbrich
2019-10-15 10:41 ` Michael Olbrich
2019-10-15 12:38   ` Andreas Pretzsch [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=9bfc88cc425f530c2c345af5d637f9455c817f76.camel@cn-eng.de \
    --to=apr@cn-eng.de \
    --cc=ptxdist@pengutronix.de \
    /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