00013312eb
Signed-off-by: Stefan Weil <sw@weilnetz.de>
25 lines
1.1 KiB
Markdown
25 lines
1.1 KiB
Markdown
# Security Policy
|
||
|
||
## Supported Versions
|
||
|
||
We actively support BigBlueButton through the community forums and through security updates.
|
||
|
||
| Version | Supported |
|
||
| ------- | ------------------ |
|
||
| 2.5.x (or earlier) | :x: |
|
||
| 2.6.x | :white_check_mark: |
|
||
| 2.7.x | :white_check_mark: |
|
||
| 3.0.x | :x: |
|
||
|
||
We have released 2.7 to the community and are going to support both 2.6 and 2.7 together for the coming months (while we're actively developing the next release). Also, BigBlueButton 2.5 is now end of life.
|
||
|
||
As such, we recommend that all administrators deploy 2.7 going forward. You'll find [many improvements](https://docs.bigbluebutton.org/2.7/new-features) in this newer version.
|
||
|
||
## Reporting a Vulnerability
|
||
|
||
If you believe you have found a security vulnerability in BigBlueButton please let us know directly by
|
||
- using GitHub's "Report a vulnerability" functionality on https://github.com/bigbluebutton/bigbluebutton/security/advisories
|
||
- or e-mailing security@bigbluebutton.org with as much detail as possible.
|
||
|
||
Regards,... [BigBlueButton Team](https://docs.bigbluebutton.org/support/faq.html#bigbluebutton-committer)
|