node.js - why do I get 'extra' characters when I decrypt a cookie from .NET using Nodejs? -


i have application running on nodejs. when receive cookie encrypted using .net framework can decrypt it: see this

i used solution provided stackoverflow question. result similar this

expected hmac: 88e332b9a27b8f6f8d805ae718c562c1c8b721ed
actual hmac: 6beaff25834e72357fd40e80e76458091224fae8
hex: 010112ea9a47b2f2ce08fe121e7d78b6f2ce0801085400650073007400550073006500720016540065007300740020007400650073007400730073006f006e002c00200072006f006c0066007a006f007200012f00ff1d892908d9c497bd804f5f22eab043ff6368702c

utf-8: ��g���}x�testusertest testsson, rolfzor/���ė��o_"��c�chp,

what don't understand encoding characters result of utf-8? causing unicode characters showup? buffer issue when trying decrypt message?

fwiw: thing being encrypted number, 123412341234.


Comments

Popular posts from this blog

ios - MKAnnotationView layer is not of expected type: MKLayer -

ZeroMQ on Windows, with Qt Creator -

unity3d - Unity SceneManager.LoadScene quits application -