Would be great thing to learn when I'll be trying Rust, I guess.
Mio - "lightweight I/O library for Rust". But this is a cryptographic part that "is not going to be used".
#SIGNAL MESSENGER ARCHITECTURE CODE#
Poksho - "This is some incomplete code used for testing". Sgx_common - I have no slightest idea what it can be, please tell me.īOLT - "BOLT is the binary optimiser used for SVR which is backed by sgx and sores our usernames and profiles protected with pins", as Leptopoda statesĬurve25519-dalek ( a repo elsewhere) - related security audit, related note Yay, signal uses the best of two worlds, both protocol buffers and JSON. Seems to be a derivative of BoringSSL, again, correct me if I am wrong here Ring - a cryptography library, README insists on it being provided as-is. Serde_json - a JSON serializer and deserializer written on Rust. Rust_openssl - not on signalapp repo, correct me if I am wrong here. Also, how does snow connect to Java server, anyway? Is it a part of a microservice? Snow - an implementation of Trevor Perrin's Noise Protocol on Rust, a bunch of protocols, having a label " Warning This library has not received any formal audit". Other parts mentioned by Leptopoda (yes, again, lol): Storage service probably controls files and images, 13 - mentioned by CerberusĬontact discovery service, - mentioned by Cerberus Zero knowledge proofs, - not sure what it does, mentioned by Leptopoda and Cerberus Secure value recovery, - side repo with new features, not sure what it does, mentioned by Leptopoda
#SIGNAL MESSENGER ARCHITECTURE SOFTWARE#
I don't see the license shift to proprietary software on GitHub.
Again, most of the stuff discussed are parts of the server kept separately in one GitHub account:, which is much less dramatic than "Signal server becoming proprietary". UPD: now that I think about it, I can start the list. This comment by Leptopoda seems to be most productive. Those repos are linked by one GitHub account, as far as I see that ( signalapp).ĭevelopment process takes time and this is an open source product, some delays are to be expected. Firstly, it's very good the community is active and is monitoring the development.If we had links to server dev repos grouped somewhere on the wiki, so it's easy to browse known parts of the server code, that'd be nice.
0 kommentar(er)
