Implement cryptoSignEd25519SkToSeed (crypto_sign_ed25519_sk_to_seed) about libsodium_dart_bindings HOT 8 CLOSED

Thanks for the quick reply @Skycoder42 , This resolved my issue

from libsodium_dart_bindings.

Thanks for your help @Skycoder42 ,
It worked for sodium sumo too after replacing package:sodium/sodium.dart with package:sodium/sodium_sumo.dart

from libsodium_dart_bindings.

Hi. These methods are indeed implemented in the packages. However, the are part of the "Sumo" variant, as those APIs are not available in the standard sodium.js bindings. However, when working with the dart-vm, they are always available. Here are some docs you can read more about that:

• Overview of the provided APIs and differences between standard and sumo: https://github.com/Skycoder42/libsodium_dart_bindings/tree/main/packages/sodium#api-status
• DartDoc of the SignSumo class: https://pub.dev/documentation/sodium/latest/sodium_sumo/SignSumo-class.html
• Usage example on how to load the sumo variant of the library, to get access to the APIs: https://github.com/Skycoder42/libsodium_dart_bindings/tree/main/packages/sodium_libs#usage

Currently, the dart APIs only allow you to access the default implementations/algorithms of the different cryptographic concepts. However, the naming closely follows the official names. In your example, after loading the sumo variant of sodium, you can access the crypto_sign_ed25519_sk_to_seed method as follows:

final sodium = await SodiumSumoInit.init();
// ...
final seed = sodium.crypto.sign.skToSeed(secureKey)

The ed25519 part is omitted.

from libsodium_dart_bindings.

@Skycoder42 When i try to init SodiumSumo on mac m1, i am getting the below errors.

LateInitializationError: Field '_instance@154288322' has not been initialized.
package:sodium_libs/src/sodium_platform.dart                          SodiumPlatform._instance
sodium_platform.dart:1
SodiumPlatform.instance
sodium_platform.dart:23
SodiumSumoInit.init.<fn>
sodium_sumo_init.dart:38
BasicLock.synchronized
basic_lock.dart:31
SodiumSumoInit.init
sodium_sumo_init.dart:33
SodiumUtilsImpl.init
sodium_utils_io.dart:10
SodiumUtils.init
sodium_utils.dart:13 

This is the code i am trying to run

await SodiumSumoInit.init()

Let me know if any other details you need for the issues

from libsodium_dart_bindings.

This looks like you did not initialize the widget bindings. Make sure to call WidgetsFlutterBinding.ensureInitialized(); when using the library before flutter has rendered the first frame

from libsodium_dart_bindings.

I am calling it from one of the test cases and it's dart project.
Also tried calling it with WidgetsFlutterBinding.ensureInitialized(); still getting the same error

  setUpAll(() async {
     sodium = await SodiumSumoInit.init();
  });

from libsodium_dart_bindings.

Ah, I see. That is expected behavior - the library does not automatically load the native libraries in unit tests, only in integration tests. This is dictated by flutter and nothing I have control over. You should mock it in your tests, using for example mocktail.

If you do not want to mock it for whatever reason, you can import sodium/sodium.dart instead and load the library manually for your test cases. On macOS, you need install libsodium from homebrew and then reference the distributed dylib. See https://github.com/Skycoder42/libsodium_dart_bindings/tree/main/packages/sodium#vm---loading-the-dynamic-library

from libsodium_dart_bindings.

Ok got it, This seems to work, now the issue is the below code give me sodium instance how can i get SodiumSumo, to use the crypto_sign_ed25519_sk_to_seed, i cannot find the same init2 function in SodiumSumoInit

await SodiumInit.init2(() => DynamicLibrary.open("/usr/local/lib/libsodium.dylib"))

from libsodium_dart_bindings.