-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add an example how a large Cloud would implement tls-crypt-v2 #8
Conversation
@@ -663,7 +663,7 @@ struct clear_control_payload { | |||
The 2048 bits client-specific key ``Kc`` is identical to the key for the control channel encryption. | |||
</t> | |||
<t> | |||
The wrapped key has the foloowing components: | |||
The standard format used by OpenVPN for the wrapped key has the foloowing components: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"following"
openvpn-wire-protocol.xml
Outdated
</ol> | ||
</t> | ||
|
||
<t> Note, since the Wkc format is opaque to the client, a server can decided to use |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"a server can decide"
openvpn-wire-protocol.xml
Outdated
<t> Note, since the Wkc format is opaque to the client, a server can decided to use | ||
a different format. For example when using a large infrastructure, e.g. a Cloud service, | ||
it is desirable to allow using multiple different server keys to be able to replace a | ||
compromised key or to be able to key rotation. </t> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"to be able to do key rotation"
Other than the very minor text correction nitpicks, this looks good to me, FWIW. |
Signed-off-by: Arne Schwabe <[email protected]>
a905c5f
to
7a16c4b
Compare
No description provided.