-
Notifications
You must be signed in to change notification settings - Fork 412
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Introduce FAQ section into kernelCTF guidelines. (#133)
* 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 <poprdi@google.com> --------- Co-authored-by: Tamás Koczka <poprdi@google.com>
- Loading branch information
1 parent
aac27fb
commit c6972fc
Showing
2 changed files
with
8 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters