🚀 go-pugleaf

In message <PM00042F7A91AB5706@sean-mackennas-computer.unknown.dom>, 
Sean MacKenna <me@isomewhere.co.uk> writes
>Is there an easy way to add a password to control entry to some of my pages?
>I would be grateful for any help.
>
You should find some samples with a quick look around 
www.hotscripts.com. I had a quick look the other day and there were 
certainly some JavaScript ones.  None of these are exactly secure but 
you have to be intent on finding a way in without a password.  Problem 
is some of them show that when by the reader using the "show source 
code" facility in the browser.

I have one version that uses a JavaScript action box to enter the 
password and that prevents people looking at the code right there - but 
there are still fairly simple easy if you are determined enough but it 
is better.  I can't remember where I found it but if you would like a 
copy of the files (very small) email me.  I'm sure you can find your way 
round the address - just take out the nospam and add in the missing 
stop.

There are others who occasionally respond in this group who know much 
more than I do about using a database to handle passwords but that can 
be overkill unless the security needs to be strong and you understand 
more about that sort of coding than I do.  A Google search of this group 
and demon.ip.support (I think) several months ago might lead you to a 
previous discussion.
-- 
Duncan K
Downtown Dalgety Bay

In message <sTairDFrnzOGFwGL@apbz24.dial.pipex.com>, Duncan Kennedy 
<obg@nospamotterson-bg.couk> wrote
>In message <PM00042F7A91AB5706@sean-mackennas-computer.unknown.dom>, 
>Sean MacKenna <me@isomewhere.co.uk> writes
>>Is there an easy way to add a password to control entry to some of my pages?
>>I would be grateful for any help.
>>
[snip good stuff]

Note that Demon homepages do not permit you to run things on their 
servers (the more expensive business pages do), so anything you do has 
to be written by you in the coding for your page and has to be run by 
the browser of the reader. You need to consider what will happen if the 
reader doesn't run the script, has such things disabled, etc.
-- 
Andy
For Austria & its philately, Lupus, & much else visit
<URL:http://www.kitzbuhel.demon.co.uk/>

In article "Adding password" in <demon.homepages.authoring>, on Wed, 2
May 2007 Sean MacKenna <me@isomewhere.co.uk> writes

>Is there an easy way to add a password to control entry to some of my pages?
>I would be grateful for any help.

Depending on what's on your site, an easy way to password protect it
would be to put all your secret content into Word documents, PDFs or ZIP
files and to password-protect those files.  
-- 
David Gibson
Spam-cloaked message: The Reply-to: address *is* valid.

In article "Adding password" in <demon.homepages.authoring>, on Sat, 5
May 2007 Andy <andy@kitzbuhel.demon.co.uk> writes

>Note that Demon homepages do not permit you to run things on their 
>servers (the more expensive business pages do), so anything you do has 
>to be written by you in the coding for your page and has to be run by 
>the browser of the reader. You need to consider what will happen if the 
>reader doesn't run the script, has such things disabled, etc.

I have written a JavaScript password routine that is sufficiently arcane
that it is immune to casual snooping; and it is fail-safe if JavaScript
is not running.  

Obviously it is not 100% secure because the determined snooper can read
the JavaScript.  But it has been designed to be immune to search-engine
and casual human snooping for the password or the secret page.

The demo is at http://caves.org.uk/js/demo/  but please be warned:
currently it does not work reliably in Internet Explorer if your
security settings are higher than "medium". 

This is because if you have your security level set too high, IE blocks
the 'popup' which is the script window. For some reason, my script bombs
out at that point and takes you directly to the spoofed 401 message, so
you dont see the password box at all, and you cannot get past the '401'
page :-(

So... either lower your IE security settings or go in via Firefox which
seems to work OK (for me, anyway; with my security settings).

-- 
David Gibson
Spam-cloaked message: The Reply-to: address *is* valid.

In article "Adding password" in <demon.homepages.authoring>, on Sat, 5
May 2007 David Gibson <david@[127.0.0.1]> writes

>The demo is at http://caves.org.uk/js/demo/  but please be warned:
>currently it does not work reliably in Internet Explorer if your
>security settings are higher than "medium". 
>
>This is because if you have your security level set too high, IE blocks
>the 'popup' which is the script window. For some reason, my script bombs
>out at that point

OK; worked out why.  Because IE wont execute the pop-up script window
its as if the user pressed "cancel" and the code is designed to take you
to the 401 page if you click on cancel.

Also, there is an annoying behaviour of the history list to contend
with. You can get stuck in a loop. Pressing cancel ought to execute
history.back() to avoid this, I guess.

Well, plenty there for you to tinker around with, anyway.

There is another version of the code at http://caves.org.uk/js/demo2/
Its exactly the same, but without the comments in the JS.  This might
make it clearer, or more of a challenge to work out how to hack;
depending on your viewpoint :-)

-- 
David Gibson
Spam-cloaked message: The Reply-to: address *is* valid.

In message <NjAV+7C98OPGFw5p@mcrosolv.demon.co.uk>, David Gibson 
<david@[127.0.0.1]> writes
>In article "Adding password" in <demon.homepages.authoring>, on Sat, 5
>May 2007 David Gibson <david@[127.0.0.1]> writes
>
>>The demo is at http://caves.org.uk/js/demo/  but please be warned:
>>currently it does not work reliably in Internet Explorer if your
>>security settings are higher than "medium".
>>
>>This is because if you have your security level set too high, IE blocks
>>the 'popup' which is the script window. For some reason, my script bombs
>>out at that point
>
>OK; worked out why.  Because IE wont execute the pop-up script window
>its as if the user pressed "cancel" and the code is designed to take you
>to the 401 page if you click on cancel.
>
>Also, there is an annoying behaviour of the history list to contend
>with. You can get stuck in a loop. Pressing cancel ought to execute
>history.back() to avoid this, I guess.
>
>Well, plenty there for you to tinker around with, anyway.
>
>There is another version of the code at http://caves.org.uk/js/demo2/
>Its exactly the same, but without the comments in the JS.  This might
>make it clearer, or more of a challenge to work out how to hack;
>depending on your viewpoint :-)
>
Your version uses the same *idea as the one I have  but yours is rather 
cleaner and neater.

-- 
Duncan K
Downtown Dalgety Bay