Update getremotelogs.sh to accept custom a SSH port #135
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi!
Before anything else, thank you for RedELK! It's been a much welcome addition to and an essential part of our workflow.
This PR adds an SSH port argument to the
getremotelogs.sh
script that defaults to22
.Due to how our lab is structured, we have been using a custom version of RedELK where the teamserver pushes the logs. We finally decided to update our team server setup to match RedELK instead, but we can't use a standard SSH port for the
getremotelogs.sh
script.I can undo the style changes if necessary. They were mostly to quiet down shellcheck.
Regarding the argument count check, I didn't see an issue with passing too many arguments, so opted for a
less than
check to make the SSH port argument optional. Please correct me if I'm wrong.