Fixes #16572: Update security doc after 6.0 #662
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
peckpeck
reviewed
Jan 17, 2020
| the public key coming from previous inventory and to ensure it really comes from the right node.It avoids treating a | ||
| malicious (or bogus) inventory coming from another node, and you should check the public key when accepting a new node. | ||
| * Once a node has sent a signed inventory, no unsigned inventory will be accepted for this node. | ||
| === Syslog reporting |
There was a problem hiding this comment.
maybe add a sentence saying that from 6.0 it is disabled by default
|
PR updated with a new commit |
peckpeck
approved these changes
Jan 17, 2020
|
This PR is not mergeable to upper versions. |
|
OK, squash merging this PR |
amousset
force-pushed
the
arch_16572/update_security_doc_after_6_0
branch
from
5964cac
to
3f46843
Compare
This pull request was closed.
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.
https://issues.rudder.io/issues/16572