nanog mailing list archives

Re: Wikipedia drops support for old Android smartphones; mandates TLSv1.2 to read


From: Mike Hammett <nanog () ics-il net>
Date: Tue, 31 Dec 2019 07:39:33 -0600 (CST)

"obvious reasons" 




----- 
Mike Hammett 
Intelligent Computing Solutions 
http://www.ics-il.com 

Midwest-IX 
http://www.midwest-ix.com 

----- Original Message -----

From: "Antonios Chariton" <daknob.mac () gmail com> 
To: "North American Network Operators' Group" <nanog () nanog org> 
Sent: Tuesday, December 31, 2019 3:47:58 AM 
Subject: Re: Wikipedia drops support for old Android smartphones; mandates TLSv1.2 to read 

Ignoring the obvious reasons why TLS is needed and HTTP should not be used, I guess people who want an HTTP version of 
Wikipedia that is read-only and knowingly insecure, censorable, modifiable, etc. can donate a few million dollars to 
the Wikimedia Foundation, before the tax year is over, for the engineers, infrastructure, and everything, and write a 
special note, and maybe Wikipedia may consider this.. Worst case, you just funded a secure encyclopedia and helped it 
grow in 2020 and years to come.. :) 



Let’s see those receipts coming! 




On 31 Dec 2019, at 09:50, Ryan Hamel < ryan () rkhtech org > wrote: 


Just let the old platforms ride off into the sunset as originally planned like the SSL implementations in older JRE 
installs, XP, etc. You shouldn't be holding onto the past. 


Ryan 


On Tue, Dec 31, 2019, 12:41 AM Constantine A. Murenin < mureninc () gmail com > wrote: 

<blockquote>




On Tue, 31 Dec 2019 at 02:29, Matt Hoppes < mattlists () rivervalleyinternet net > wrote: 


<blockquote>
Why do I need Wikipedia SSLed? I know the argument. But if it doesn’t work why not either let it fall back to 1.0 or to 
HTTP. 

This seems like security for no valid reason. 


Exactly. I used the wording from their own page; but I think it's actually misleading. They're actually going out of 
their way to prevent users of "old Android smartphones" from accessing Wikipedia; if they did nothing, everyone would 
still be able to read happily over HTTP. 


C. 

</blockquote>

</blockquote>



Current thread: