From: David S Gathright <David.Gathright@lasp.colorado.edu>
To: gargp@acm.org
Cc: help-gnats@gnu.org
Subject: Re: Trouble using encrypted passwords
Date: Mon, 10 Nov 2003 19:09:00 -0000 [thread overview]
Message-ID: <1068490311.1169.49.camel@red5> (raw)
In-Reply-To: <3FAFE919.8020402@acm.org>
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?
Thanks for the try, though. I can resort to that if needed, but I'd
rather not if there is a simpler way.
DSG
On Mon, 2003-11-10 at 12:38, Pankaj K Garg wrote:
> David S Gathright wrote:
>
> > Hi, all.
> >
> > I'm using a vanilla GNATS 4.0 installation on a Solaris 5.9 box. For
> > some reason, MD5 encryption isn't working for me, so I'm trying standard
> > UNIX crypt() encryption. I'm rather perplexed at the statement in
> > Appendix C of the gnats documentation, which states that "crypt()
> > passwords can be generated by using standard UNIX passwords tools".
> > What tools are these (and do you have any examples of how I can use
> > them)?
>
> Did you try generating the passwords using the 'passwd' command and then
> cuting and pasting from /etc/passwd or /etc/shadow?
--
David S Gathright <David.Gathright@lasp.colorado.edu>
LASP - University of Colorado
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats
next prev parent reply other threads:[~2003-11-10 19:09 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 [this message]
2003-11-10 19:58 ` Pankaj K Garg
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=1068490311.1169.49.camel@red5 \
--to=david.gathright@lasp.colorado.edu \
--cc=gargp@acm.org \
--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).