3 added 38 characters in body
source | link

For several years I see that Google, Facebook, etc start serving (and even redirect to) content via HTTPS.

Serving sites that prompts passwords in insecure HTTP was wrong even in 1999 but it considered acceptable even in 2010.

But nowadays even public pages (like queries from Bing/Google) is served via HTTPS.

What events caused mass migration to HTTPS? Wikileaks scandal, US / EU law enforcement, reduced cost of SSL/TSL handshake with generally dropped cost of server time, growing up IT culture level in management?

Even public efforts like https://letsencrypt.org/ started not so long ago...

@briantist As I also maintain hobby sites and interested in cheap/effortless SSL/TLS solution. For VPS (which starts from 5$/month) I recently evaluated Let's encrypt with certbot (other bots available) in webroot operation mode. This provides me with valid SAN certificate for 3 month (and it is in cron job - renewal performed a month before expiration date):

certbot certonly -n --expand --webroot \
        -w /srv/www/base/ -d example.com \
        -w /srv/www/blog/ -d blog.example.com

For several years I see that Google, Facebook, etc start serving (and even redirect to) content via HTTPS.

Serving sites that prompts passwords in insecure HTTP was wrong even in 1999 but it considered acceptable even in 2010.

But nowadays even public pages (like queries from Bing/Google) is served via HTTPS.

What events caused mass migration to HTTPS? Wikileaks scandal, US / EU law enforcement, reduced cost of SSL/TSL handshake with generally dropped cost of server time, growing up IT culture level in management?

Even public efforts like https://letsencrypt.org/ started not so long ago...

@briantist As I also maintain hobby sites and interested in cheap/effortless SSL/TLS solution I recently evaluated Let's encrypt with certbot (other bots available) in webroot operation mode. This provides me with valid SAN certificate for 3 month (and it is in cron job - renewal performed a month before expiration date):

certbot certonly -n --expand --webroot \
        -w /srv/www/base/ -d example.com \
        -w /srv/www/blog/ -d blog.example.com

For several years I see that Google, Facebook, etc start serving (and even redirect to) content via HTTPS.

Serving sites that prompts passwords in insecure HTTP was wrong even in 1999 but it considered acceptable even in 2010.

But nowadays even public pages (like queries from Bing/Google) is served via HTTPS.

What events caused mass migration to HTTPS? Wikileaks scandal, US / EU law enforcement, reduced cost of SSL/TSL handshake with generally dropped cost of server time, growing up IT culture level in management?

Even public efforts like https://letsencrypt.org/ started not so long ago...

@briantist As I also maintain hobby sites and interested in cheap/effortless SSL/TLS solution. For VPS (which starts from 5$/month) I recently evaluated Let's encrypt with certbot (other bots available) in webroot operation mode. This provides me with valid SAN certificate for 3 month (and it is in cron job - renewal performed a month before expiration date):

certbot certonly -n --expand --webroot \
        -w /srv/www/base/ -d example.com \
        -w /srv/www/blog/ -d blog.example.com
2 added 486 characters in body
source | link

For several years I see that Google, Facebook, etc start serving (and even redirect to) content via HTTPS.

Serving sites that prompts passwords in insecure HTTP was wrong even in 1999 but it considered acceptable even in 2010.

But nowadays even public pages (like queries from Bing/Google) is served via HTTPS.

What events caused mass migration to HTTPS? Wikileaks scandal, US / EU law enforcement, reduced cost of SSL/TSL handshake with generally dropped cost of server time, growing up IT culture level in management?

Even public efforts like https://letsencrypt.org/ started not so long ago...

@briantist As I also maintain hobby sites and interested in cheap/effortless SSL/TLS solution I recently evaluated Let's encrypt with certbot (other bots available) in webroot operation mode. This provides me with valid SAN certificate for 3 month (and it is in cron job - renewal performed a month before expiration date):

certbot certonly -n --expand --webroot \
        -w /srv/www/base/ -d example.com \
        -w /srv/www/blog/ -d blog.example.com

For several years I see that Google, Facebook, etc start serving (and even redirect to) content via HTTPS.

Serving sites that prompts passwords in insecure HTTP was wrong even in 1999 but it considered acceptable even in 2010.

But nowadays even public pages (like queries from Bing/Google) is served via HTTPS.

What events caused mass migration to HTTPS? Wikileaks scandal, US / EU law enforcement, reduced cost of SSL/TSL handshake with generally dropped cost of server time, growing up IT culture level in management?

Even public efforts like https://letsencrypt.org/ started not so long ago...

For several years I see that Google, Facebook, etc start serving (and even redirect to) content via HTTPS.

Serving sites that prompts passwords in insecure HTTP was wrong even in 1999 but it considered acceptable even in 2010.

But nowadays even public pages (like queries from Bing/Google) is served via HTTPS.

What events caused mass migration to HTTPS? Wikileaks scandal, US / EU law enforcement, reduced cost of SSL/TSL handshake with generally dropped cost of server time, growing up IT culture level in management?

Even public efforts like https://letsencrypt.org/ started not so long ago...

@briantist As I also maintain hobby sites and interested in cheap/effortless SSL/TLS solution I recently evaluated Let's encrypt with certbot (other bots available) in webroot operation mode. This provides me with valid SAN certificate for 3 month (and it is in cron job - renewal performed a month before expiration date):

certbot certonly -n --expand --webroot \
        -w /srv/www/base/ -d example.com \
        -w /srv/www/blog/ -d blog.example.com
    Tweeted twitter.com/StackWebmasters/status/824256088547672066
    Post Reopened by dan
    Post Made Community Wiki by dan
    Post Closed as "primarily opinion-based" by closetnoc, dan
1
source | link

What events caused mass migration to HTTPS?

For several years I see that Google, Facebook, etc start serving (and even redirect to) content via HTTPS.

Serving sites that prompts passwords in insecure HTTP was wrong even in 1999 but it considered acceptable even in 2010.

But nowadays even public pages (like queries from Bing/Google) is served via HTTPS.

What events caused mass migration to HTTPS? Wikileaks scandal, US / EU law enforcement, reduced cost of SSL/TSL handshake with generally dropped cost of server time, growing up IT culture level in management?

Even public efforts like https://letsencrypt.org/ started not so long ago...