bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bruce Korb <bkorb@gnu.org>
To: bug-gnulib@gnu.org
Subject: gc-pbkdf2-sha1 is deprecated
Date: Fri, 18 Sep 2020 08:58:57 -0700	[thread overview]
Message-ID: <61d0906e-aa38-8c92-8d9f-ece85a8dccbf@gnu.org> (raw)
In-Reply-To: <4725cba4-3dc2-314a-0e1d-fb48c1a51540@gnu.org>

Hi Bruno, et al.,

Next question: what do I do about crypto/gc-pbkdf2-sha1? It is labeled 
as "deprecated", but I need a function that produces precisely the same 
result. It really doesn't matter to me that folks have figured out how 
to jigger a file to produce an arbitrary sha1 sum. I only need a fairly 
random result from summing a few tens of bytes of text. So as long as 
"deprecate" doesn't mean it's going away, I'm fine. I use the code to 
create an unguessable password. Just because it's possible to use 
different source text to produce the same password doesn't matter at all. :)

Cheers - Bruce




  reply	other threads:[~2020-09-18 16:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAKRnqNLXD7waxPm7h=5S2-HkAe9WMVsLDtCuNrOFy_eyJZeZBQ@mail.gmail.com>
     [not found] ` <56102afd-8924-3338-722f-da03e590dd63@gnu.org>
     [not found]   ` <87d02ob434.fsf@herbrand>
2020-09-14 21:11     ` Trying to bootstrap my project, distcheck doesn't configure Bruce Korb
2020-09-14 22:53       ` Bruno Haible
2020-09-15 14:16         ` Bruce Korb
2020-09-18 15:58           ` Bruce Korb [this message]
2020-09-18 16:32             ` gc-pbkdf2-sha1 is deprecated Bruno Haible
2020-09-21 22:49               ` Bruce Korb
2020-09-22 15:04                 ` Bruce Korb
2020-09-22 17:03                   ` Bruno Haible
2020-09-23 16:55                     ` gc-pbkdf2-sha1 must not be deprecated Bruce Korb

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://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=61d0906e-aa38-8c92-8d9f-ece85a8dccbf@gnu.org \
    --to=bkorb@gnu.org \
    --cc=bug-gnulib@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).