Better info!

Ahhh... never was good at explaining how my stuff works. did you look in the example folder?

Data integrity with expiration for forms, links, cookies or other things.

Low security will stop url tampering and is nice to search engine ranking
if you do not use the expire, ip in encoding or an unique key for each user.

Remember if a method that prevents others from access to ones link encoding is used,
will heart that pages search engine ranking.

For some areas of your web portal when using Methods that prevent others from using
once links is applied (mainly for Admin and/or Member areas of the site)
can stop form hijacking and link hijacking witch for some web portals can give the
attacker control over Admin and Member accounts.

With the new action 4 and 5 one can have full control with when a cookie expires,
because the cookie expirations are stored in the users
browser and can be changed. the expiration encoding and a little extra perl code can be
used to replace the cookies old expiration method to one that will always work.
These two new actions are also good for securing data in hidden form field with or
without the expiration and other setting.

The Referer check 1 will check the Referers encoding witch was the last encoded QUERY_STRING,
if it matches the current QUERY_STRING, has a length of 1024 and if from the QUERY_STRING's domain.
Matching the Referer can match a Referer of any domain provided.
Using any of these Referer check can prevent users from spoofing there referer, Most web masters
Do not check the Referers because many people use referer spoofing and do not want to give it up.
So if you want to loose members or convince them not to spoof referers on your site, is up to you.

When one has mastered this module they will see the may possibilities it has to offer.
Secures Form: hijacking, url/data tampering and gives control for data to expire.
Could offer other securitys.

In reply to Re: SF_form_secure by SFLEX
in thread SF_form_secure by SFLEX

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.