From: Jean Abou Samra <jean@abou-samra.fr>
To: Maxime Devos <maximedevos@telenet.be>, guile-user@gnu.org
Cc: Jonas Hahnfeld <hahnjo@hahnjo.de>
Subject: Re: 64-bit Guile on Windows
Date: Wed, 6 Jul 2022 18:33:36 +0200 [thread overview]
Message-ID: <54dc525c-9aaa-edc3-5f75-3b6fb8a65975@abou-samra.fr> (raw)
In-Reply-To: <6791233a2e66404803e97de8efb7ec6b9f77a174.camel@telenet.be>
On 6/28/22 12:52, Maxime Devos wrote:
> Jean Abou Samra schreef op di 28-06-2022 om 10:38 [+0200]:
>> We had exactly the same problem at LilyPond, and this was the fix:
>>
>> https://gitlab.com/lilypond/lilypond/-/blob/master/release/binaries/lib/dependencies.py#L721
>>
> For security, shouldn't this check the hash of the downloaded tarballls
> and patches?
Sorry, I forgot to reply to this. Yes, it likely should. On the other
hand, LilyPond has a lot of much more pressing security issues to care
about…
Jean
next prev parent reply other threads:[~2022-07-06 16:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 13:56 64-bit Guile on Windows Thomas Thiriez via General Guile related discussions
2022-06-27 17:28 ` Jan Nieuwenhuizen
2022-06-27 19:33 ` Thomas Thiriez via General Guile related discussions
2022-06-28 8:38 ` Jean Abou Samra
2022-06-28 10:52 ` Maxime Devos
2022-07-06 16:33 ` Jean Abou Samra [this message]
2022-06-28 14:41 ` Thomas Thiriez via General Guile related discussions
2022-06-28 15:00 ` Thomas Thiriez via General Guile related discussions
2022-06-28 16:14 ` Maxime Devos
2022-06-28 22:07 ` Dr. Arne Babenhauserheide
2022-06-29 9:07 ` Thomas Thiriez via General Guile related discussions
2022-11-22 12:44 ` Jean Abou Samra
2022-11-22 13:22 ` Mike Gran
2023-03-23 23:14 ` Thomas Thiriez via General Guile related discussions
-- strict thread matches above, loose matches on Subject: below --
2022-11-22 14:32 Jean Abou Samra
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54dc525c-9aaa-edc3-5f75-3b6fb8a65975@abou-samra.fr \
--to=jean@abou-samra.fr \
--cc=guile-user@gnu.org \
--cc=hahnjo@hahnjo.de \
--cc=maximedevos@telenet.be \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).