[DOC][master] #63469 Issue - Replaced the key rejection paragraph with suggested fix & Added a links..#63584
[DOC][master] #63469 Issue - Replaced the key rejection paragraph with suggested fix & Added a links..#63584v-aryan wants to merge 2 commits intosaltstack:masterfrom
Conversation
|
Hi there! Welcome to the Salt Community! Thank you for making your first contribution. We have a lengthy process for issues and PRs. Someone from the Core Team will follow up as soon as possible. In the meantime, here’s some information that may help as you continue your Salt journey.
There are lots of ways to get involved in our community. Every month, there are around a dozen opportunities to meet with other contributors and the Salt Core team and collaborate in real time. The best way to keep track is by subscribing to the Salt Community Events Calendar. |
|
Please do tell about the changes which are wrong and need to be solved ! |
dmurphy18
left a comment
There was a problem hiding this comment.
Spelling mistakes, and should the updated messages wrap at 72 column, or let them free flow and force the user to scroll to end of line, believe they need to wrap similar to the messages being replaced.
|
Please address the changes requested above |
|
Fixed the typos |
|
Looks like there's a problem generating the man pages |
|
Also, please rebase and resolve conflicts |
What does this PR do?
This PR fixes the first suggested issue which is mentioned in the guides for replacing the content with another and adding a link for [removal/rejection sections]
What issues does this PR fix or reference?
Fixes:
The Salt Master generates a new AES key to encrypt its publications at certain events such as a Master restart or the removal of a Minion key. If you are encountering this problem of too many minions re-authing against the Master, you will need to recalibrate your setup to reduce the rate of events like a Master restart or Minion key removal (salt-key -d).
To
The Salt Master generates a new AES key to encrypt its publications at certain events such as a Master restart or the removal/rejection of a Minion key. If you are encountering this problem of too many minions re-authing against the Master, you will need to recalibrate your setup to reduce the rate of events like a Master restart, Minion key removal (salt-key -d) or Minion key rejection (salt-key -r).
And
A rotating AES key is used to encrypt jobs that are sent to the Salt minion by the Salt master, and to encrypt connections to the Salt master fileserver. A new key is generated and used each time the Salt master restarts and each time a Salt minion key is deleted using the salt-key command.
To
A rotating AES key is used to encrypt jobs that are sent to the Salt minion by the Salt master, and to encrypt connections to the Salt master fileserver. A new key is generated and used each time the Salt master restarts and each time a Salt minion key is deleted/rejected using the salt-key command.
Merge requirements satisfied?
First suggested fix was fixed and the second suggested fix cannot be find which is in "ROTATING SECURITY KEYS" later on it was mentioned that it can be founded on next repository ("https://github.com/saltstack/salt-get-started/blob/7d87b3323913e9b5191fee739d52894ac6ed3811/system/communication.md").