Feature request: RSAVerify handle CRLF line endings in the 'Message' field

**Is your feature request related to a problem? Please describe.**
When attempting to verify an email DKIM signature, the message to be verified typically contains **CRLF** line endings. However, when uploaded to the "Message" textarea, the line endings are replaced with **LF**, causing a different hash to be computed, which naturally always results in 'Verification failure'.
I'm guessing this is probably an html textarea issue, rather than a bug in the project.

**Describe the solution you'd like**
Proposed solution could be to add additional toggle button "Message Input", where a user can choose how a Message should be interpreted/decoded. ie. (Hex, UTF8, Latin1, Base64).

**Alternate solution**
A textarea allowing escaped characters. Example: 'Hello\r\n'

**Additional context**

Start by reproducing the CRLF-to-LF conversion in the RSAVerify operation's Message textarea with a DKIM-signed message. Inspect how the Message input is interpreted and compare the proposed decoding toggle with escaped-character input; done means a CRLF message can be verified without changing its hash.

Written by the indexing model from the issue text.