I note that the bytes which the C# is taking the SHA1 of are little-endian UTF-16:

  // s = '1234'
  ....
  byte[] bytes = Encoding.Unicode.GetBytes(s);
  // bytes = 49, 0, 50, 0, 51, 0, 52, 0

[download]
so you're probably best off:
  my $data = encode("UTF-16LE", .....);

[download]
On my x86 (little-endian) machine
  my $data = encode("UTF-16", '1234');

[download]
gives $data bytes:
  0xFE 0xFF 0x00 0x31 0x00 0x32 0x00 0x33 0x00 0x34

[download]
which is big-endian complete with BOM. Whereas:
  my $data = encode("UTF-16LE", '1234');

[download]
gives $data bytes:
  0x31 0x00 0x32 0x00 0x33 0x00 0x34 0x00

[download]
which is little-endian sans BOM; which appears to be what's required.

In reply to Re^3: Rewriting a C# Encryption Function by gone2015
in thread Rewriting a C# Encryption Function by bkiahg

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.