I think you're right that losing access to Github is a serious problem. I'm worried that an attack like this could be used in conjunction with some zero-day. Imagine a bunch of distributed teams trying to deploy a fix…
There's a very strong argument to be made that regulation is the only way to improve this situation. A negative externality like this is unlikely to correct itself. Cheap manufacturers will continue to save money by…
I found a really really stale name server that didn't respect TTLs.
I can understand the instinct to move, but I think the answer is to split your eggs among many baskets, not just pick a sturdier basket. I don't think the Dyn team is necessarily bad, it was an enormous assault.
I'm sure a lot of people were unscathed by this event, but it appears to be more of a warm-up than the main event. I think it demonstrates the likelihood of further attacks and the possibility that those could have…
Good point! We are working through the details of those sorts of use cases, and are thinking of ways to mitigate the risks posed. A lot depends on the characteristics of your particular background tasks, but here are a…
I think you're right that losing access to Github is a serious problem. I'm worried that an attack like this could be used in conjunction with some zero-day. Imagine a bunch of distributed teams trying to deploy a fix…
There's a very strong argument to be made that regulation is the only way to improve this situation. A negative externality like this is unlikely to correct itself. Cheap manufacturers will continue to save money by…
I found a really really stale name server that didn't respect TTLs.
I can understand the instinct to move, but I think the answer is to split your eggs among many baskets, not just pick a sturdier basket. I don't think the Dyn team is necessarily bad, it was an enormous assault.
I'm sure a lot of people were unscathed by this event, but it appears to be more of a warm-up than the main event. I think it demonstrates the likelihood of further attacks and the possibility that those could have…
Good point! We are working through the details of those sorts of use cases, and are thinking of ways to mitigate the risks posed. A lot depends on the characteristics of your particular background tasks, but here are a…