uint8arrays | Utility methods for dealing with Uint8Arrays

I am using a secure embedded chip (ATECC508) to generate an ECDSA message/signature combination using the secp256r1 curve.

The information from the chip outputs in Uint8Arrays: message[32], signature[64], and publickey[64]; The public key is in raw byte format, giving both X/Y coordinates in a 64 byte array, without the 0x04 padding on the front.

The public key will only successfully import into WebCrypto as long as I pad the 64 byte array with 0x04 on the front.

However, when I attempt to verify the message and signature, it always fails.

I created a simulator script to help debug. It uses WebCrypto to generate the message, signature, and public key instead of the crypto chip. The simulator generates a 32 byte Uint8array message array, and signs the message returning a 64byte Uint8array for its signature. The public key that WebCrypto generates is also verified to have the 0x04 padding in the front, before the 64bytes representing the X/Y coordinates of the curve. This means I believe that the information generated by the simulator should be in the exact same format as what the chip provides.

Any message, signature and public key which is generated from WebCrypto can be successfully verified...but I cant authenticate the information from the chip...it is always unsuccessful.

I have no reason to suspect the values from the chip are wrong, and I have generated many messages/signatures from the chip...none of them work. I have also tried a second chip with the same result.

Output example from chip (does not verify):

UPDATED CODE

I'm using this code to claim the use of the serial-2-USB device. It shows up and I can query the info about it, ie. "connected to USB2.0-Serial VID: 6790 PID: 29987" (CH34x from Qinheng). To be clear, I use the winUSB driver (downloaded with zadig-2.5.exe, Windows 10) and have uninstalled the original drivers.

I get the received data as dataview but when I do the decode it comes out gibberish. And I see that the array length pretty much corresponds to what I know my ESP8266 is posting over the serial port.

Example of decoded data: �(#���D"D�T�b�!A#7mP�R�N����#�m93aw9 ½�d-K��b��BF+3ѡ��kag1�R�#��#!!r����g�!d��a��谛oa��399�}��1D�#��'99�����9�����'99���'99����@@譛

I get the data as Uint8Arrays but even if I try to make my own parser the same gibberish is the end result. Do I need to care about USB stuff as in start bits, ack bits etc. etc.? All the example code out there just do a text decoder and that's it.

serial.js + index.html

I have two Uint8Arrays of length 32 bytes each and I want to merge them to one Uint8Array of length 64.

So my question is:

Is there a way to merge two TypedArrays to a new TypedArray of the same type in AssemblyScript.

I guess I'm looking for the equivalent of the TypedArray.set() method in Javascript:

I'm using the FileReader api to load the contents of a file input into the browser's memory. This jsfiddle includes a working example: https://jsfiddle.net/qyh1s60d/

I turn the result into a Uint8Array and display it in a div:

I'm trying to send ArrayBuffer using WebRTC and simple-peer package. And I got these issues:

• Another browser receives several events with Uint8Arrays which are part of the original ArrayBuffer. Length of each Uint8Array is not greater than 262528. It happens when I send large ArrayBuffer from chrome to chrome.
• I get TypeError: The expression cannot be converted to return the specified type. error on sender browser when I send large ArrayBuffer from firefox to chrome.

But everything is fine when:

• ArrayBuffer length is small.
• when I send data from chrome to firefox.

I use peer.send(data) and peer.on('data', callback) functions from simple-peer and code is really simple so I have no idea what's going wrong.

I'm working on a personal project that involves retrieving audio from YouTube, manipulating the audio, and streaming the result to the browser. So far I have the first and last steps down, but the middle is proving a challenge.

Thanks to the youtube-audio-stream package, getting the audio was easy. I wanted to manipulate the raw audio samples, so I followed their README example and piped the stream into a Decoder from the lame package.

I threw together a couple stream transforms... one to merge incoming chunks together until a size threshold was met, and the other one to actually do something with those chunks. At the end of the pipeline, I added a wav writer (which adds a WAV header so the browser isn't confused about the raw data coming in).

This actually results in normal audio output if my audio transform just passes along the chunks without any modification. So I know that the pipeline itself isn't broken. But for some reason, performing the following operation results in garbled noise:

I'm using in-browser Javascript, not NodeJS. I have two Uint8Arrays ...