Path: csiph.com!aioe.org!.POSTED!not-for-mail From: =?UTF-8?Q?Arne_Vajh=c3=b8j?= Newsgroups: comp.lang.java.programmer Subject: Re: SSL trends Date: Thu, 15 Sep 2016 20:18:10 -0400 Organization: Aioe.org NNTP Server Lines: 31 Message-ID: References: NNTP-Posting-Host: 7SK6yTFfqwlIPNBLl3l7Qg.user.gioia.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 X-Notice: Filtered by postfilter v. 0.8.2 Xref: csiph.com comp.lang.java.programmer:35617 On 9/15/2016 4:55 PM, Roedy Green wrote: > There has been a trend to flip from http: to https:. Google has been > pushing this. > > However there are a set of headaches that come with the transition. > 1. clients must have the root cert installed All normal browsers should have that. Not a problem. > 2. certs expire Should be handled via OS/browser updates. Nobody should surf the internet with a OS/browser that is not being updated. Not a problem > 3. there is more CPU overhead Usually there are plenty of CPU available client side. Not a problem. > 4. caching is turned off Wrong. > 5. certs often do not work for some people. People can't access the > website to complain. That is very rare - not "often". Arne