erm... mod_auth , don't recall mentioning it.
Second, why write a daemon if you already have them: ftp, telnet, rlogin, etc... .
What can I say but ,why write a cgi with authentication when there are daemons that support auth to /etc/shadow like rlogin... oh that's right this is a web application. My gist was that whilst your cgi gets called on demand by apache, you can have an entirely different and non-cgi accessible script that runs as root , hence has carte-blanche over things like getpwbyname that are simply unavailable to for instance - the apache user.
I do not for a minute suggest that you don't know what you are doing. I am pleased your code is quite secure and well tainted.
Is there less harm in finding out passwords of Mysql, htpasswd etc, than there is of system accounts?
Obviously none are desirable, but owning a system account gives rise to far more possibilities for harming that particular system IMHO.
I can't believe it's not psellchecked
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.