While I'm all for the tradition of April fools jokes around the internet, I'm a bit concerned about the nature of this particular one.
- The redirect makes it appear that the site has been compromised, to many people this is likely to affect their trust of the Linux kernel and it's development.
- kernel.org is the main website for the Linux Kernel - not a blog, a fake sales page etc, its the core of Linux.
IMO - The logo is fine, the title is OK, the URL redirect is inappropriate.
Re:The Hurr Durr Archives
by mricon on Tuesday March 31, 2015 @10:42PM
(#9301210)
It redirects to a site with a valid certificate belonging to "The Linux Foundation." To a domain with a whois record belonging to The Linux Foundation. With DNS servers belonging to the Linux Foundation.
Re:The Hurr Durr Archives
by geofft on Tuesday March 31, 2015 @11:14PM
(#9301300)
The first part isn't super reliable. Historically, CAs have just let you put whatever you want there and only enforced the common name. They're supposed to be cleaning up their act (at least for recently-issued certs), but I'd still only trust it for EV certs.
The rest is all valid. (Unless you assume that the hack also hacked DNS, which is plausible but unlikely.)
Re:The Hurr Durr Archives
by iancarroll on Tuesday March 31, 2015 @11:21PM
(#9301332)
Do you have any links regarding that? Regardless, some/most trusted CAs include the OID 2.23.140.1.2.2 when a certificate is OV validated per CA/B guidelines, so you could just look for that.
Link to source: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux....
While I'm all for the tradition of April fools jokes around the internet, I'm a bit concerned about the nature of this particular one.
- The redirect makes it appear that the site has been compromised, to many people this is likely to affect their trust of the Linux kernel and it's development.
- kernel.org is the main website for the Linux Kernel - not a blog, a fake sales page etc, its the core of Linux.
IMO - The logo is fine, the title is OK, the URL redirect is inappropriate.
Come on.
The rest is all valid. (Unless you assume that the hack also hacked DNS, which is plausible but unlikely.)
At $employer -
>Content Blocked (content_filter_denied)
>Content Category: "Suspicious"