Use Forgejo workflows and registry
All checks were successful
publish-latest / docker (push) Successful in 9s
ci / test (3.10) (push) Successful in 19s
ci / test (3.12) (push) Successful in 19s
ci / test (3.13) (push) Successful in 19s
ci / container (push) Successful in 7s
publish-image / docker (push) Successful in 8s
All checks were successful
publish-latest / docker (push) Successful in 9s
ci / test (3.10) (push) Successful in 19s
ci / test (3.12) (push) Successful in 19s
ci / test (3.13) (push) Successful in 19s
ci / container (push) Successful in 7s
publish-image / docker (push) Successful in 8s
This commit is contained in:
parent
dbc7464b58
commit
e7bde2b3f4
12 changed files with 134 additions and 40 deletions
12
SECURITY.md
12
SECURITY.md
|
|
@ -8,13 +8,11 @@ begin.
|
|||
|
||||
## Reporting a vulnerability
|
||||
|
||||
Do not open a public issue for a suspected vulnerability. Prefer GitHub's
|
||||
private vulnerability reporting from the repository's Security tab. Include
|
||||
the affected commit or version, impact, reproduction steps, and any suggested
|
||||
mitigation.
|
||||
|
||||
If private reporting is not enabled, ask the maintainer for a private reporting
|
||||
channel without disclosing vulnerability details publicly.
|
||||
Do not open a public issue for a suspected vulnerability. Contact the
|
||||
maintainer through an established private channel and include the affected
|
||||
commit or version, impact, reproduction steps, and any suggested mitigation.
|
||||
If you do not have a private contact method, ask for one in an issue without
|
||||
disclosing vulnerability details.
|
||||
|
||||
Do not include real SNMP credentials, `.env`, `config.ini`, `state.json`,
|
||||
controller addresses, AP names, or unredacted logs. Reports will be
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue