supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: "Laurent Bercot" <ska-skaware@skarnet.org>
To: "skaware@list.skarnet.org" <skaware@list.skarnet.org>
Cc: "supervision@list.skarnet.org" <supervision@list.skarnet.org>
Subject: [announce] but what about *second* skarnet.org November 2023 release?
Date: Mon, 20 Nov 2023 04:07:56 +0000	[thread overview]
Message-ID: <em311b5ad9-867d-4e63-96a2-3b5c230cb421@2c456439.com> (raw)


  Hello,

  New versions of some skarnet.org packages are available.
  This is mostly a bugfix release, addressing the problems that were
reported since the big release two weeks ago.

  Despite that, s6-dns got a minor version bump because the fixes
needed an additional interface; and s6-networking got a major bump,
because it needed an interface change. Nothing that *should* impact
you, the changes are pretty innocuous; but see below.

skalibs-2.14.0.1        (release)
s6-2.12.0.1            (release)
s6-dns-2.3.7.0            (minor)
s6-networking-2.7.0.0        (major)
tipidee-0.0.2.0            (minor)


  * skalibs-2.14.0.1
    ----------------

  This release is important if you want the fixes in s6-dns: the
ipv6 parsing code has been revamped.

  https://skarnet.org/software/skalibs/
  git://git.skarnet.org/skalibs


  * s6-2.12.0.1
    -----------

  It's only a bugfix, but you want to grab this version, because the
bug was impactful (s6-svscanctl -an not working as intended).

  https://skarnet.org/software/s6/
  git://git.skarnet.org/s6


  * s6-dns-2.3.7.0
    --------------

  - The parsing of /etc/hosts now ignores link-local addresses instead
of refusing to process the whole file.
  - New interface to only process /etc/hosts if a client requires it.

  https://skarnet.org/software/s6-dns/
  git://git.skarnet.org/s6-dns


  * s6-networking-2.7.0.0
    ---------------------

  - s6-tlsc-io has changed interfaces; now it's directly usable from a
terminal. This change should be invisible unless you were using
s6-tlsc-io without going through s6-tlsc (which, until now, there was
no reason to do).
  - s6-tcpserverd now logs "accept" and "reject" instead of "allow" and
"deny", this terminology now being reserved to s6-tcpserver-access.
  - The -h option to s6-tcpclient and s6-tcpserver-access has changed
semantics. Previously it was used to require a DNS lookup, and was 
hardly
ever specified since it was the default (with -H disabling DNS lookups).
Now it means that DNS lookups must be preceded by a lookup in the
hosts database.
  - A new pair of options, -J|-j, are accepted by s6-tlsc-io and
s6-tlsd-io, and by extension the whole TLS chain of tools. -J means that
s6-tls[cd]-io should exit nonzero with an error message if the peer 
fails
to send a close_notify before closing the connection; -j, which is the
default, means ignore it and exit normally.
  - The TLS tunnels work as intended in more corner cases and
pathological situations.

  https://skarnet.org/software/s6-networking/
  git://git.skarnet.org/s6-networking


  *  tipidee-0.0.2.0
     ---------------

  - Bugfixes.
  - New configuration options: "log x-forwarded-for", to log the contents
of the X-Forwarded-For header, if any, along with the request; and
"global executable_means_cgi", to treat any executable file as a CGI
script (which is useful when you control the document hierarchy, but
dangerous when it's left to third-party content manager programs).

  https://skarnet.org/software/tipidee/
  git://git.skarnet.org/tipidee


  Enjoy,
  As always, bug-reports welcome.

--
  Laurent


             reply	other threads:[~2023-11-20  4:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-20  4:07 Laurent Bercot [this message]
2023-11-20 11:20 ` Alexis

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=em311b5ad9-867d-4e63-96a2-3b5c230cb421@2c456439.com \
    --to=ska-skaware@skarnet.org \
    --cc=skaware@list.skarnet.org \
    --cc=supervision@list.skarnet.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).