public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: Pankaj K Garg <gargp@acm.org>
To: David S Gathright <David.Gathright@lasp.colorado.edu>
Cc: help-gnats@gnu.org
Subject: Re: Trouble using encrypted passwords
Date: Mon, 10 Nov 2003 19:58:00 -0000	[thread overview]
Message-ID: <3FAFFDA1.9090805@acm.org> (raw)
In-Reply-To: <1068490311.1169.49.camel@red5>

David S Gathright wrote:
> No, I didn't try that, mostly because I don't have root access on that
> machine. 
> 
> What I guess is most confusing to me is that there are three pieces of
> information:  the raw password, the salt, and the encrypted password. 
> Now, in the MD5 scheme, the salt is stored with the encrypted password
> ($1$salt$enc_password).  However, in the crypt() scheme, there is no
> specified way to store the key, so, how is that done?

Its been a while since I did this, but looking at the code, it seems 
that the salt is '$1$', '$2$', etc. Can you try these with the 
Python/Perl code and see what happens? The source code in gnatsd.c is 
using the C library function 'crypt' with these salts.


-- 
Pankaj K Garg                         garg@zeesource.net
1684 Nightingale Avenue               408-373-4027
Suite 201                             408-733-2737(fax)
Sunnyvale, CA 94087

		http://www.zeesource.net




_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats

  reply	other threads:[~2003-11-10 19:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-10 18:33 David S Gathright
2003-11-10 18:48 ` Pankaj K Garg
2003-11-10 19:09   ` David S Gathright
2003-11-10 19:58     ` Pankaj K Garg [this message]
2003-11-10 22:20       ` David S Gathright
2003-11-10 23:54         ` Hans-Albert Schneider

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=3FAFFDA1.9090805@acm.org \
    --to=gargp@acm.org \
    --cc=David.Gathright@lasp.colorado.edu \
    --cc=help-gnats@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).