in reply to Re: HTACCES & Cookies
in thread htaccess and cookies
Using CGI to authenticate users is no less secure than using basic HTTP authentication, credentials are passed as plain text in both cases. You can allow your users to login via an SSL connection if you want it more secure.
Your best bet is to create a cookie that contains certain information (IP address, username, time, expiry, for example) and an MD5 digest of that information and send that back to the client after a successful login. Each subsequent request just makes sure the cookie hasn't been tampered with by checking the data in the cookie against the MD5 hash, you need not check the username against the password each time. This has the added benefit that you're not sending a username and password on each request. For a great explanation of all things authentication/authorization, have a look at the Eagle book chapter 6, it's mod_perl specific but explains the concepts very well.
Steve.
Your best bet is to create a cookie that contains certain information (IP address, username, time, expiry, for example) and an MD5 digest of that information and send that back to the client after a successful login. Each subsequent request just makes sure the cookie hasn't been tampered with by checking the data in the cookie against the MD5 hash, you need not check the username against the password each time. This has the added benefit that you're not sending a username and password on each request. For a great explanation of all things authentication/authorization, have a look at the Eagle book chapter 6, it's mod_perl specific but explains the concepts very well.
Steve.
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: Re: HTACCES & Cookies
by bronto (Priest) on Jun 26, 2002 at 11:59 UTC | |
by kidd (Curate) on Jun 26, 2002 at 14:19 UTC | |
by stevenc (Novice) on Jun 26, 2002 at 14:30 UTC | |
by stevenc (Novice) on Jun 26, 2002 at 13:35 UTC |
In Section
Seekers of Perl Wisdom