From: "Ludovic Courtès" <ludo@gnu.org>
To: guile-user@gnu.org, guile-sources@gnu.org, guix-devel@gnu.org
Subject: Guile-Gcrypt 0.4.0 released
Date: Thu, 01 Dec 2022 15:36:03 +0100 [thread overview]
Message-ID: <87r0xjyywc.fsf@gnu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1285 bytes --]
I’m pleased to announce Guile-Gcrypt version 0.4.0:
git clone https://notabug.org/cwebber/guile-gcrypt.git
cd guile-gcrypt
git checkout v0.4.0 # or 425554d4327eeeb60c39e3d4a1b7bc5e36b63953
git tag -v v0.4.0
The ‘git tag -v’ command checks the authenticity of your checkout.
You may need to retrieve the signing key first:
gpg --keyserver pool.sks-keyservers.net \
--recv-keys 3CE464558A84FDC69DB40CFB090B11993D9AEBB5
Guile-Gcrypt provides Guile 3.0/2.x bindings to the GNU Libgcrypt
cryptography library. It provides modules for cryptographic hash
functions, message authentication codes (MAC), public-key cryptography,
strong randomness, and more.
Excerpt from the ‘NEWS’ file:
* Changes in 0.4.0 (since 0.3.0)
** ‘base64-encode’ and ‘base64-decode’ now let you optionally control padding
** New supported algorithms added to (gcrypt hash)
** New supported algorithms added to (gcrypt mac)
** Improvements and fixes to the manual
Guile-Gcrypt does not currently wrap all the Libgcrypt API. Your help
in improving it is very welcome! For bug reports and patches, see:
https://notabug.org/cwebber/guile-gcrypt
Plain email to Chris or myself or guile-user would also work fine. :-)
Ludo’.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 853 bytes --]
next reply other threads:[~2022-12-01 14:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 14:36 Ludovic Courtès [this message]
2022-12-03 22:45 ` Guile-Gcrypt 0.4.0 released Vagrant Cascadian
2022-12-05 14:58 ` Ludovic Courtès
2022-12-06 20:21 ` Jonathan Brielmaier
2022-12-08 16:05 ` Ludovic Courtès
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=87r0xjyywc.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-sources@gnu.org \
--cc=guile-user@gnu.org \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.