Hi Maxim, When you set the real certificate expiration as I year, I considered the timestamp would be counted from the deployment day but not the build day. For example, if I deployed an incubator 2.0 version on Jan, 24th 2015, then the certificate will be expired on Jan, 24th 2016, but the build day could be on Jun, 2014.
Sent from Mail for Windows 10 刘文涛 Wentao Liu Partner of a cloud company Hunan Yun Zhong Man Bu Information Technology corp.Ltd 湖南云中漫步信息技术有限公司 Mobile phone: +86-13687359517 Fax: +86-731-88716009 From: Maxim Solodovnik Sent: 2015年11月25日 21:17 To: dev Cc: [email protected] Subject: Re: Signer certificate expiry it is self-signed certificate with expiration period: 6 months Releases are being signed by real certificates with expiration period: 1 year On Wed, Nov 25, 2015 at 6:26 PM, Susheel Jalali <[email protected]> wrote: > Dear OpenMeetings Developers, > > At build time we are seeing, in the build log, a warning that signer > certificate will expire in six months, as shown below. > Can we not use this instance after six months? > > We appreciate any inisghts. > > *Build comment* > > [signjar] Warning: > [signjar] The signer certificate will expire within six months. > [signjar] No -tsa or -tsacert is provided and this jar is not > timestamped. Without a timestamp, users may not be able to validate this > jar after the signer certificate's expiration date (2016-02-22) or after > any future revocation date. > > -- > Sincerely > > Susheel Jalali > > Coscend Communications Solutions__ > > Web site:<http://www.coscend.com/>www.Coscend.com > > ------------------------------------------------------------------ > > CONFIDENTIALITY NOTICE: See 'Confidentiality Notice Regarding E-mail > Messages from Coscend Communications Solutions' posted at: < > http://www.coscendcommunications.com/Terms_and_Conditions.html> > http://www.Coscend.com/Terms_and_Conditions.html > > > -- WBR Maxim aka solomax
