cossacklabs
Nuances of Replacing OpenSSL with Google's BoringSSL
Show HN: Acra, new database protection suite for PostgreSQL
Importing with ctypes in Python: preventing overflows
Advanced encryption for Redis and Postgres
Show HN: Advanced encryption in PostgreSQL
12 and 1 Ideas How to Enhance Backend Data Security
Why making Internet safe is everyone’s responsibility
Back end key management 101
Classic database security patterns you should know
Zero Knowledge Protocols without Magic
Introducing WebThemis: modern cryptography for Google Chrome web apps
Re:Zero Knowledge Authentication Protocol Secure Comparator
on Wednesday December 09, 2015 @12:06PM (#10704960)
... and a more formal whitepaper for cryptographic people:
https://cossacklabs.com/static/secure-comparator-paper-v1.pd...
Zero Knowledge Authentication Protocol Secure Comparator
Upgrading curve ed25519 implementation to meet extended security challenges
Re:You should avoid SSL for your applications
on Wednesday November 04, 2015 @05:25AM (#10505607)
Well, network is TCP/IP based last time I've checked, but yes, most people today tend to organize such communications over HTTP for simplicity (although it's not that good at all), I get your point.
Re:You should avoid SSL for your applications
on Thursday October 29, 2015 @04:44AM (#10469835)
This is exactly the point we're leading to - if you need vast heterogenous support everywhere, you're doomed to use TLS/SSL and you'd better cook it well, cause it has plenty of problems.
But, from our point of view, most non-web-developers (mobile? distributed applications? there are plenty), who now use SSL, but can afford themselves either avoid HTTP at all, or implement decent cryptographic stack on top of it, because they control both client and server, and don't need multitude of platforms to talk in the same way.
That's the point we're leading to in this article.