Yes, I believe that a strike-out solution is the correct approach.
This is because someone setting up SSL would definitely test to make sure that it is at least running correctly. For such a person, and indeed everyone else, a warning would suffice to highlight that something is broken. The admin would either discover by themselves and fix it, or it would get reported. In the down time, people can still get stuff done.
In this case, A change in Chrome is what caused the SSL configuration on the server to become broken. This is not the fault of the Server Admin. Some weaknesses (https://weakdh.org
) were discovered and caused Chrome to change it's behaviour and it broke many sites, so of which may not even be possible to address (assuming there are home broadband routers out there which dared to be "secure" and use SSL, and are vulnerable to this issue, then the owners of these routers can no longer manage their routers, even though the admin page is only accessible from the LAN, and SSL was just a nice-to-have feature, not a necessity).
Yea, basically, Google and other browser vendors should scream loudly and sensibly when they believe a user is straying into trouble, but they should never assume to know more than the user what exactly is going on and leave the user without the ultimate choice in what action to take.