Path: csiph.com!optima2.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!1.eu.feeder.erje.net!newsfeed.fsmpi.rwth-aachen.de!newsfeed.straub-nv.de!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Eric Sosman Newsgroups: comp.lang.java.programmer Subject: Re: netty with ssl Date: Mon, 27 Jul 2015 09:53:50 -0400 Organization: A noiseless patient Spider Lines: 39 Message-ID: References: <7224870d-053b-449f-84a5-61e31af54cc6@googlegroups.com> <0984fdc3-6cbb-4c3a-92c9-9ee4053edc67@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Mon, 27 Jul 2015 13:52:18 +0000 (UTC) Injection-Info: mx02.eternal-september.org; posting-host="858a9d65d95f4ea4d355bd116aa2cdbf"; logging-data="6711"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18qaqmqJBH7Gs98z/z/bYoO" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 In-Reply-To: Cancel-Lock: sha1:TMBG4SK8FggK8ROS0XpCvmGG+QU= Xref: csiph.com comp.lang.java.programmer:32162 On 7/27/2015 9:26 AM, e.d.programmer@gmail.com wrote: > On Monday, July 27, 2015 at 8:45:19 AM UTC-4, Louie wrote: >> 在 2015年7月27日星期一 UTC+8下午7:45:35，Eric Sosman写道： >>> On 7/27/2015 6:33 AM, Louie wrote: >>>> Hi >>>> I'm using the netty with ssl, but it doesn't work.This is my error log and the ssl code. >>>> >>>> error code: >>>> adding as trusted cert: >>>> Subject: EMAILADDRESS=xxx, CN=Louie, OU=SDG, O=SDG, L=SH, ST=SH, C=CN >>>> Issuer: EMAILADDRESS=xxx, CN=Louie, OU=SDG, O=SDG, L=SH, ST=SH, C=CN >>>> Algorithm: RSA; Serial number: 0xffc3decf334dd844 >>>> Valid from Mon Jul 27 17:05:34 CST 2015 until Thu Jul 24 17:05:34 CST 2025 >>>> [...] >>> >>> Just a wild guess, because I know little or nothing about this >>> stuff, BUT: Have you noticed that "Mon Jul 27 17:05:34 CST" is in >>> the future (as of your post at "Mon, 27 Jul 2015 03:33:39 -0700 (PDT)")? >>> That is, perhaps your authentication failed because the certificate was >>> not yet valid! If so, maybe things will start working if you wait a >>> few more hours. >>> >>> Or maybe not -- Remember, I said "wild guess." >> >> Thanks for your help, because I'm in China, the time will different from you. > > Today is Monday in North America. Assuming the 17:05:34 is hours:minutes:seconds, the time is still future. Time is the same everywhere when you reference time zone (CST), though offhand I don't think that's your problem, or only problem. 17:05:34 Monday in China Standard Time (UTC+8:00) was 09:05:34 UTC, or 05:05:34 Eastern Daylight Time (UTC-4:00), or 02:05:34 Pacific Daylight Time (UTC-7:00), all well before the time stamp of the original posting. 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