comment on

Authorization is the second step, before that you will need an authentication check to make sure that the one who logs in is indeed who (s)he says (s)he is (that is the usual login-id and password stuff).

It is a bit difficult to see how you can authenticate through e-mail (perhaps putting the log-in and password in the body of the e-mail? But that is not secure at all as anybody who intercepts the e-mail will know your log-in and password). Simply checking for the e-mail address of the sender is of course not enough as e-mail headers are far too easily spoofed. Anyone who has taken the Spam 101-course will know how to do it.

CountZero

"If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law

In reply to Re^3: What is wrong with variable? by CountZero
in thread What is wrong with variable? by w3b

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


"be consistent"
	PerlMonks