[
https://issues.apache.org/jira/browse/KNOX-733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430520#comment-15430520
]
chris snow commented on KNOX-733:
---------------------------------
This sounds good. A few questions ...
- If the CLI is generating the truststore, the output should include the
certificate signature and inform the user to manually verify that the
certificate signature is correct (i.e. it is not the injected certificate of an
attacker performing a man-in-the-middle attack)?
- The developer may also want to build the truststore manually and provide a
truststore password? Is it possible to provide certificate passwords too in
truststores?
- If the developer is using their own certificate authority or a less well
known public certificate authority, the truststore may not need the cluster
certificate and instead only need the CA certificate?
- In more secure environments, is it possible to configure knox server to
require client certificates to authenticate to the server? If so, the CLI
should also be able to access the client certificate in a keystore?
> Knox shell client is susceptible to man-in-the-middle attack
> -------------------------------------------------------------
>
> Key: KNOX-733
> URL: https://issues.apache.org/jira/browse/KNOX-733
> Project: Apache Knox
> Issue Type: Bug
> Reporter: chris snow
> Assignee: chris snow
> Fix For: 0.10.0
>
>
> The Knox shell client does not verify the certificate of the server.
> One option would be to provide another method where developers can provide
> their own client, e.g.
> public static Hadoop login( String url, String username, String password,
> HttpClient client ) throws URISyntaxException { }
> https://github.com/apache/knox/blob/master/gateway-shell/src/main/java/org/apache/hadoop/gateway/shell/Hadoop.java#L60
> I can provide a patch if you are happy with this approach.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
