Groups > comp.lang.java.programmer > #32163

Re: netty with ssl

Newsgroups	comp.lang.java.programmer
Date	2015-07-27 08:09 -0700
References	<7224870d-053b-449f-84a5-61e31af54cc6@googlegroups.com> <mp55hl$an9$1@dont-email.me> <0984fdc3-6cbb-4c3a-92c9-9ee4053edc67@googlegroups.com> <e6b9ed5d-b489-4f03-9d77-586ddacac82e@googlegroups.com> <mp5d2i$6hn$1@dont-email.me>
Message-ID	<fbbe5231-a76b-4d39-abdb-ae4b439959e8@googlegroups.com> (permalink)
Subject	Re: netty with ssl
From	e.d.programmer@gmail.com

Show all headers | View raw

On Monday, July 27, 2015 at 9:54:02 AM UTC-4, Eric Sosman wrote:
>      It's too bad that the error message used the ambiguous "CST" without
> an accompanying "UTC+8:00" to avoid confusion.
> 
> -- 
> esosman@comcast-dot-net.invalid
> "Don't be afraid of work. Make work afraid of you." -- TLM

That would make more sense if China refers to their UTC+8:00 as CST.  They really should be unique.  Around here CST is Central Standard Time (UTC - 6:00).
If you Google the error the first result does appear to have a likely solution.
http://stackoverflow.com/questions/15076820/java-sslhandshakeexception-no-cipher-suites-in-common

Thread

netty with ssl Louie <liuhongyuand@gmail.com> - 2015-07-27 03:33 -0700
  Re: netty with ssl Eric Sosman <esosman@comcast-dot-net.invalid> - 2015-07-27 07:45 -0400
    Re: netty with ssl Louie <liuhongyuand@gmail.com> - 2015-07-27 05:45 -0700
      Re: netty with ssl e.d.programmer@gmail.com - 2015-07-27 06:26 -0700
        Re: netty with ssl Eric Sosman <esosman@comcast-dot-net.invalid> - 2015-07-27 09:53 -0400
          Re: netty with ssl e.d.programmer@gmail.com - 2015-07-27 08:09 -0700
  Re: netty with ssl Louie <liuhongyuand@gmail.com> - 2015-07-28 00:10 -0700
    Re: netty with ssl e.d.programmer@gmail.com - 2015-07-28 05:44 -0700
  Re: netty with ssl phalgun251@gmail.com - 2016-03-02 09:53 -0800

csiph-web