[jira] [Resolved] (DIRKRB-703) Reduce client-side information leakage of MySQL plugin

2018-03-27 Thread Frank Zeng (JIRA)
[ https://issues.apache.org/jira/browse/DIRKRB-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Frank Zeng resolved DIRKRB-703. --- Resolution: Fixed > Reduce client-side information leakage of MySQL plugin >

[jira] [Assigned] (DIRKRB-659) Support authentication with NT-ENTERPRISE principal names

2018-03-27 Thread Jiajia Li (JIRA)
[ https://issues.apache.org/jira/browse/DIRKRB-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiajia Li reassigned DIRKRB-659: Assignee: Dmitry Bedrin > Support authentication with NT-ENTERPRISE principal names >

[jira] [Commented] (DIRSERVER-2225) Usage of maven-source-plugin goal jar-no-fork instead of jar

2018-03-27 Thread Emmanuel Lecharny (JIRA)
[ https://issues.apache.org/jira/browse/DIRSERVER-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16416296#comment-16416296 ] Emmanuel Lecharny commented on DIRSERVER-2225: -- Thanks !   Aplying the suggested change

[jira] [Commented] (DIRKRB-659) Support authentication with NT-ENTERPRISE principal names

2018-03-27 Thread Dmitry Bedrin (JIRA)
[ https://issues.apache.org/jira/browse/DIRKRB-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16415099#comment-16415099 ] Dmitry Bedrin commented on DIRKRB-659: -- [~jiajia] hm, that's not that straightforward - there's not a

Re: Studio & Java 9

2018-03-27 Thread Emmanuel Lécharny
Le 27/03/2018 à 08:07, Stefan Seelmann a écrit : > On 03/27/2018 12:45 AM, Emmanuel Lecharny wrote: >> >> Yeah, I really think it's the problem. >> >> I have committed a fix (using 3L instead of 30L) because, anyway, it >> does not make any sense to use such a short timeout. > > Yes, that

Re: Studio & Java 9

2018-03-27 Thread Stefan Seelmann
On 03/27/2018 12:45 AM, Emmanuel Lecharny wrote: > > Yeah, I really think it's the problem. > > I have committed a fix (using 3L instead of 30L) because, anyway, it does > not make any sense to use such a short timeout. Yes, that was clearly the cause, I don't know why that was 30ms, maybe