metalnem / noise Goto Github PK

When the message transport is over UDP and packet loss does happen,
There is no option to set the CipherState.SetNonce forward,
because every class is markt as internal

In order to facilitate secure memory solutions, KeyPair:

• should not copy a given private key into a byte array to make it suitable for KeyPair storage (i.e. in factory methods ala Curve25519.GenerateKeyPair
• should not use managed buffer.Clear() to zero out memory on disposal, rather deferring to something like libsodium_free

This is a pre-requisite for enabling secure memory scenarios in this library, and could work for PSKs in the Protocol API methods.

Hey! Someone help please with an example with encryption using the Noise_XX_25519_AESGCM_SHA256 algorithm.

Having Noise.NET support Noise_XK_secp256k1_ChaChaPoly_SHA256 (the Lightning variant of Noise) would be very useful for developers looking to build Lightning Network related projects in C# (or other .NET languages).

See BOLT #8: Encrypted and Authenticated Transport for details.

As far as I know there are no Noise protocol .NET frameworks with support for Noise_XK_secp256k1_ChaChaPoly_SHA256.

I like to use/test noise in a mobile device management solution. Devices can register but need to be (manually) approved before they are allowed to "join". I think adding a pre-shared key inside of the device app is pointless since attackers could just decompile the app. Can I use noise without a pre-shared key or should I use it anyway?