Navigation Menu

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

fix sdes loopback more #657

Merged
merged 1 commit into from Jun 16, 2020
Merged

fix sdes loopback more #657

merged 1 commit into from Jun 16, 2020

Conversation

fippo
Copy link
Contributor

@fippo fippo commented May 5, 2020

loopbackAnswer = loopbackAnswer
.replace(/a=crypto:0 AES_CM_128_HMAC_SHA1_32\sinline:.{44}/, '');
.replace(/a=crypto:1 .*/, '')
.replace(/a=crypto:2 .*/, '');
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should this be .replace(/a=crypto:[1-9]+ .*/g, '')?
are we guaranteed that the first crypto algo is always OK to use?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we are but this is sdes and it seems like chrome might even not be compliant in not handling multiple a=crypto in an answer.
Updated

@fippo
Copy link
Contributor Author

fippo commented May 5, 2020

lint failure is... meh but too hard to fix. This is unlikely a regression from this change but please use 👀 to double check

@alvestrand alvestrand merged commit 1af574b into webrtc:master Jun 16, 2020
@fippo fippo deleted the fix-loopback branch June 16, 2020 11:55
@fippo fippo mentioned this pull request Jun 17, 2020
MirkoBonadei pushed a commit that referenced this pull request Jun 18, 2020
see comments in #666, #657 was wrong
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants