Originally posted by: joshsquall
Make it a virtual directory in IIS and disallow annoymous access in the Directory Security section of it's Properties. You can then create an account specifically for that purpose and have people login using it.
Originally posted by: vrbaba
Originally posted by: joshsquall
Make it a virtual directory in IIS and disallow annoymous access in the Directory Security section of it's Properties. You can then create an account specifically for that purpose and have people login using it.
but that always creates a windows logon account also, right? (which I dont want) well, as long as i can protect remote desktop access to that account, i think i can deal with it
Originally posted by: LoKe
Depends on how secure you want it. 🙂
if ($username == 'omg' && $password == 'hai') {
// display page }
else {
echo "Go away, nub!";}
Originally posted by: vrbaba
Originally posted by: LoKe
Depends on how secure you want it. 🙂
if ($username == 'omg' && $password == 'hai') {
// display page }
else {
echo "Go away, nub!";}
haha...
whts the point when the script is publicly viewable. i think "secure" defines that
Originally posted by: KB
You can use windows login passwords in IIS security (NTLM Windows Authentication or Basic Digest) and just deny the user account "interactive login" rights. This would prevent them from logging into remote desktop.
What is the dictionary in? If it is ASP.Net then you can use ASP.net builtin security.