Another option: convert the data to a JSON string base64-encoded JSON string, then sign the string.
use JSON::XS;
use Digest::MD5 'md5_hex';
use MIME::Base64;
my $signing_key = '//Sw0rdFiSh//';
my $data = {
first_name => 'Will',
last_name => 'Smith',
age => 39,
};
my $json_string = encode_json( $data );
my $signature = md5_hex( $signing_key . $json_string );
my $base64_encoded = encode_base64( $json_string, '' );
# Send the encoded data and the signature in the HTML as hidden fields
print <<"HTML";
<input type="hidden" name="_signature" value="@{[ $signature ]}" />
<input type="hidden" name="_data" value="@{[ $base64_encoded ]}" />
HTML
Later, when processing the stored data on another step:
my $json_string = decode_base64( $q->param('_data') );
my $new_signature = md5_hex( $signing_key . $json_string );
unless( $new_signature eq $q->param('_signature') )
{
die "The data has been tampered with";
}# end unless()
-
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.
|