-
Notifications
You must be signed in to change notification settings - Fork 861
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
Introduced ENABLE_ENCRYPTION flag, ON by default. #670
Conversation
…off haicrypt and SSL deps. Strictenc still supported without ability to set pw
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.
@ethouris Can you please check that when two peers have different encryption build definition, the expected behavior is respected.
E.g. two srt-live-transmit
instances. One built with encryption enabled, the second- with the encryption disabled.
Caller with encryption enabled. Listener with encryption disabled.
Caller | Listener | Connection | |
---|---|---|---|
no strict | no pwd | no strict | established |
no strict | no pwd | strict | established |
no strict | pwd | no strict | established |
no strict | pwd | strict | rejected |
According to what I have tested, the only case when it matters is when you have one side with encryption supported and configured, and the other side with encryption unsupported. The current state is that with such a combination you need to have both sides strict encryption off, otherwise the connection is rejected. |
Please specify which cases you've tested. |
|
Disabling the encryption throws an error and ends the build configuration. Running: ./configure --disable-encryption Throws the following error: It appears that this issue should not be labeled as DONE. Not sure is it requires a separate issue. |
Hi @hgs-gmicros |
Fixes #666
This introduces the compile option for encryption (cmake:
SRT_ENABLE_ENCRYPTION=OFF
, configure:--disable-encryption
). When used: