You guys seem like you know your onions...
Can I ask for a quick sanity check on an idea?
Background -
An ASP extranet site requires dynamic and secure content generated by a mod_perl package on a remote system called via an iFrame.
Logon credentials are passed from the ASP site as MD5 encrypted cookie values.
The mod_perl app looks at these against an internal list and then allows / disallows access to the relevant content.
I'm not convinced that this is safe from cookie poisoning (the values of some of the keys would be easy to guess). Also, I would like the mod_perl app to be flexible enough to react to any combination of values with which it is presented (i.e. for values that do not yet exist).
I am thinking that if the ASP system digitally signed the values in the cookie (using its private key) then the mod_perl app could be sure that they originated there and only there and act accordingly.
Is this a valid approach?
Many thanks in advance and apologies for the not-directly-perl-related nature of this post.
SM
-
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.
|