fix SUID/SGID bit cleaning API spelling #72
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
thanks @dupuy for pointing this out! |
|
@dupuy to make it complete, it would be great if you could fix it in https://github.com/TelekomLabs/chef-os-hardening/blob/master/TUTORIAL.md as well |
|
OK, I (re?)added the typo fix to TUTORIAL.md, and fixed a rubocop alignment error I introduced when I wrapped a long line - with the additional 2 commits, it is satisfying Travis and Coveralls. |
|
@dupuy great work! |
chris-rock
added a commit
that referenced
this pull request
Jan 28, 2015
fix SUID/SGID bit cleaning API spelling (unkown -> unknown)
rollbrettler
pushed a commit
to rollbrettler/chef-os-hardening
that referenced
this pull request
Sep 16, 2016
add privilege separation via sandbox mode for ssh >= 5.9
schurzi
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Having a misspelling in an API is especially awkward, since fixing the spelling could break the code. But I think this is obscure enough that nobody is likely to be using it already...