Home / Security
Security
How to report a vulnerability in the ObliviOS source, what to expect, and the key to encrypt to.
Reporting a vulnerability
Open an issue, or send an email to beau.ten.berge@gmail.com. An issue is public: if you would rather the problem is not public before it is fixed, use the email. Plain text is fine; you can encrypt it with the PGP key below if you want to, but you do not have to.
Please include what is affected (file, patch or package), how to reproduce the problem, and the impact you expect.
The key
E694 4F84 B523 8F58 7493
Compare this fingerprint with the key before you encrypt to it. The public key is security-contact.asc, in every repository.
What to expect
- I reply within 3 days.
- I agree a disclosure date with you. There is no fixed time to a fix.
- I credit you in the fix unless you ask me not to.
- There is no bug bounty.
Scope
In scope: the patches, services and scripts in the ObliviOS repositories. ObliviOS is source only, so there is no build, image or update service to report on. A weakness that exists in upstream GrapheneOS or AOSP is better reported to those projects. Tell me as well if my patches make it worse.
Which sites are mine
Only oblivios.org, oblivios.dev and the four repositories on github.com/Beau4201 are mine. Do not trust any other site, app, account or package that uses the name ObliviOS. The contact and the key on this page are the only ones I use for reports.
security.txt
The same contact is served as /.well-known/security.txt (RFC 9116):
Contact: mailto:beau.ten.berge@gmail.com Expires: 2027-11-16T12:00:00Z Encryption: https://oblivios.org/security-contact.asc Preferred-Languages: en Canonical: https://oblivios.org/.well-known/security.txt Policy: https://oblivios.org/security