From c6972fc46b1a25b8d823f41ec44b8010178c05bc Mon Sep 17 00:00:00 2001 From: artmetla <77324544+artmetla@users.noreply.github.com> Date: Thu, 26 Sep 2024 12:50:02 +0200 Subject: [PATCH] Introduce FAQ section into kernelCTF guidelines. (#133) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * Introduce FAQ section into kernelCTF guidelines. Add FAQ section to guidelines and provide answer to the first question. * Apply suggestions from code review Co-authored-by: Tamás Koczka --------- Co-authored-by: Tamás Koczka --- kernelctf/faq.md | 5 +++++ kernelctf/rules.md | 4 +++- 2 files changed, 8 insertions(+), 1 deletion(-) create mode 100644 kernelctf/faq.md diff --git a/kernelctf/faq.md b/kernelctf/faq.md new file mode 100644 index 000000000..0865aa6ea --- /dev/null +++ b/kernelctf/faq.md @@ -0,0 +1,5 @@ +# Frequently Asked Questions (FAQ) + +#### 1. I submitted one report to [bughunters.google.com](https://bughunters.google.com/) containing multiple exploits. I noticed that some of the associated pull requests have been merged, and I received a payment notification email from kernelCTF awarding only partial rewards (not for all submitted exploits). When will I receive all the bounties? + +The above described situation means that at this moment only some of the exploits have been reviewed, the rest of exploits associated with the report remain in the review queue. We are doing everything possible to prioritize review of similar submissions and bundle them together, but sometimes we still need more time to make a decision on all the exploits provided. Please stay tuned for the updates on the remaining pull requests. As soon as other pull requests are merged the subsequent bounties will also be issued. diff --git a/kernelctf/rules.md b/kernelctf/rules.md index f02cc401a..2693b741c 100644 --- a/kernelctf/rules.md +++ b/kernelctf/rules.md @@ -387,7 +387,9 @@ If possible, also include how stable your exploit is (e.g. it worked 90% of the We announce major program changes on [Google's Security Blog](https://security.googleblog.com/), but we may change minor, mostly technical details (like steps in the submission process) by changing this page and announcing the change on our [#kernelctf-announcements](https://discord.gg/yXue2RwDEA) Discord channel. -If you have any question regarding kernelCTF, feel free to ask on the [#kernelctf](https://discord.gg/ECS5VnJZys) Discord channel. +## Questions about program + +If you have any questions regarding kernelCTF, check [the FAQ page](faq.md) and feel free to ask on the [#kernelctf](https://discord.gg/ECS5VnJZys) Discord channel. ## Non-kernel vulnerabilities