Andreas Metzler writes:
> I just made a test-upload to experimental.
I just found out I may have been wrong about 3.0.7's defaults, and so
this problem might not be fixed yet. I'll investigate soon, and likely
have another upload by this weekend, if we do end up needing one.
Thanks
--
Rob Bro
On 2021-08-28 Vagrant Cascadian wrote:
> I talked to rlb breifly who thought recent versions of guile-3.0 in
> Debian may work around and/or fix the triggering issue for
> guile-gnutls. Would you be up for trying to switch guile-gnutls to
> guile-3.0 again?
Hello,
I just made a test-upload to ex
I talked to rlb breifly who thought recent versions of guile-3.0 in
Debian may work around and/or fix the triggering issue for
guile-gnutls. Would you be up for trying to switch guile-gnutls to
guile-3.0 again?
Thanks for considering!
live well,
vagrant
signature.asc
Description: PGP signatu
Package: guile-3.0
Version: 3.0.4-2
Let's track this properly …
- Forwarded message from Ludovic Courtès -
Date: Fri, 05 Feb 2021 16:16:41 +0100
From: Ludovic Courtès
Subject: Bug#964284: guile-gnutls: update to use guile 3.0
Message-ID: <87y2g235pi@gnu.org>
I forgot
I forgot to mention that a simple workaround (that I’d recommend for
Debian) is to patch Guile >= 2.2.7 (3.0 included) like so:
diff --git a/libguile/numbers.c b/libguile/numbers.c
index 19d2b2d87..de7999861 100644
--- a/libguile/numbers.c
+++ b/libguile/numbers.c
@@ -158,7 +158,7 @@ VARARG_MPZ_IT
Hi all,
Ludovic Courtès skribis:
> Where to go from here? Here are options that come to mind:
>
> • Configure Nettle with ‘--enable-mini-gmp’. However, the manual
> mentions that it’s “slower” and “more likely to leak side-channel
> information” (info "(nettle) Installation").
I tri
Hi Daiki,
Daiki Ueno skribis:
> Ludovic Courtès writes:
>
>> This is because Guile >= 3.0.1 and >= 2.2.7 changes the GMP allocation
>> functions such that they go through libgc¹. As a result, libgc may
>> reuse that memory when it becomes unreachable from its point of view; in
>> this case, si
Hello Ludo,
Ludovic Courtès writes:
> This is because Guile >= 3.0.1 and >= 2.2.7 changes the GMP allocation
> functions such that they go through libgc¹. As a result, libgc may
> reuse that memory when it becomes unreachable from its point of view; in
> this case, since GnuTLS structures are n
Hi,
Ludovic Courtès skribis:
> [10219|3] Peer requested CA: CN=GNUTLS TEST SERVER,OU=GNUTLS,O=FSF,C=GR
> [10219|3] Peer requested CA: CN=GNUTLS INTERMEDIATE TEST
> CA,OU=GNUTLS,O=FSF,C=GR
> [10219|4] checking cert compat with RSA-SHA256
> [10219|3] ASSERT:
> ../../../lib/ext/signature.c[_gnutl
Ludovic Courtès writes:
> It looks as though the public or private key were corrupt, but nothing
> obvious.
>
> Unfortunately, there doesn’t seem to be a similar test case in C. The
> closest one is ‘tls12-rehandshake-cert-auto’, but it uses anonymous
> certificates and different priority string
Hi,
(+Cc: gnutls-help. This is about the failure of
‘guile/tests/reauth.scm’ observed on Debian.)
Thanks Rob & Vagrant. The debugging output Vagrant posted reads:
--8<---cut here---start->8---
[10219|3] Peer requested CA: CN=GNUTLS TEST SERVER,OU=GNUTLS,O=FS
Ludovic Courtès writes:
> On the ‘gnutls_3_6_X’ branch, I can run the following loop for a while
> without experiencing the issue (on x86_64-linux-gnu):
>
> while make check TESTS=tests/reauth.scm ; do : ; done
I was just able reproduce it again in a bullseye (testing) amd64 VM
while building
On 2020-12-07, Andreas Metzler wrote:
> On 2020-12-07 Ludovic Courtès wrote:
>> Vagrant Cascadian skribis:
> [...]
>> > I was never able to reproduce the failure locally on multiple occasions,
>> > although once triggered a rebuild on the buildd machines that failed in
>> > the same way.
>
>> Sam
On 2020-12-07 Ludovic Courtès wrote:
> Vagrant Cascadian skribis:
[...]
> > I was never able to reproduce the failure locally on multiple occasions,
> > although once triggered a rebuild on the buildd machines that failed in
> > the same way.
> Same here and I don’t think we got a report upstrea
Hello,
Vagrant Cascadian skribis:
> On 2020-07-04, Vagrant Cascadian wrote:
>> The attached patch updates guile-gnutls to use guile 3.0, which is the
>> current version of guile, available in unstable and bullseye. It would
>> be ideal if the switch happened before bullseye was released.
>
> Thi
Control: found 964284 3.7.0-1
Control: affects 964284 guix
On 2020-07-04, Vagrant Cascadian wrote:
> The attached patch updates guile-gnutls to use guile 3.0, which is the
> current version of guile, available in unstable and bullseye. It would
> be ideal if the switch happened before bullseye was
Package: guile-gnutls
Version: 3.6.14-2
Severity: normal
Tags: patch
The attached patch updates guile-gnutls to use guile 3.0, which is the
current version of guile, available in unstable and bullseye. It would
be ideal if the switch happened before bullseye was released.
Thanks for maintaining g
17 matches
Mail list logo
