From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Amirouche Boubekki <amirouche@hypermove.net>
Cc: guile-user@gnu.org,
guile-user <guile-user-bounces+amirouche=hypermove.net@gnu.org>
Subject: Re: UUID3 implementation for Guile
Date: Tue, 9 Jan 2018 14:29:43 +0100 [thread overview]
Message-ID: <20180109132943.2mhujlxz4hyeqlc5@floriannotebook> (raw)
In-Reply-To: <2a9cacddebb25ab38af93be00e76fe69@hypermove.net>
[-- Attachment #1: Type: text/plain, Size: 1218 bytes --]
On Tue, Jan 09, 2018 at 11:00:26AM +0100, Amirouche Boubekki wrote:
> […]
> I think it's better to rely on libgcrypt and gnutls. I don't
> do that myself, yet, because industria is the easy solution.
>
> The problem with industria is that we are not sure it's used
> by people and that the cryptography is correct. Whereas libgcrypt
> and gnutls have a much wider audience with less chances of bugs
> and compromissions.
>
Rereading the old thread, if there are not any new options I will use
gcrypt with some sort of FFI. Thank you!
> Can you explain how do you use md5 and uuid3 with haunt?
>
> FWIW I would prefer to use something base62, instead of exposing
> a md5 hash directly.
I need to automatically generate unique ids for Haunt’s Atom feeds and
for the CSS of a non-JavaScript sortable HTML table (i.e. multiple
variants of the same table between which one can switch with CSS).
The automatic generation should be deterministic so the page does not
change when rebuilding the Web site. That is why I wanted to use
UUID3 for it. I thought security need not be considered here but who
knows, maybe I should just use a secure hash instead of a UUID.
Regards,
Florian
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-01-09 13:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 14:58 UUID3 implementation for Guile pelzflorian (Florian Pelz)
2018-01-08 15:47 ` pelzflorian (Florian Pelz)
2018-01-09 10:00 ` Amirouche Boubekki
2018-01-09 13:29 ` pelzflorian (Florian Pelz) [this message]
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=20180109132943.2mhujlxz4hyeqlc5@floriannotebook \
--to=pelzflorian@pelzflorian.de \
--cc=amirouche@hypermove.net \
--cc=guile-user-bounces+amirouche=hypermove.net@gnu.org \
--cc=guile-user@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.
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).