Hi Antoine
After some investigation I found that the count for the mentioned error
was not slowly evolving, it was appearing at beginning of March a lot
more than before. So I checked for changes on my side and found I had
prolonged delays for hosts that are dns blacklisted too much (I set a
smal
On 2017-03-30 06:06:48, Adrian Zaugg wrote:
> Hi Antoine
>
> On 29.03.17 22:21, Antoine Beaupré wrote:
>> On 2017-03-29 19:32:33, Adrian Zaugg wrote:
>> Litterally, "backporting" would mean uploading to wheezy-backports, and
>> there is already a backport there:
> I saw that one, but I think it is
Hi Antoine
On 29.03.17 22:21, Antoine Beaupré wrote:
> On 2017-03-29 19:32:33, Adrian Zaugg wrote:
> Litterally, "backporting" would mean uploading to wheezy-backports, and
> there is already a backport there:
I saw that one, but I think it is missing some security fixes.
> Now, maybe a backport
On 2017-03-29 19:32:33, Adrian Zaugg wrote:
> Is backporting a newer version an option?
Litterally, "backporting" would mean uploading to wheezy-backports, and
there is already a backport there:
https://packages.debian.org/source/wheezy-backports/gnutls28
Since gnutls26 is not in jessie or any l
On 29/03/17 19:32, Adrian Zaugg wrote:
>> I would tend towards fixing this only if it's the former, not the
>> latter. This is, after all, why we want people to upgrade...
> It is wise to upgrade in many situations and I completely agree that the
> newer versions solve many problems. There are situ
On 29/03/17 21:31, Carlos Alberto Lopez Perez wrote:
> Given that Wheezy LTS EOL is in 2 months [1]
Sorry. That is wrong. Wheezy LTS EOL is in 1 year and 2 months.
/me goes for some more coffee.
signature.asc
Description: OpenPGP digital signature
On 29.03.17 16:36, Antoine Beaupré wrote:
> Is this a regression in GnuTLS? Or just an aggravating problem from the
> rising adoption of SHA-512?
I don't think the only problem with libgnutls26 is SHA-512. As it seems
the mentioned error can occur in many situations, some for example write
about
On 2017-03-29 13:41:54, Adrian Zaugg wrote:
> I know LTS is not about fixing bugs, this one is critical though and it
> affects probably many wheezy installations. As it gets worse with time,
> it might be that some one would like to care anyway or maybe there is a
> known solution to this problem
Dear Longtermers
Watching the exim logs of my wheezy server, I discover a lot of
connection aborts of incoming TLS connections. The error is quite
generic: "A TLS packet with unexpected length was received." This seems
to be a often observed problem since long time.
Unfortunately the error is in
