G
Guest
Is there a way to create a website where one of the web pages that it points
to requires a password to access?
to requires a password to access?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
R
Ronx
Password Protect Part of a Web: (Requires FrontPage extensions on
server, and host must support subwebs with unique permissions)
http://support.microsoft.com/default.aspx?scid=kb;en-us;301554 (FP2000)
http://support.microsoft.com/default.aspx?scid=kb;en-us;825451 (FP2003)
Protect individual pages: (Requires Windows Server with support for ASP
and Access database)
http://support.microsoft.com/default.aspx?scid=kb;en-us;825498
The same database technique can be used with PHP and mySQL, or any other
combination of server-side script and database technologies your server
supports.
server, and host must support subwebs with unique permissions)
http://support.microsoft.com/default.aspx?scid=kb;en-us;301554 (FP2000)
http://support.microsoft.com/default.aspx?scid=kb;en-us;825451 (FP2003)
Protect individual pages: (Requires Windows Server with support for ASP
and Access database)
http://support.microsoft.com/default.aspx?scid=kb;en-us;825498
The same database technique can be used with PHP and mySQL, or any other
combination of server-side script and database technologies your server
supports.
D
David Berry
For another sample of using a database and ASP See
http://www.kamath.com/tutorials/tut003_auth.asp
http://www.kamath.com/tutorials/tut003_auth.asp
P
Paul C
Hi
David Seems easy enough but I have a concern about SQL injection, is this
code safe from these sort of attacks?
Paul M
David Seems easy enough but I have a concern about SQL injection, is this
code safe from these sort of attacks?
Paul M
?
.._..
Well, considering the code uses a flat MS Access Database without using SQL
at all, I'd say you are pretty safe from SQL injection attacks.
at all, I'd say you are pretty safe from SQL injection attacks.
D
David Berry
SQL Injection attacks have nothing to do with SQL Server. It has to do with
being able to alter the SQL Statements on a site so Access is just as
vulnerable. See http://en.wikipedia.org/wiki/SQL_injection and
http://www.sitepoint.com/article/sql-injection-attacks-safe and
http://msdn.microsoft.com/msdnmag/issues/04/09/sqlinjection/default.aspx for
some articles. (there are many more out there. Just do a search for SQL
Injection Attacks)
being able to alter the SQL Statements on a site so Access is just as
vulnerable. See http://en.wikipedia.org/wiki/SQL_injection and
http://www.sitepoint.com/article/sql-injection-attacks-safe and
http://msdn.microsoft.com/msdnmag/issues/04/09/sqlinjection/default.aspx for
some articles. (there are many more out there. Just do a search for SQL
Injection Attacks)
J
Jon Spivey
Or put another way any self-respecting script kiddy could log straight into
a site "protected" by the Kamath script ;-) To be fair the article was
written a long time ago but it's not something that should be recommended on
a newsgroup.
Cheers,
Jon
a site "protected" by the Kamath script ;-) To be fair the article was
written a long time ago but it's not something that should be recommended on
a newsgroup.
Cheers,
Jon
D
David Berry
It's only meant to be an example. If you're going to do ASP coding then I'd
start with a good book.
start with a good book.