Am I the only person that wants and expects integrated password protection in a Perl script? Would you like to see it in the next version of Links as much as I would?

I understand the correct way to protect files is to CHMOD the directories, et cetera, et cetera, but how about us Windows cry babies? Why should we have to trouble our ISP's to password protect the Links directory; be forced to run FrontPage extensions and install child webs; or add kludgey code fixes, just to protect an excellent but vulnerable Links program?

I know this isn't rocket science. However, two constants in human existence are laziness and addiction to our pain. So, many of us just put off the implementation of password protection schemes and languish in torment, rather than do "the right thing" and fix the protection hole(s) in Links. Wouldn't it be much easier if GTI just added a little password protection code in the next version? This would at least offer some sort of quasi-password protection, like every other links program on the web has?

What do YOU think? Do you want to see Password Protection in the next links version... or is it just me?

------------------
Lenon.com Homepage
www.lenon.com
------------------
Lenon.com Links Page
See our "Snap Interfaced"
Gossamer Threads v.2.0
www.lenon.com/links/pages
------------------