From: "Andrew" <inbox@andy.co.uk>
To: "John T. Williams" <jowillia@vt.edu>
Cc: linux-c-programming <linux-c-programming@vger.kernel.org>
Subject: Re: Password Encryption & Philosophy
Date: Sat, 31 May 2003 10:05:57 +0100 [thread overview]
Message-ID: <002801c32759$5c6c9b60$a885bc3e@alanmari> (raw)
In-Reply-To: 000c01c32693$4d336e10$ed64a8c0@descartes
Is it necessary to store the password? IMHO it is bad policy to store the
password anyway because if someone gets physical access to your box they can
access everything without having to even look in the password file. This
could be collegues at work, friends or family at home, quite a lot of people
really. I'd avoid it if possible and not add the 'feature'.
If it has to go in I would encrypt it to disk, what you need to find is
something reasonably uniqe to seed it with. Perhaps a nic mac address or
something like that. Lets face it, if someone is really serious about it
they can get round anything, it only took a couple of weeks for versions of
XP with the security functions completely by-passed to start making the
rounds for instance.
----- Original Message -----
From: "John T. Williams" <jowillia@vt.edu>
To: "John T. Williams" <jtwilliams@vt.edu>
Cc: "linux-c-programming" <linux-c-programming@vger.kernel.org>
Sent: Friday, May 30, 2003 11:07 AM
Subject: Password Encryption & Philosophy
> I had a problem, and I was wondering if anyone had a solution.
> I'm writing a client which gives the user the option to store their
> password, and I want to lend some security to the password being stored.
My
> problem is that no matter what algorithm I use to encrypt and decrypt the
> password (it can't be a one way hash, bc I have to be able to send it to
the
> server in its original form), anyone who has access to the source code and
> the encrypted password can get the original password back. Does anyone
have
> any suggestions on how to encrypt a password with an open source algorithm
> and yet lend more security stored information.
>
> Sincerly,
> John T. Williams
> jtwilliams@vt.edu
>
> -
> To unsubscribe from this list: send the line "unsubscribe
linux-c-programming" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
next prev parent reply other threads:[~2003-05-31 9:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-26 8:44 question on socket connection Ranga Reddy M - CTD ,Chennai.
2003-05-26 10:05 ` John T. Williams
2003-05-30 10:07 ` Password Encryption & Philosophy John T. Williams
2003-05-30 13:48 ` John Anthony Kazos Jr.
2003-05-31 9:05 ` Andrew [this message]
2003-06-01 21:14 ` ipaddress from hostname John T. Williams
2003-06-02 0:33 ` ronkhu
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='002801c32759$5c6c9b60$a885bc3e@alanmari' \
--to=inbox@andy.co.uk \
--cc=jowillia@vt.edu \
--cc=linux-c-programming@vger.kernel.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 NNTP newsgroup(s).