Re: [ubuntu-studio-devel] Our website

2017-05-31 Thread Len Ovens
On Wed, 31 May 2017, Jonathan Aquilina wrote: One thing that wasnt mentioned here. If you guys use google chrome, and im not sure if chromium supports this but have you all noticed the browser shows you if a site is secure and using https or not? It seems like they are cracking down on http

Re: [ubuntu-studio-devel] Our website

2017-05-31 Thread Jonathan Aquilina
One thing that wasnt mentioned here. If you guys use google chrome, and im not sure if chromium supports this but have you all noticed the browser shows you if a site is secure and using https or not? It seems like they are cracking down on http based sites. I have experience with Lets encrypt

Re: [ubuntu-studio-devel] Our website

2017-05-30 Thread Hank Stanglow
Count me in with those who thing everything should be encrypted, including email and SMS. Now that Let's Encrypt exists I can't see any reason not to use https. I just did a nmap of ubuntustudio.org and see that it's running Apache 2.4.7 on Ubuntu which I believe means 14.04 (Trusty). Setting

Re: [ubuntu-studio-devel] Our website

2017-05-30 Thread Len Ovens
On Tue, 30 May 2017, Hank Stanglow wrote: use https. I just did a nmap of ubuntustudio.org and see that it's running Apache 2.4.7 on Ubuntu which I believe means 14.04 (Trusty). Setting up Let's Encrypt on 14.04 is a bit of a hassle. I tried it for a few days before As happens I have set up

Re: [ubuntu-studio-devel] Our website

2017-05-30 Thread lukefromdc
First reason is to defeat Verizon's "UIDH" online tracking header https://www.verizonwireless.com/support/unique-identifier-header-faqs/ and no doubt to defeat similar tracking that other ISPs will roll out. They are used as unblockable trackers for ad serving partners but do not work with https

[ubuntu-studio-devel] Our website

2017-05-30 Thread Len Ovens
I had this conversation on IRC. Anyone know if this is a problem? My web understanding is old. - 06:11 < mchelen> any reason why ubuntustudio.org doesn't default to HTTPS? 07:56 < OvenWerks> mchelen: no idea. 09:15 < mchelen>