This one has two super easy ones that don't cross into wierd areas like SEO

- Herd Immunity: If only important data is encrypted we will know who to beat 
on with a wrench to get it. If everything is encrypted rubber hose cryptography 
becomes a bit harder

- Data integrity: Every persons or companies network you transverse with 
un-encrypted data increases the chances that they data can be modified in 
transit. It is possible one day to see a future where Comcast  decides to 
inject or replace ads or redirects on un-encrypted sites to help bolster their 
profit margins. Without using some sort of transit layer encryption or security 
it is hard to be sure that the site didn't get modified in transit.

These are both things that have current real world exploits that are happening 
right now, and are IMO the real reason why everything should at least have an 
https option even if it isnt redirected to by default.

---
Jason Barbier | E: [email protected] 


On Wed, Jan 2, 2019, at 9:09 AM, James Mason wrote:
> Hi John,
> 
> Yes, we can implement HTTPS on the LFNW blog, but it is a low priority.
> 
> Devil's advocate: what benefits are you expecting from having an HTTPS 
> connection to a completely static, public web site?
> 
> - James Mason
> 
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Friday, December 28, 2018 3:03 PM, John Sullivan <[email protected]> wrote:
> 
> > James Mason [email protected] writes:
> >
> > > And without further ado... the URL is
> > > http://blog.linuxfestnorthwest.org
> > > ... or http://blog.lfnw.org for short. Click the RSS icon at the top
> > > or the bottom, for the RSS feed.
> >
> > Thanks, any chance of getting https?
> >
> > -john
> >
> > ----------------------------------------------
> >
> > John Sullivan | Executive Director, Free Software Foundation
> > GPG Key: A462 6CBA FF37 6039 D2D7 5544 97BA 9CE7 61A0 963B
> > https://status.fsf.org/johns | https://fsf.org/blogs/RSS
> >
> > Do you use free software? Donate to join the FSF and support freedom at
> > https://my.fsf.org/join.
> >
> > Fest-list mailing list
> > [email protected]
> > https://lists.blug.org/cgi-bin/mailman/listinfo/fest-list
> 
> 
> _______________________________________________
> Fest-list mailing list
> [email protected]
> https://lists.blug.org/cgi-bin/mailman/listinfo/fest-list
_______________________________________________
Fest-list mailing list
[email protected]
https://lists.blug.org/cgi-bin/mailman/listinfo/fest-list

Reply via email to