Aha. I see. When I tried to pack your string I noticed that perl thought that it was being given unicode data and treated it accordingly. Instead of plain pack "H*", $str, try do { use bytes; pack "H*", $str }. See bytes for more on forcing perl to not try to interpret it as unicode.

Oh further drat. when I wrote that I saw things like \323 and thought "aha! a value over 255, obviously unicode." Unfortunately for me, that was an octal number and this whole digression on unicode is entirely unrelated. So, show us the value produced by the encryption server and the value fetched from the database. As-is, there isn't anything that you're doing wrong.

In reply to Re^5: convert hexadecimal value to encrypted string by diotalevi
in thread convert hexadecimal value to encrypted string by linuxfan

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.