From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: libfreetype CVE FYI
Date: Wed, 21 Oct 2020 19:03:40 +0200 [thread overview]
Message-ID: <87mu0fmryr.fsf@Rainer.invalid> (raw)
In-Reply-To: <ba7ab31e-4f49-8453-ef51-fe40ac156ca8@cornell.edu> (Ken Brown via Cygwin-apps's message of "Tue, 20 Oct 2020 14:00:09 -0400")
Ken Brown via Cygwin-apps writes:
>> https://sourceforge.net/projects/freetype/files/freetype2/2.10.4/
>
> Thanks, Brian. I'll update it.
Did you intend to release this security / minor version update as a test
release? It would seem more prudent to just update the package or do
you expect problems?
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables
next prev parent reply other threads:[~2020-10-21 17:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 16:50 [ITA from Yaakov] freeport2 Ken Brown
2020-05-12 16:53 ` Ken Brown
2020-05-12 18:08 ` Marco Atzeri
2020-05-12 18:34 ` Ken Brown
2020-05-12 19:00 ` Marco Atzeri
2020-05-12 18:02 ` [ITA from Yaakov] freetype2 Yaakov Selkowitz
2020-05-12 18:46 ` Ken Brown
2020-10-20 14:46 ` libfreetype CVE FYI Brian Inglis
2020-10-20 18:00 ` Ken Brown
2020-10-21 17:03 ` Achim Gratz [this message]
2020-10-21 21:20 ` Ken Brown
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=87mu0fmryr.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin-apps@cygwin.com \
/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).