praxis23

9 ms·

1.
What do we really need to encrypt? Cheatsheet(cossacklabs.com)
7 points by praxis23 8y ago|0 comments
2.
Implementing GDPR right and security demands(cossacklabs.com)
1 points by praxis23 8y ago|0 comments
3.
Database leakage/SQL injection detection through poison records(cossacklabs.com)
2 points by praxis23 8y ago|0 comments
4.
A Linux Auditd Rule Set Mapped to MITRE's Attack Framework(github.com)
51 points by praxis23 8y ago|1 comments
5.
Current trends and challenges in post-quantum cryptography [pdf](math.auckland.ac.nz)
2 points by praxis23 8y ago|0 comments
6.
Overview of governmental bans on encryption(medium.com)
1 points by praxis23 8y ago|0 comments
7.
Reducing Docker container image sizes(cossacklabs.com)
3 points by praxis23 8y ago|0 comments
8.
Learn cryptographic engineering by example(github.com)
210 points by praxis23 8y ago|16 comments
9.
Migrating to OpenSSL 1.1.0 API(cossacklabs.com)
1 points by praxis23 8y ago|0 comments
10.
Fuzzing Ethereum Smart Contracts(blog.trailofbits.com)
3 points by praxis23 9y ago|0 comments
11.
Top security/cryptographic fails of 2017(medium.com)
7 points by praxis23 9y ago|0 comments
12.
by praxis23 9y ago
It's fairly easy to price against perceived worth of labor, but it isn't really helpful neither in competitive, nor in emerging markets to base pricing decisions solely on it. Concepts behind all pricing models are fairly simple a
13.
by praxis23 9y ago
I wonder how many times it's coming back before people will actually start to put some thought (or learning) into design of things that involves a lot of un-obvious considerations?
14.
Auditable Macros in C Code(cossacklabs.com)
55 points by praxis23 9y ago|12 comments
15.
A walk through an F* proof(gist.github.com)
2 points by praxis23 9y ago|0 comments
16.
Explaining Zero Knowledge Protocols with Halloween Candy(medium.com)
5 points by praxis23 9y ago|0 comments
17.
Awesome crypto papers for engineers(github.com)
12 points by praxis23 9y ago|0 comments
18.
Performing Padding Oracle Attack from Powershell(lowleveldesign.org)
1 points by praxis23 9y ago|0 comments
19.
Quantum collision search: not overly scary(blog.cr.yp.to)
1 points by praxis23 9y ago|0 comments
20.
Building application back ends with end-to-end encryption(medium.com)
2 points by praxis23 9y ago|0 comments
21.
by praxis23 9y ago
Anyone already posted "2 unit tests, 0 integration tests"? [1]. It's funny, because 4WS actually had security proofs, which considered all the pieces in isolation, but never in symbiosis. [1] https://gfycat.com&#x2
22.
by praxis23 9y ago
Serving in the army (and actually going to war, which is a nightmare, for a brief period): 1. It helps you get discipline right, and care less about "productivity" and "motivation" - you just do stuff. 2. It teaches you
23.
by praxis23 9y ago
Even though I adore the concept (remember the original posts by J.Spilman in 2012 and kept rolling it in my head for a while), this introduces new remote SPOF for authentication process, doesn't it?
24.
by praxis23 9y ago
Smaller userbase means less damage for data holder (the company), not the actual damaged party (person, whose password is leaked). It's not the type of attack implemented on the threat vector that matters - you remove one, you introduc
25.
by praxis23 9y ago
TOASSA is indeed a book every responsible software engineer has to read these days. Apart from finding bugs, this book is extremely helpful in understanding how bugs come to be, and hints on ways to avoid them.