Well here's one good reason:

https://www.eff.org/deeplinks/2015/04/china-uses-unencrypted-websites-to-hijack-browsers-in-github-attack

tl;dr: If you use http, anyone can 'man in the middle' the connection and insert almost anything. And they do.

See also https://www.eff.org/encrypt-the-web

regards

Dan


On Mon, May 8, 2017 at 8:44 PM, LucaDC <dicappello@...2144...> wrote:
Hi to all,
I've just heard about this initiative.
It seems something positive but after a first thought I couldn't help
asking: why? What is the purpose to secure a public connection on which no
sensitive data flow?
I've had some sporadic errors with Firefox when connecting to HTTPS sites
because of expired certificates and I was only trying to connect to them
coming from Google so to see their contents for the first time, which
doesn't involve sending sensitive data that deserve encryption; so in those
cases the useless HTTPS layer only prevented me from accessing the service.

I'm probably missing some point that makes this really interesting. Is it
just a trend?

Regards.
Luca




--
View this message in context: http://inkscape.13.x6.nabble.com/Let-s-encrypt-is-this-possible-tp4979718p4979744.html
Sent from the Inkscape - Dev mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@...1656...784...sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel



--

--
Private or confidential message? Public Key available here