News for hackers. Stuff that matters.
Re:Meltdown and Spectre Linux kernel status by proginthebox on Saturday January 06, 2018 @11:02AM (#16085786)
The website serves JS and does not serve it over https, and discusses Spectre bug and how to patch it. I know he is the second most important guy on linux, but the irony.
Re:Meltdown and Spectre Linux kernel status by xroche on Saturday January 06, 2018 @11:35AM (#16085943)
And you probably know much better than the second most important guy on linux what security means on the Internet: securing some javascript script on a random blog.
Re:Meltdown and Spectre Linux kernel status by axiomofquality on Saturday January 06, 2018 @11:43AM (#16085993)
HTTPS should be expected by now - ISPs keep messing with my unencrypted traffic.
Re:Meltdown and Spectre Linux kernel status by lisper on Saturday January 06, 2018 @12:05PM (#16086124)
Then you should get yourself a different ISP or a VPN.
Re:Meltdown and Spectre Linux kernel status by AaronFriel on Saturday January 06, 2018 @12:17PM (#16086224)
This is an extremely easy thing to say for many people around the world.

But for a large number of people - Americans, folks in countries with monopolies or state manipulation of internet traffic - it is not.

Not everyone has a different ISP to choose from. VPNs are a risky proposition and can significantly reduce bandwidth and increase latency.

Re:Meltdown and Spectre Linux kernel status by sigmar on Saturday January 06, 2018 @12:45PM (#16086435)
Anyone that thinks ISPs don't mess with traffic, should check out this malware research

https://www.virusbulletin.com/conference/vb2017/abstracts/la...

Re:Meltdown and Spectre Linux kernel status by mjal on Saturday January 06, 2018 @12:09PM (#16086163)
Some places have no other choices for ISPs. I don't disagree that a VPN would help but that feels like it's simply dismissing that there's a problem.
Re:Meltdown and Spectre Linux kernel status by proginthebox on Saturday January 06, 2018 @12:46PM (#16086445)
It's not about that guy's blog. This causes desensitization to non-HTTPS traffic and when people then actually visit non-HTTPS malicious blog, they get infected. If all "trusted" websites were HTTPS, then whenever there was untrusted access, people will notice it and raise alarm.
Re:Meltdown and Spectre Linux kernel status by dasil003 on Saturday January 06, 2018 @12:08PM (#16086153)
I get the irony, but if you could magically visualize the entire internet security threat matrix, this would fall so far down the list and his other work is so high in terms of impact, that it would absolutely no sense for him to take even one minute away from his other activities to address this.
Re:Meltdown and Spectre Linux kernel status by proginthebox on Saturday January 06, 2018 @12:47PM (#16086455)
Yes, hence my question. I have tried to setup a HTTPS service and it seems incredibly complicated if you have your own domain name. Even with lets encrypt, if you are using github pages for hosting but your own custom domain, you are out of luck. The point is not that he is not serious about security, point is, it is too hard to get normal security correct. And I am not talking about "cryptography is hard". I am talking about tools which should be easy and standardized. Those are hard.
Re:Meltdown and Spectre Linux kernel status by dasil003 on Saturday January 06, 2018 @08:00PM (#16088427)
What question?
Re:Meltdown and Spectre Linux kernel status by boysabr3 on Saturday January 06, 2018 @11:40AM (#16085970)
On a related note, accessing the site over Chrome will full site isolation can help protect against both bugs: https://support.google.com/faqs/answer/7622138#chrome