[
https://issues.apache.org/jira/browse/METRON-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16619935#comment-16619935
]
ASF GitHub Bot commented on METRON-1784:
----------------------------------------
GitHub user mmiklavc opened a pull request:
https://github.com/apache/metron/pull/1204
METRON-1784: Re-allow remote ssh and scp in Centos full dev
## Contributor Comments
https://issues.apache.org/jira/browse/METRON-1784
Tired of having to manually modify sshd_config in full dev for Centos to
re-enable remote ssh and scp manually? Then this PR is for you!
Somewhere along the way the default image for Centos shifted the
sshd_config defaults to disallow remote logins. This reverts that back to the
way we had it before to make it easier to transfer files, login, etc. I also
modified the role + tags so that you can run just the specific task by
providing the tag - see testing example below.
**Testing**
I modified the main playbook.yml for Centos such that you can also test
this via ansible tags against a running instance without tearing it down
completely, should you choose.
- Switch to `metron/metron-deployment/development/centos6`
- Run `vagrant up` if you don't already have a full dev instance running,
or alternatively `vagrant --ansible-tags="enable-remote-ssh" provision` to run
the tag/role for an existing instance.
- Verify that you can now ssh into the box.
- cd into some other directory
- ssh root@node1
- enter password and it should succeed. Previously you would get a
`root@node1: Permission denied (publickey,gssapi-keyex,gssapi-with-mic).`
exception
## Pull Request Checklist
Thank you for submitting a contribution to Apache Metron.
Please refer to our [Development
Guidelines](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61332235)
for the complete guide to follow for contributions.
Please refer also to our [Build Verification
Guidelines](https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds?show-miniview)
for complete smoke testing guides.
In order to streamline the review of the contribution we ask you follow
these guidelines and ask you to double check the following:
### For all changes:
- [x] Is there a JIRA ticket associated with this PR? If not one needs to
be created at [Metron
Jira](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel).
- [x] Does your PR title start with METRON-XXXX where XXXX is the JIRA
number you are trying to resolve? Pay particular attention to the hyphen "-"
character.
- [x] Has your PR been rebased against the latest commit within the target
branch (typically master)?
### For code changes:
- [x] Have you included steps to reproduce the behavior or problem that is
being changed or addressed?
- [x] Have you included steps or a guide to how the change may be verified
and tested manually?
- [x] Have you ensured that the full suite of tests and checks have been
executed in the root metron folder via:
```
mvn -q clean integration-test install &&
dev-utilities/build-utils/verify_licenses.sh
```
- n/a Have you written or updated unit tests and or integration tests to
verify your changes?
- n/a If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [x] Have you verified the basic functionality of the build by building
and running locally with Vagrant full-dev environment or the equivalent?
### For documentation related changes:
- n/a Have you ensured that format looks appropriate for the output in
which it is rendered by building and verifying the site-book? If not then run
the following commands and the verify changes via
`site-book/target/site/index.html`:
```
cd site-book
mvn site
```
#### Note:
Please ensure that once the PR is submitted, you check travis-ci for build
issues and submit an update to your PR as soon as possible.
It is also recommended that [travis-ci](https://travis-ci.org) is set up
for your personal repository such that your branches are built there before
submitting a pull request.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mmiklavc/metron enable-remote-ssh
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/metron/pull/1204.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1204
----
commit 26fefa56691a569055683a843a1cdcf7b66895d6
Author: Michael Miklavcic <michael.miklavcic@...>
Date: 2018-09-19T00:53:27Z
Enable remote ssh/scp login in full dev centos
----
> Re-allow remote ssh and scp in Centos full dev
> ----------------------------------------------
>
> Key: METRON-1784
> URL: https://issues.apache.org/jira/browse/METRON-1784
> Project: Metron
> Issue Type: Improvement
> Reporter: Michael Miklavcic
> Assignee: Michael Miklavcic
> Priority: Major
>
> Centos full dev changed such that remote ssh and scp are disabled by default
> unless you change to the playbook directory and use "vagrant ssh" directly.
> This modifies the sshd_config to set "PasswordAuthentication yes"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
