andreijiroh-dev/website
1
0
Fork 0
mirror of https://mau.dev/andreijiroh-dev/website.git synced 2025-06-07 13:09:32 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

docs(website): update contact pages

Browse source 
Signed-off-by: Andrei Jiroh Halili <ajhalili2006@andreijiroh.xyz>
This commit is contained in:
Andrei Jiroh Halili 2024-07-27 03:44:43 +08:00
parent ec1cdd8172
commit 61a225ad22
No known key found for this signature in database
GPG key ID: 67BFC91B3DA12BE8
5 changed files with 82 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

25
markdown/contact/security.md
View file

@ -8,14 +8,20 @@ Please consult [my general security policy](../security.md) and any project
or org/project-specific policies (via its own `SECURITY.md` file) before proceeding here.
Otherwise, you'll be ignored at best or blocked/muted and reported as spam at worst.
## Looking for PGP keys?
## Looking for PGP and SSH keys?
If you're looking for my PGP keys, please [visit this page](../keys/index.md).
If you're looking for my PGP and SSH keys I use in commits and connecting to machines and code forges
over SSH, please [visit this page](../keys/index.md).
## Security questions
I am not a cybersecurity person or have expertise in cryptography, so sorry if I can't reply to you.
I may redirect you to resources or give advice as my capacity allow.
## Submitting security patches
If you also want to submit a security patch, please DO NOT mention about the vunlerability
within the patch (unless via the specialized security mailing list mentioned below).
If you also want to submit a security patch, which I appreciate your effort as a maintainer, please DO NOT mention about the vulnerability
within the patch (unless via these methods below).
### via email
@ -25,10 +31,19 @@ archives is limited to few trusted people alongside myself.
### as confidential GitLab merge request
When submitting a security-senstive patch in GitLab, don't forget to mark it as
When submitting a security-sensitive patch in GitLab, don't forget to mark it as
confidential merge request or request to access to security patches-only private fork.
[See GitLab Docs for details](https://docs.gitlab.com/ee/user/project/merge_requests/confidential.html).
### in GitHub private vulnerability reports
On projects with private vulnerability reporting enabled, after submitting your report,
you can push your patches to a private fork specific to that report.
## Notifying regarding data leaks
## See also
* [Encrypted Communications](../user-manual/encrypted-communications.md) for additional guidance