3 ms·
Why is Protect a non-blocking call? That means that after I call Protect on some data, it's not actually protected yet.
by nemo1618 9y ago
Why is Protect a non-blocking call? That means that after I call Protect on some data, it's not actually protected yet.
- libeclipse 9y agoHey there! Thanks for this advice, I'll definitely consider this in the next release. Like I said in other parts of this thread, the project is in very early stages right now and, as I understand from reading a lot of the replies, I seem to have missed a lot. All of this stuff will be fixed soon.
- stouset 9y agoI would strongly encourage you to just wrap `libsodium`. The authors have thought about this problem a lot, and have done the hard work for you — there is a surprising amount being done behind the scenes to give the kinds of guarantees cryptographic keys warrant. If CGo isn't acceptable, at least use their implementation to guide the design your go-native version.