praxis23
Implementing GDPR right and security demands
Database leakage/SQL injection detection through poison records
A Linux Auditd Rule Set Mapped to MITRE's Attack Framework
Current trends and challenges in post-quantum cryptography [pdf]
Overview of governmental bans on encryption
Reducing Docker container image sizes
Learn cryptographic engineering by example
Migrating to OpenSSL 1.1.0 API
Fuzzing Ethereum Smart Contracts
Top security/cryptographic fails of 2017
Concepts behind all pricing models are fairly simple and don't require overly sophisticated math. Instead, they require sober look into 4 variables:
- Replacement cost: what would it cost to replace your service/product with something else?
- Market price: what others are charing, charge around their price.
- Cashflow/Net present value: if something you're producing has long-term economic impact, you may price not only based on actual value of your offering, but on long-term profit your offering will generate. And, in some cases in enterprise industries, this is the only way to reasonably justify your prices.
- Value-based pricing: this is fine adjustment mechanism for everything you've figured during previous three stages. Think who's target audience for your product, and if there's something which makes your product more valuable for them than the rest of the market - price it accordingly. Simple example - luxury DSLRs (whose sensors, firmware and lenses are just as good as professional ones, yet luxury casing and a good brand name makes them significantly more expensive).
(I'm not a salesman, I'm an engineer, yet I had to sit through decisionmaking sessions about pricing services in 2 different companies over last decade, and found them very amusing - if you get to the core, the ideas are very simple, they're just surrounded by plenty of bullshit bingo and lingo).
Auditable Macros in C Code
A walk through an F* proof
Explaining Zero Knowledge Protocols with Halloween Candy
Awesome crypto papers for engineers
Performing Padding Oracle Attack from Powershell
Quantum collision search: not overly scary
Building application back ends with end-to-end encryption
1. It helps you get discipline right, and care less about "productivity" and "motivation" - you just do stuff. 2. It teaches you that your reserves and powers are limited, and priorities are an hourly grind of making the right choices. 3. It teaches you to stay sharp all the time, no matter what your body tells you to feel.
Not that I've mastered any of these, but even small hints I've picked up really changed my life before/after spending 6 months in pre-field training and a year in field (I was officer-in-reserve before, but it teaches you knowledge, not skill).
So, yeah, the problem is political in a way that everyone is coming with their own agenda into it, which has little grounding in reality, yet affects decisions of many people substantially.