libsignal-node
Security and privacy
end-to-end encryption library
SHOW HN2017
How HN took it
0 positive, 3 neutral or asking, 0 mixed, 4 critical, out of 7 comments about the project. Thread score -0.44.
Docs: 0 for, 2 againstExecution: 0 for, 2 against
The thread, comment by comment
Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.
positive neutral or mixed critical about another commenter or something else the maker
What HN said
What people liked
Ported directly from the JavaScript library, keeping interfaces and commit history
From 1 comment
It's ported directly from the javascript lib so most of the interfaces are exactly the same (async differences in some cases and a couple storage interface differences, see:…
tooker on HN
Emscripten builds of the crypto functions have been reliable and performant
From 1 comment
The C components are just a few emscripten compiled curve25519-donna and ed25519 functions for elliptic curve routines. It comes directly from the web library without any…
tooker on HN
Objections
No tests, so compatibility with libsignal is unverified
From 2 comments
One of the nice things about JS versions of stuff is being able to run it everywhere. With that being said, I'd be skeptical of using this since it doesn't appear to have any…
TheAceOfHearts on HNHow much is this based on the libsignal-protocol-JavaScript code? Where does it differ from it? Where are the tests to test protocol steps? I actually love seeing things like…
micaksica on HN
Written in JavaScript rather than TypeScript, lacking type safety
From 1 comment
What disturbs me about this port is that they did not use Typescript. I would have expected that they would use a strongly typesafe language in the ideal case.
sandGorgon on HN
Native C bindings can crash the process on bad input
From 1 comment
Many checks still need to be done in runtime. Bindings to C code can cause the program to exit if you pass incorrect input.
partycoder on HN
Crypto library is risky to adopt while new and under-documented
From 1 comment
How much is this based on the libsignal-protocol-JavaScript code? Where does it differ from it? Where are the tests to test protocol steps? I actually love seeing things like…
micaksica on HN
Requests
Add documentation
From 1 comment
How much is this based on the libsignal-protocol-JavaScript code? Where does it differ from it? Where are the tests to test protocol steps? I actually love seeing things like…
micaksica on HN
Port the tests
From 1 comment
It's ported directly from the javascript lib so most of the interfaces are exactly the same (async differences in some cases and a couple storage interface differences, see:…
tooker on HN
Questions
How closely is it based on libsignal-protocol-JavaScript and where does it differ?
From 1 comment
How much is this based on the libsignal-protocol-JavaScript code? Where does it differ from it? Where are the tests to test protocol steps? I actually love seeing things like…
micaksica on HN
Is it a true port or just bindings?
From 1 comment
So it is "bindings", but not a "port"?
qznc on HN
Alternatives named
libsignal-protocol-javascript (the original JavaScript library)
From 1 comment
How much is this based on the libsignal-protocol-JavaScript code? Where does it differ from it? Where are the tests to test protocol steps? I actually love seeing things like…
micaksica on HN