[jira] [Updated] (IGNITE-6167) Ability to enabled TLS protocols and cipher suites

2018-08-21 Thread Vladimir Ozerov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-6167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-6167:

Fix Version/s: 2.7

> Ability to enabled TLS protocols and cipher suites
> --
>
> Key: IGNITE-6167
> URL: https://issues.apache.org/jira/browse/IGNITE-6167
> Project: Ignite
>  Issue Type: Wish
>  Components: security
>Affects Versions: 2.1
>Reporter: Jens Borgland
>Assignee: Mikhail Cherkasov
>Priority: Major
> Fix For: 2.7
>
>
> It would be very useful to be able to, in addition to the 
> {{javax.net.ssl.SSLContext}}, either specify a custom 
> {{javax.net.ssl.SSLServerSocketFactory}} and a custom 
> {{javax.net.ssl.SSLSocketFactory}}, or to be able to at least specify the 
> enabled TLS protocols and cipher suites.
> I have noticed that the 
> {{org.apache.ignite.internal.util.nio.ssl.GridNioSslFilter}} has support for 
> the latter but I cannot find a way of getting a reference to the filter 
> instance. The {{GridNioSslFilter}} also isn't used by {{TcpDiscoverySpi}} as 
> far as I can tell.
> Currently (as far as I can tell) there is no way of specifying the enabled 
> cipher suites and protocols used by Ignite, without doing it globally for the 
> JRE.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (IGNITE-6167) Ability to enabled TLS protocols and cipher suites

2018-08-20 Thread Vladimir Ozerov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-6167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-6167:

Ignite Flags: Docs Required

> Ability to enabled TLS protocols and cipher suites
> --
>
> Key: IGNITE-6167
> URL: https://issues.apache.org/jira/browse/IGNITE-6167
> Project: Ignite
>  Issue Type: Wish
>  Components: security
>Affects Versions: 2.1
>Reporter: Jens Borgland
>Assignee: Mikhail Cherkasov
>Priority: Major
>
> It would be very useful to be able to, in addition to the 
> {{javax.net.ssl.SSLContext}}, either specify a custom 
> {{javax.net.ssl.SSLServerSocketFactory}} and a custom 
> {{javax.net.ssl.SSLSocketFactory}}, or to be able to at least specify the 
> enabled TLS protocols and cipher suites.
> I have noticed that the 
> {{org.apache.ignite.internal.util.nio.ssl.GridNioSslFilter}} has support for 
> the latter but I cannot find a way of getting a reference to the filter 
> instance. The {{GridNioSslFilter}} also isn't used by {{TcpDiscoverySpi}} as 
> far as I can tell.
> Currently (as far as I can tell) there is no way of specifying the enabled 
> cipher suites and protocols used by Ignite, without doing it globally for the 
> JRE.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (IGNITE-6167) Ability to enabled TLS protocols and cipher suites

2018-08-01 Thread Mikhail Cherkasov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-6167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mikhail Cherkasov updated IGNITE-6167:
--
Summary: Ability to  enabled TLS protocols and cipher suites  (was: Ability 
to set custom SSLServerSocketFactory and SSLSocketFactory or enabled TLS 
protocols and cipher suites)

> Ability to  enabled TLS protocols and cipher suites
> ---
>
> Key: IGNITE-6167
> URL: https://issues.apache.org/jira/browse/IGNITE-6167
> Project: Ignite
>  Issue Type: Wish
>  Components: security
>Affects Versions: 2.1
>Reporter: Jens Borgland
>Assignee: Mikhail Cherkasov
>Priority: Major
>
> It would be very useful to be able to, in addition to the 
> {{javax.net.ssl.SSLContext}}, either specify a custom 
> {{javax.net.ssl.SSLServerSocketFactory}} and a custom 
> {{javax.net.ssl.SSLSocketFactory}}, or to be able to at least specify the 
> enabled TLS protocols and cipher suites.
> I have noticed that the 
> {{org.apache.ignite.internal.util.nio.ssl.GridNioSslFilter}} has support for 
> the latter but I cannot find a way of getting a reference to the filter 
> instance. The {{GridNioSslFilter}} also isn't used by {{TcpDiscoverySpi}} as 
> far as I can tell.
> Currently (as far as I can tell) there is no way of specifying the enabled 
> cipher suites and protocols used by Ignite, without doing it globally for the 
> JRE.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (IGNITE-6167) Ability to enabled TLS protocols and cipher suites

2018-08-01 Thread Mikhail Cherkasov (JIRA)


 [ 
https://issues.apache.org/jira/browse/IGNITE-6167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mikhail Cherkasov updated IGNITE-6167:
--
Summary: Ability to enabled TLS protocols and cipher suites  (was: Ability 
to  enabled TLS protocols and cipher suites)

> Ability to enabled TLS protocols and cipher suites
> --
>
> Key: IGNITE-6167
> URL: https://issues.apache.org/jira/browse/IGNITE-6167
> Project: Ignite
>  Issue Type: Wish
>  Components: security
>Affects Versions: 2.1
>Reporter: Jens Borgland
>Assignee: Mikhail Cherkasov
>Priority: Major
>
> It would be very useful to be able to, in addition to the 
> {{javax.net.ssl.SSLContext}}, either specify a custom 
> {{javax.net.ssl.SSLServerSocketFactory}} and a custom 
> {{javax.net.ssl.SSLSocketFactory}}, or to be able to at least specify the 
> enabled TLS protocols and cipher suites.
> I have noticed that the 
> {{org.apache.ignite.internal.util.nio.ssl.GridNioSslFilter}} has support for 
> the latter but I cannot find a way of getting a reference to the filter 
> instance. The {{GridNioSslFilter}} also isn't used by {{TcpDiscoverySpi}} as 
> far as I can tell.
> Currently (as far as I can tell) there is no way of specifying the enabled 
> cipher suites and protocols used by Ignite, without doing it globally for the 
> JRE.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)