public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: "Paul Traina" <pst@juniper.net>
To: "Sartoretti Pascal" <psa@elca.ch>, <gnats-devel@sourceware.cygnus.com>
Cc: "Dieperink Alwin" <alwin.dieperink@elca-matrix.ch>
Subject: Re: GNATS: 2 features needed
Date: Wed, 05 Jul 2000 11:04:00 -0000	[thread overview]
Message-ID: <00d601bfe6ab$46918040$fba8c73f@shockwave.org> (raw)
In-Reply-To: <A13B47F8EC3FD111A91500C04FD2A282DD362E@exchange.elca.ch>

They are not planned.  Please implement using the 4.0 code and send the
diffs back to us for review.

----- Original Message -----
From: "Sartoretti Pascal" <psa@elca.ch>
To: <gnats-devel@sourceware.cygnus.com>
Cc: "Dieperink Alwin" <alwin.dieperink@elca-matrix.ch>
Sent: Tuesday, July 04, 2000 5:42 AM
Subject: GNATS: 2 features needed


> Hello,
>
> We are happy users of GNATS and gnatsweb. We currently use them only
> internally for customer projetcs, we would like also to give direct access
> to some customers via the Internet. To allow this, we need two new
features:
>
> 1- In gnatsweb, add the possibility for a user to change his
> password.
>
> 2- Currently, passwords are stored in plain text format in the
> configuration file. We would like them to be stored in a
> cyphered way (e.g. MD5).
>
> We need these two features so much that we are ready to implement them
> if needed. Could you tell us if they are already planned in a next
> version of GNATS/gnatsweb? By the way, do you feel any interest for
> them?
>
> Thanks in advance
>
> Pascal Sartoretti
>
> ==============================================
> Pascal Sartoretti Tel: +41 21 613 21 11
> ELCA Informatique SA Fax: +41 21 613 21 00
> Av. de la Harpe 22-24 Pascal.Sartoretti@elca.ch
> < mailto:Pascal.Sartoretti@elca.ch >
> CH-1000 Lausanne 13, Switzerland
>
>
>

      reply	other threads:[~2000-07-05 11:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-04  5:45 Sartoretti Pascal
2000-07-05 11:04 ` Paul Traina [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

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

  git send-email \
    --in-reply-to='00d601bfe6ab$46918040$fba8c73f@shockwave.org' \
    --to=pst@juniper.net \
    --cc=alwin.dieperink@elca-matrix.ch \
    --cc=gnats-devel@sourceware.cygnus.com \
    --cc=psa@elca.ch \
    /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).