This is clearly a major hassle as it may force you to keep TLS 1.0/1.1 around for longer than you’d like or educate users to install
latest Google Chrome from the Play Store. To get a better understanding what the experience may look like is I tested it on my Android
4.2 table and this is what it it looks like

This is what the built-in browser capabilities are

Unfortunately this will result in a very nasty error that says secure connection cannot be established

Same device with Google Chrome installed passes the capability test with flying colors

My children like to play Minecraft and they often like to play with their friends and cousins who are remote. To do so in the past I would set up my laptop at the house, set up port forwarding on the
router, etc. This would often not work as the router would not accept the changes, my laptop firewall was on etc. Instead I decided to shift all this to the cloud.
In this particular example I will be using Google Cloud Engine since it allows you to have persistent disks. To minimize costs I will automate creation and destruction of minecraft server(s) using Hashicorp’s Terraform.

All the terraform template and files can be found in this specific Github Repo

You will need to sign up for a Google Cloud account. You may also optionally buy a domain name from a registrar so that you don’t need
to enter IP addresses in your minecraft client. If you do so rename dns.tf.disabled to dns.tf and change this section

As described in the README what this set of templates will do is create a persistent disk where you will store your gameplay and spin up
a minecraft server just for that time being. When you want to play
you will need to type

make create

and when you are done playing you will type

make destroy

Cost of this should be minimal. In the TF template I’m setting a persistent disk of size of 10 GB (change that in main.tf if you need to). That will cost you approximately $0.40 per month. On top of it you’d be paying for
g1.small instance cost which is about $0.02 per hour. You can certainly opt for a faster instance by adjusting the instance size in main.tf file.
Also if you are using DNS there will be DNS query costs but those should be minimal.

I was working with a customer trying to configure Fastly’s Log Streaming
and ship logs to their Rsyslog server. Fastly supports sending Syslog over TLS however it appeared that TLS handshake was not succeeding as we
would end up with gibberish in the logs e.g.

It will use the TLS certificate from /etc/letsencrypt and listen to TLS requests on port 5144. There is no client
authentication ie. authmode=anon. If you want to authenticate clients you will need to change authmode to e.g.