public
nobgit
read
NobMail
Based on mailcow: dockerized
Languages
Repository composition by tracked source files.
PHP
49%
JavaScript
35%
HTML
9%
CSS
4%
Shell
2%
Python
1%
Lua
0%
Perl
0%
Ruby
0%
SCSS
0%
Create file
Wiki Documentation
Clone
https://nobgit.com/orgs/nobgit/nobmail.git
ssh://[email protected]:2222/orgs/nobgit/nobmail.git
Trace
SECURITY.md
Trace helps you understand code history line by line. See who changed each line, when it changed, and which commit introduced it.
Author
Date
Commit
Line
Code
1
# Security Policies and Procedures
3
This document outlines security procedures and general policies for the _mailcow: dockerized_ project as found on [mailcow-dockerized](https://github.com/mailcow/mailcow-dockerized).
5
* [Reporting a Vulnerability](#reporting-a-vulnerability)
6
* [Disclosure Policy](#disclosure-policy)
7
* [Comments on this Policy](#comments-on-this-policy)
9
## Reporting a Vulnerability
11
The mailcow team and community take all security vulnerabilities
12
seriously. Thank you for improving the security of our open source
13
software. We appreciate your efforts and responsible disclosure and will
14
make every effort to acknowledge your contributions.
16
Report security vulnerabilities by emailing the mailcow team at:
18
info at servercow.de
20
mailcow team will acknowledge your email as soon as possible, and will
21
send a more detailed response afterwards indicating the next steps in
22
handling your report. After the initial reply to your report, the mailcow
23
team will endeavor to keep you informed of the progress towards a fix and
24
full announcement, and may ask for additional information or guidance.
26
Report security vulnerabilities in third-party modules to the person or
27
team maintaining the module.
29
## Disclosure Policy
31
When the mailcow team receives a security bug report, they will assign it
32
to a primary handler. This person will coordinate the fix and release
33
process, involving the following steps:
35
* Confirm the problem and determine the affected versions.
36
* Audit code to find any potential similar problems.
37
* Prepare fixes for all releases still under maintenance.
39
## Comments on this Policy
41
If you have suggestions on how this process could be improved please submit a
42
pull request.