-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[FIX]: Update CODEOWNERS and github-actions (#20)
* [FIX] Add asset mappers for the static assets (#15) * update codewoners and add github-actions * update documentation
- Loading branch information
Showing
9 changed files
with
23 additions
and
52 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1 @@ | ||
* @bugloper | ||
.github/ @bugloper @SELISEdigitalplatforms/DEVOPS-ADMIN-ALL-REPOS | ||
CODEOWNERS @bugloper @SELISEdigitalplatforms/DEVOPS-ADMIN-ALL-REPOS | ||
* @SELISEdigitalplatforms/oss-maintainers-gem-gotenberg |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,43 +1,3 @@ | ||
# Reporting a security bug | ||
## Reporting a Vulnerability | ||
|
||
<!-- Note: Need to discuss this --> | ||
All security bugs in gotenberg should be reported to the core team through our private mailing list [[email protected]]. Your report will be acknowledged within 24 hours, and you’ll receive a more detailed response to your email within 48 hours indicating the next steps in handling your report. | ||
|
||
After the initial reply to your report, the security team will endeavor to keep you informed of the progress being made towards a fix and full announcement. These updates will be sent at least every five days, although in practice, it is more likely to be every 24-48 hours. | ||
|
||
If you have not received a reply to your email within 48 hours, or have not heard from the security team for the past five days, there are a few steps you can take: | ||
|
||
## Disclosure Policy | ||
|
||
gotenberg follows a 5-step disclosure policy, which is upheld to the best of our ability. | ||
|
||
1. Security report received and is assigned a primary handler. This person will coordinate the fix and release process. | ||
2. Problem is confirmed and a list of all affected versions is determined. Code is audited to find any potential similar problems. | ||
3. Fixes are prepared for all releases which are still supported. These fixes are not committed to the public repository but rather held locally pending the announcement. | ||
4. A suggested embargo date for this vulnerability is chosen and distros@openwall is notified. This notification will include patches for all versions still under support and a contact address for packagers who need advice back-porting patches to older versions. | ||
5. On the embargo date, the [mailing list][mailing-list] and [security list][security-list] are sent a copy of the announcement. The changes are pushed to the public repository and new gems released to RubyGems. | ||
|
||
Typically, the embargo date will be set 72 hours from the time vendor-sec is first notified, however, this may vary depending on the severity of the bug or difficulty in applying a fix. | ||
|
||
This process can take some time, especially when coordination is required with maintainers of other projects. Every effort will be made to handle the bug in as timely a manner as possible, however, it’s important that we follow the release process above to ensure that the disclosure is handled in a consistent manner. | ||
|
||
## Security Updates | ||
|
||
Security updates will be posted on the [mailing list][mailing-list] and [security list][security-list]. | ||
|
||
## Comments on this Policy | ||
|
||
If you have any suggestions to improve this policy, please email the core team at [[email protected]]. | ||
|
||
## Credit for Reporters | ||
|
||
We highly appreciate the efforts of security researchers who report vulnerabilities to us. We offer the following forms of recognition: | ||
|
||
TODO: Decide on these | ||
* Reporters will be listed on the project's official documentation site. | ||
* Reporters will be acknowledged in the security advisories and release notes associated with the fix. | ||
|
||
We strive to ensure that reporters receive due credit for their valuable contributions to the security of gotenberg. | ||
|
||
[mailing-list]: http://groups.google.com/group/gotenberg/topics | ||
[security-list]: http://groups.google.com/group/gotenberg-security/topics | ||
To report (possible) security issues in this gem, please use Github's [private reporting feature](https://github.com/SELISEdigitalplatforms/gotenberg/security/advisories/new). |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters