4,405 karma · joined October 15, 2013
Most recent comment:
> We're working hard on it, but will probably not land this in production before the end of February. Still, we are very much aware of the upcoming deadline and committed to meeting it. Thanks for the enthusiasm everyone! :-)
https://excel.uservoice.com/forums/304921/suggestions/105490...
I don't have that problem. Maybe if I wore skinny jeans. Unlock from pocket is the way I usually do it.
That does nothing for deployed sites that aren't actively developed? Browser devs have decided those sites are worth not breaking.
To me this sounds like a firewall/vpn moved into the application layer.
That's pretty much the best case scenario. A lot of chipmakers (Conexant, Jmicron, Intel in many cases) don't allow you to download drivers directly from them. So you are stuck with whatever the OEM provides. In some cases I've found that newer model laptops by the same OEM use the same audio/media controllers under the hood in some case and I can use the newer driver from the updated model.
When I bought a 7700k over the summer, I went by benchmarks which showed it over Ryzen for most non-parallel workloads. I suspect these numbers bring Ryzen much closer if not beyond. With all these old benchmarks online, CPU shoppers are likely to be misled.
Thinking further, I wonder how benchmarkers patch machines? Will they keep anti-virus enabled so that they receive the 2018-01 patch?
Reading the detailed report[1], it sounds like tls-sni-01 requires being able to serve an invalid certificate temporarily. As far as I know, CDNs won't let you do that. This problem is probably more related to shared webhosts (which is hinted at in the detailed report).
I couldn't agree more. As I've been devising a patching plan over the past few days I couldn't help but wonder "how long will I have to do this"? My hope is that in future OS releases (say, Windows Client/Server 1803) the mitigations will be default-on for clean installations (minimally).