Skip to content
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 PBKEYLEN negotiation table to the documentation. #2641

Closed
maxsharabayko opened this issue Feb 2, 2023 · 0 comments · Fixed by #2659
Closed

Add PBKEYLEN negotiation table to the documentation. #2641

maxsharabayko opened this issue Feb 2, 2023 · 0 comments · Fixed by #2659
Labels
[docs] Area: Improvements or additions to documentation Type: Maintenance Work required to maintain or clean up the code
Milestone

Comments

@maxsharabayko
Copy link
Collaborator

maxsharabayko commented Feb 2, 2023

Add PBKEYLEN negotiation table to the documentation.

If both parties set PBKEYLEN and the value on both sides is different, this is considered a conflict. It is resolved by the Initiator party, which takes its own value if the SRTO_SENDER option is set to true. Otherwise, it takes the value from the Responder party. The assignment of Initiator-Responder roles matches the Caller-Listener layout. In the case of Rendezvous this assignment depends on the result of the cookie comparison.

* - any.

Initiator Responder Result
SRTO_PBKEYLEN SRTO_SENDER SRTO_PBKEYLEN SRTO_SENDER
0 * 0 * AES-128
0 * AES-128 * AES-128
0 * AES-192 * AES-192
0 * AES-256 * AES-256
AES-128 * 0 i AES-128
AES-128 * AES-128 g AES-128
AES-128 0 AES-192 n AES-192
AES-128 0 AES-256 o AES-256
AES-128 1 AES-192 r AES-128
AES-128 1 AES-256 e AES-128
AES-192 * 0 d AES-192
AES-192 0 AES-128 * AES-128
AES-192 * AES-192 * AES-192
AES-192 0 AES-256 * AES-256
AES-192 1 AES-128 * AES-192
AES-192 1 AES-256 * AES-192
AES-256 * 0 * AES-256
AES-256 0 AES-128 * AES-128
AES-256 0 AES-192 * AES-192
AES-256 * AES-256 * AES-256
AES-256 1 AES-128 * AES-256
AES-256 1 AES-192 * AES-256
@maxsharabayko maxsharabayko added Type: Maintenance Work required to maintain or clean up the code [docs] Area: Improvements or additions to documentation labels Feb 2, 2023
@maxsharabayko maxsharabayko added this to the v1.5.2 milestone Feb 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[docs] Area: Improvements or additions to documentation Type: Maintenance Work required to maintain or clean up the code
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant