From: 5p9 <5p9@ipfire.org>
To: development@lists.ipfire.org
Subject: libgcrypt new version *fix a critical security problem*
Date: Thu, 18 Aug 2016 13:10:44 +0200 [thread overview]
Message-ID: <8bcbb899-bacc-e788-8e86-20ca7998858e@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 230 bytes --]
Hi @ all,
for your information. I found a new version for libgcrypt, see
http://www.linuxfromscratch.org/blfs/view/svn/general/libgcrypt.html or
https://lists.gnupg.org/pipermail/gnupg-announce/2016q3/000395.html
BR,
Thomas
next reply other threads:[~2016-08-18 11:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 11:10 5p9 [this message]
2016-08-22 2:01 ` Michael Tremer
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=8bcbb899-bacc-e788-8e86-20ca7998858e@ipfire.org \
--to=5p9@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