From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] squid: Update to 4.5
Date: Fri, 04 Jan 2019 18:07:10 +0000 [thread overview]
Message-ID: <7DD4FCC4-FF89-45FB-8A9D-86EB85B9F412@ipfire.org> (raw)
In-Reply-To: <3acb0703-c790-e823-fa7d-d24f604ebb1c@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1847 bytes --]
Hey,
indeed. Luckily we are not users of this SSL bump nightmare.
Best,
-Michael
> On 4 Jan 2019, at 18:02, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>
> Hi,
>
> On 02.01.2019 20:11, Michael Tremer wrote:
>>> ...
>>>>
>>>> Why do they compare everything to squid 3.5 then?
>>>
>>> No idea. Perhaps to make upgrading easier for people running
>>> (huge/complex) 3.x-installations? They even still list "missing
>>> squid.conf options available in Squid-2.7"! ;-)
>>>
>>> ...3.x will not be continued, see:
>>>
>>> https://wiki.squid-cache.org/RoadMap/Squid3
>>>
>>> "We are no longer releasing new Squid series with 3.x numbers.”
>>
>> No, it is indeed time to migrate!
>> ...
> Just for completeness - excerpts from the official announcement which
> came today: ;-)
>
> ***SNIP***
> The Squid HTTP Proxy team is very pleased to announce the availability
> of the Squid-4.5 release!
>
> This release is a security and bug fix release resolving several issues
> found in the prior Squid releases.
>
> The major changes to be aware of:
>
> * Bug 4253: ssl_bump prevents access to some web contents
>
> ...
>
> * Redesign forward_max_tries to count TCP connection attempts
>
> ...
>
> * Fix client_connection_mark ACL handling of clientless transactions
>
> ...
>
> * Multiple NetDB behaviour updates
>
> ...
>
> * The logformat code %>handshake is added
>
> ...
>
> * Use pkg-config for detecting libxml2
>
> ...
>
> All users of Squid-4 with SSL-Bump functionality are urged to upgrade
> as soon as possible.
>
> All other users of Squid-4 are encouraged to upgrade as time permits.
>
> All users of Squid-3 are encouraged to upgrade where possible.
> ***SNAP***
>
> The last sentence says it all...
>
> Best,
> Matthias
prev parent reply other threads:[~2019-01-04 18:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 17:39 Matthias Fischer
2019-01-02 17:27 ` Michael Tremer
2019-01-02 18:55 ` Matthias Fischer
2019-01-02 19:01 ` Michael Tremer
2019-01-02 19:10 ` Matthias Fischer
2019-01-02 19:11 ` Michael Tremer
2019-01-04 18:02 ` Matthias Fischer
2019-01-04 18:07 ` Michael Tremer [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=7DD4FCC4-FF89-45FB-8A9D-86EB85B9F412@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