public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: Yngve Svendsen <yngve.svendsen@clustra.com>
To: Milan Zamazal <pdm@zamazal.org>
Cc: gnats-devel@sources.redhat.com
Subject: Re: Encrypted password patch
Date: Sun, 24 Jun 2001 15:05:00 -0000	[thread overview]
Message-ID: <5.1.0.14.2.20010625000541.00b3fe88@10.10.1.1> (raw)
In-Reply-To: <87vgllyj84.fsf@blackbird.zamazal.org>

At 17:45 24.06.2001 +0200, Milan Zamazal wrote:
>Please note that patch breaks the compilation if the `crypt' function is
>not present.  It should handle the situation reasonably, possibly by
>never matching passwords not starting with $0$; the code must be
>#ifdefed appropriately.

I'll look into it as soon as I can.

>I wouldn't like to make GNATS installation dependent on Perl (despite
>this is only a small utility), so the script should be written in C or
>in sh using standard Unix tools (I'd think about awk, I think it's
>present on every Unix system).

Yes, I'll see what I can get done. The only problem is that calculating MD5 
hashes in a portable way in a shell script might prove to be a real 
challenge. It might be that we need a C program for the job. If so, I'll 
try to specify the intended behaviour to you.

- Yngve

  parent reply	other threads:[~2001-06-24 15:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-20 15:24 Yngve Svendsen
2001-06-21 22:54 ` /etc/qnats-db.conf Margaret BRIERTON
2001-06-22  0:11   ` /etc/qnats-db.conf Yngve Svendsen
2001-06-24 11:26 ` Encrypted password patch Milan Zamazal
2001-06-24 11:34   ` Rick Macdonald
2001-06-24 12:06     ` Milan Zamazal
2001-06-24 12:33       ` Rick Macdonald
2001-06-24 15:19         ` Milan Zamazal
2001-06-24 15:05   ` Yngve Svendsen [this message]
2001-06-24 15:25     ` Milan Zamazal
2001-06-25 23:29       ` cgi_error Margaret BRIERTON
2001-06-26  1:06         ` cgi_error Yngve Svendsen
2001-06-26  6:13   ` Encrypted password patch Yngve Svendsen
2001-06-27 14:45     ` Milan Zamazal

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=5.1.0.14.2.20010625000541.00b3fe88@10.10.1.1 \
    --to=yngve.svendsen@clustra.com \
    --cc=gnats-devel@sources.redhat.com \
    --cc=pdm@zamazal.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).