libsodium

I've spent an embarrasing number of hours trying to get Libsodium.js to work. See my fiddle demo (and code pasted below too). I keep getting Error: wrong secret key for the given ciphertext . What I would prefer is to replicate this PHP example of function simpleEncrypt($message, $key) into Libsodium.js. But as a starter, I'd be happy even getting the basic sample from the Libsodium.js repo to work. Any hints? Here is the code (also shown in the working fiddle): const _sodium = require("libsodium-wrappers"); const concatTypedArray = require("concat-typed-array"); (async () => { await _sodium

Trying to follow the examples here , but it gives me Fatal error: Uncaught Error: Call to undefined function sodium_randombytes_buf() On top of that, the key pairs seems to be generating weird strings like: kÿòjƒFDú{î—4]F◊î¸˜ßˆu…®_•A∞+ . Is that normal? Here's my code <?php // send $message = 'Hi, this is Alice'; $alice_to_bob_kp = sodium_crypto_box_keypair_from_secretkey_and_publickey( file_get_contents('./keys/sec-user-1_box_key.txt'), file_get_contents('./keys/pub-user-2_box_key.txt') ); $nonce = sodium_randombytes_buf(SODIUM_CRYPTO_BOX_NONCEBYTES); $ciphertext = sodium_crypto_box(

I am writing an app where users can communicate between devices with end to end encryption. For this I use the libsodium encryption library. The asymmetric encryption function, crypto_box(...) requires a nonce as one of the arguments. I am a bit confused about how to handle nonces. Does every message to one person need to be encrypted using different nonces? This does not seem right since I would have to store the used nonces on a server with public access where an attacker could just use one of the used nonces again. Is it enough that all messages sent from A to B have different nonces or can

I am porting some packages created for NodeJS to React Native using ReactNativify to rewrite Node API object dependencies to their browserify equivalents. One of them is crypto . In transformer.js (or .babelrc ) I have: // The following plugin will rewrite imports. Reimplementations of node // libraries such as `assert`, `buffer`, etc. will be picked up // automatically by the React Native packager. All other built-in node // libraries get rewritten to their browserify counterpart. [require('babel-plugin-rewrite-require'), { aliases: { crypto: 'crypto-browserify', // ... },