public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: Milan Zamazal <pdm@zamazal.org>
To: Yngve Svendsen <yngve.svendsen@clustra.com>
Cc: gnats-devel@sources.redhat.com
Subject: Re: GNATS password management
Date: Wed, 27 Jun 2001 14:45:00 -0000	[thread overview]
Message-ID: <87wv5x7ghk.fsf@blackbird.zamazal.org> (raw)
In-Reply-To: <5.1.0.14.2.20010626194604.04dcd278@mail.trd.clustra.com>

>>>>> "YS" == Yngve Svendsen <yngve.svendsen@clustra.com> writes:

    YS> Below is an outline of the two password-management tools I'd
    YS> like to see implemented for GNATS 4.

Thanks.

    YS> gnats-pwconv
    YS> gnats-pwconv [-mp] infile outfile
    YS> gnats-pwconv -n[mp] infile

[...]

    YS> -n, --nocreate	Don't create file; display results on stdout.

This option looks useless to me here.

    YS> gnats-pw
    YS> gnats-pw [-cmdps] passwordfile username accesslevel
    YS> gnats-pw -n[mdps] username accesslevel

I'd call it `gnats-passwd'.

I'm not sure I like specifying `passwordfile' this way (I know htpasswd
does it so).  I'd prefer having an `-f / --file' option instead, thus
making the argument optional, possibly combined with `-d / --database'
for specifying a particular database.  I think it's easier to handle for
GNATS admins -- they don't have to think about the exact names and
locations of the access files.

Using `-d' for database would cause a collision with:

    YS> -d, --crypt	Force CRYPT encryption of the password (default).

but maybe someone can find a better single letter for the --crypt
option.

Regards,

Milan Zamazal

-- 
I think any law that restricts independent use of brainpower is suspect.
                                               -- Kent Pitman in comp.lang.lisp

  reply	other threads:[~2001-06-27 14:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-26 10:51 Yngve Svendsen
2001-06-27 14:45 ` Milan Zamazal [this message]
2001-06-27 14:52   ` Yngve Svendsen
2001-06-29  1:45     ` Milan Zamazal
2001-06-29  1:48       ` Yngve Svendsen
2001-06-30 11:27         ` 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=87wv5x7ghk.fsf@blackbird.zamazal.org \
    --to=pdm@zamazal.org \
    --cc=gnats-devel@sources.redhat.com \
    --cc=yngve.svendsen@clustra.com \
    /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).