|
@@ -9,26 +9,11 @@
|
|
|
|
|
|
## Reporting a Vulnerability
|
|
|
|
|
|
-If you have found a potential security threat, vulnerability or exploit in Quasar
|
|
|
+If you have found a potential security threat, vulnerability or exploit in Tauri
|
|
|
or one of its upstream dependencies, please DON’T create a pull-request, DON’T
|
|
|
file an issue on GitHub, DON’T mention it on Discord and DON’T create a forum thread.
|
|
|
|
|
|
-DO reach out to the team by sending an email to **security@quasar.dev** - we
|
|
|
-will investigate and work with you to triage this issue and help you to report it
|
|
|
-if appropriate.
|
|
|
+We will be adding contact information to this page very soon.
|
|
|
|
|
|
-If you like, you may use PGP to encrypt your messages, as the public key has been published at the pgp.mit.edu keyserver.
|
|
|
-
|
|
|
-At the current time we do not have the financial ability to reward bounties, but in extreme cases will at our discretion consider a reward.
|
|
|
-
|
|
|
-## Security Audit
|
|
|
-
|
|
|
-You can apply to book the Quasar team’s security experts to perform a Security Audit
|
|
|
-for your project. Contact us to find out more about how to acquire, validate and publish
|
|
|
-an official timestamped and version-locked audit badge.
|
|
|
-
|
|
|
-`security@quasar.dev`
|
|
|
-
|
|
|
-## Security Documentation
|
|
|
-
|
|
|
-https://quasar.dev/security/
|
|
|
+At the current time we do not have the financial ability to reward bounties,
|
|
|
+but in extreme cases will at our discretion consider a reward.
|