If the app only runs via SSL, then what is the purpose of further encrypting things? Encryption is used when you want to prevent certain parties from reading messages. So who are you trying to keep from seeing the request data? An eavesdropper on the network? The SSL layer already prevents this. The client? They already know the request data, since they requested it. The server? It gets to decrypt it anyway to process the request.

The only other thing I can think of is that you're worried about cache files on the client's computer revealing the request data. But presumably (correct me if I'm wrong), the responses from the server already include ample information related to the request (i.e, if I request "/home/user/books", the response will be a nice page with a big header that says "/home/user/books").

Having two seemingly identical layers of encryption sounds pretty redundant to me. Especially when one is at a lower level in the protocol stack, standardized, and well-studied by cryptographers (I have no idea what encryption you are proposing to use on top of the SSL). I don't think this is a case of having two different security mechanisms (suspenders and a belt, using Old_Gray_Bear's terminology) -- it's like using another little tiny belt to hold the buckle onto your first belt! ;)

I'm sorry for the long story- I can't figure out how to shorten it.
Shorten it by using fewer words, not by using <small> tags, though I didn't think it was very long to begin with. ;) I could barely read the stuff in the smaller font on my browser.

blokhead

In reply to Re: In a web app, is using ssl, encrypting request data, and validating request data after decryption overkill? by blokhead
in thread In a web app, is using ssl, encrypting request data, and validating request data after decryption overkill? by leocharre

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.