Skip to content
This repository was archived by the owner on May 13, 2024. It is now read-only.

Conversation

@benjwright
Copy link
Contributor

This updates the security bug page on webrtc.org to have more relevant information. Instead of listing vulnerabilities we should just directly link to the trackers. This way the page won't get stale over time and we can provide our users with up to date information.

This is the github account for [email protected].

Copy link
Member

@MirkoBonadei MirkoBonadei left a comment

Choose a reason for hiding this comment

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

LGTM with the comment addressed.

Copy link

@psla psla left a comment

Choose a reason for hiding this comment

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

Looks good. A few nits.

Please be sure to subscribe to the mailing list to stay up to date.

### Applying Security Patches - Standalone Clients
Note that we will generally NOT merge security fixes backwards to any branches,
Copy link

Choose a reason for hiding this comment

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

See my comment below. lkgr gets security fixes, and there are no other branches in webrtc codebase.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Most commonly people use chrome builds as a tag.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants