hojothum

3 ms·

1. 1.▲
   by hojothum 8y ago

   Admittedly, most of our focus (on the crypto end) has been on simplifying the key provisioning/management process, establishing secure sockets, and signing and verifying data. Our protocol does allow for storing a source ID and additi
2. 2.▲
   by hojothum 8y ago

   Sorry, I made a bad joke above. I'm guessing there are almost certainly side-channel attacks (discovered or not) in most crypto libraries. How easily they're exploited is another topic. We don't believe we need to build more
3. 3.▲
   by hojothum 8y ago

   This is a great point. Thank you for pressing us on this and being willing to give us some feedback. We'll get some meaningful architecture diagrams in the docs asap.
4. 4.▲
   by hojothum 8y ago

   Absolutely, we wrote our own post-quantum crypto engine that has no side-channel attacks and has little to no performance overhead... Just kidding! We do not write any of our own crypto. We use common open source libraries like libsodium,
5. 5.▲
   by hojothum 8y ago

   I was literally working on this last week! Email me at eric@medcrypt.co and I’ll send you a draft to get your feedback. We definitely need some simple, high-level figures show how the libraries interact with the PKI nodes as well as local l