[
https://issues.apache.org/jira/browse/ACCUMULO-3719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14487693#comment-14487693
]
Josh Elser edited comment on ACCUMULO-3719 at 4/9/15 5:20 PM:
--------------------------------------------------------------
You can still change the SSH options if you are running Accumulo tests on a
system in which you are worried about MITM attacks. I think this is perfectly
acceptable for the context (why I made the changes). Given that so far, no one
else has even expressed an interest in running tests like this, I think this is
ok. If it actually picks up more adoption (e.g. someone wires it up to
automatically run on EC2), that's a different story.
was (Author: elserj):
You can still change the defaults if you are running Accumulo tests on a system
in which you are worried about MITM attacks. I think this is perfectly
acceptable for the context (why I made the changes). Given that so far, no one
else has even expressed an interest in running tests like this, I think this is
ok. If it actually picks up more adoption (e.g. someone wires it up to
automatically run on EC2), that's a different story.
> Disable strict host key checking for standalone SSH'ing.
> --------------------------------------------------------
>
> Key: ACCUMULO-3719
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3719
> Project: Accumulo
> Issue Type: Bug
> Components: test
> Reporter: Josh Elser
> Assignee: Josh Elser
> Fix For: 1.7.0, 1.6.3
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Leaving strict host key checking enabled is likely to cause more problems
> than it's worth, mostly due to the default required prompt.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
