407 karma · joined August 20, 2014
Too bad you won't be able to use it to secure your open-source projects. If you try it'll throw up a prompt telling you to use some initiative you can't use or afford while the provider collects the findings. What a racket.
Now Sweden is stuck in a terrible situation where we're forced to quickly sell our excess energy to Google/Microsoft/Facebook before the EU will force the use of the bottleneck fees to build more cables to Germany.
Extract those keys and your drivers can ignore all annoying work-time rules and you can just patch the files if you are audited.
This seems to mostly hold true to developers also, GitHub manages to survive just fine after all.
Apparently Firefox has "Https First" also but requires the pref dom.security.https_first to be set.
"HTTPS-Only Mode" is obviously best if you can do that.
- krya på dig katt (cat) - fuck you cat
Björn is also bear in swedish.
The AWS egress savings from this setup must be immense.
Looking at Github and uses of SerializationUtils.deserialize this is going to be painful.
In this case it seems like the attackers targeted an SDK. Subresource integrity would have helped here.
https://developer.mozilla.org/en-US/docs/Web/Security/Subres...
And for systematic non-compliance “structural or behavioural remedies”.
Wouldn't be surprised if they start splitting into separate legal entities soon to get out of the pickup price matching restrictions.
A game i run was recently hit with a 102 Ggbps CLDAP reflection attack. We were down for a while until our ISPs DDoS protection detected it after that we were mostly unaffected. If the attack is difficult to separate from legitimate traffic you'll still suffer though.
"The affected Megapacks failed safely despite total loss."
[1] https://cfpa-e.eu/container-puts-out-inextinguishable-fires-...