tweetnacl | Conservative , misuse-resistant crypto in Erlang

The example code was not quite clear what the key actually is and where you get it. You need the "repository public key" that you get from the /repos/{owner}/{repo}/actions/secrets/public-key endpoint.

Use the repository public key together with the value from your new secret:

tweetnacl-java is a port of tweetnacl-js. It is therefore to be expected that both provide the same functionality. At least for the posted method this is the case, which can be implemented on the Java side with TweetNaclFast as follows:

The problem with your current code is that nacl.util.encodeBase64() takes in either a string, Array, or Uint8Array. Since your input isn't an Array or Uint8Array, it assumes you want to pass it in as a string.

The solution, of course, is to encode it into a Uint8Array first, then encode the Uint8Array into base64. When you decode, first decode the base64 into a Uint8Array, then convert the Uint8Array back into your Float32Array. This can be done using JavaScript ArrayBuffers.

encrypted returned by SecretBox.encrypt() in the PyNaCl code is an EncryptedMessage object (a bytes subclass) that holds the concatenated (24 bytes) nonce and ciphertext. Note that EncryptedMessage also has the properties nonce and ciphertext.

Since the TweetNaCl code uses the concatenated (Base64 encoded) data, these data must first be separated (after Base64 decoding) and nonce and ciphertext must be processed separately in nacl.secretbox.open(). Please note that TweetNaCl uses TypedArrays. For the conversion to or from Utf8 or Base64 the functions from tweetnacl-util can be used:

That being said, NaCl signing keys are 64 bytes, not 32. Hence the error you get.

In the base58KeyPairGenerator function, the secret key must be the output of nacl.sign.keyPair.fromSeed(seed).secretKey (or .privateKey or whatever it's called), not just the seed.

I figured it out (mostly). Due to some magic that I haven't yet sorted out, I got a reference to npm inserted into my packages.json file.

Here's what I think happened: When I ran yarn list it informed me that a newer version of yarn was available. After considerable struggling and Googling, I figured out that I could upgrade yarn and npm to the latest version via:

Just like the warning said

DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.

To avoid the depreciation warning. You need to find out the new Buffer() methods in your codes and replace them with a new one. Such as in the extend-node.js file(NodeTaskApp-master\node_modules\iconv-lite\lib), Line 13:

he.js library was conflicting with the TweetNaCl library. Removing it and it started to work like it should.

I had the same issue today and indeed not encouraging to have warnings on a fresh new project. I just add babel core manually yarn add babel-core@^6.0.0and did not had pbs to run the new app.