Re: Toward a 2.0 GA

2019-01-17 Thread Emmanuel Lécharny
On 17/01/2019 15:14, Shawn McKinney wrote: On Jan 16, 2019, at 3:54 PM, Emmanuel Lécharny wrote: The Server, when started, will try to load the Keystore content: o If there is no provided KeyStore file, the server will use create its own Keystore, based on the default SUN provider. o

Re: Toward a 2.0 GA

2019-01-17 Thread Shawn McKinney
> On Jan 16, 2019, at 3:54 PM, Emmanuel Lécharny wrote: > > The Server, when started, will try to load the Keystore content: > > o If there is no provided KeyStore file, the server will use create its own > Keystore, based on the default SUN provider. > o Otherwise, the server will try to

Re: Toward a 2.0 GA

2019-01-16 Thread Emmanuel Lécharny
On 11/01/2019 20:03, Stefan Seelmann wrote: On 1/11/19 11:09 AM, Emmanuel Lécharny wrote: Hi guys, I'm currently checking all the pending JIRAs, trying to evaluate those that need to be closed in the coming release, those that are invalid, and those that need to be postponed. While doing

Re: Toward a 2.0 GA

2019-01-11 Thread Stefan Seelmann
On 1/11/19 11:09 AM, Emmanuel Lécharny wrote: > Hi guys, > > > I'm currently checking all the pending JIRAs, trying to evaluate those > that need to be closed in the coming release, those that are invalid, > and those that need to be postponed. > > While doing that, I see there are quite a few

Toward a 2.0 GA

2019-01-11 Thread Emmanuel Lécharny
Hi guys, I'm currently checking all the pending JIRAs, trying to evaluate those that need to be closed in the coming release, those that are invalid, and those that need to be postponed. While doing that, I see there are quite a few important ones related to TLS and security checks that