Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 7ace168

Browse files
committed
udpated images
1 parent b24ff87 commit 7ace168

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

docs/programs/retesting.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -11,17 +11,17 @@ To have hackers retest a vulnerability:
1111
1. Choose a resolved report in your inbox that you want to assign hackers to retest.
1212
2. Change the action picker to <b>Request retest</b>.
1313

14-
![choosing request retest in dropdown](./images/retesting-1.png)
14+
![choosing request retest in dropdown](./images/retest_update_6a.png)
1515

1616
3. Click <b>Request retest</b>.
1717

1818
![request retest button](./images/retesting-2.png)
1919

2020
2 random hackers with [HackerOne Clearance](/hackers/hackerone-clearance.html) participating in your program will be invited to retest the report through email.
2121

22-
![email to see retest invitation](./images/retesting-3b.png)
22+
![email to see retest invitation](./images/retesting_update_2.png)
2323

24-
In addition, the hacker that originally submitted the report will also be invited to participate in the retest, so that there will be a total of 3 retesters.
24+
In addition, the hacker that originally submitted the report will also be invited to participate in the retest, so that there will be a total of 3 retesters for your report.
2525

2626
![retest email for original hacker](./images/retesting-3c.png)
2727

@@ -31,13 +31,13 @@ When the hacker clicks <b>View retest invitation</b> in the email, they’ll be
3131

3232
Upon acceptance, participating hackers will be able to familiarize themselves with the vulnerability report and check to see that the vulnerability is properly fixed. After they’ve tested the vulnerability, they can click the <b>answer these questions</b> link in the report banner to submit their findings.
3333

34-
![answer these questions link in banner](./images/retesting-4.png)
34+
![answer these questions link in banner](./images/retesting_update_3.png)
3535

3636
The hacker will be asked to answer the following questions:
3737
* Are you able to reproduce the vulnerability?
3838
* Are you able to identify a bypass to the fix?
3939

40-
![retest questionnaire](./images/retesting-5c.png)
40+
![retest questionnaire](./images/retesting_update_1.png)
4141

4242
If they were able to identify a bypass, they can can submit a new vulnerability report and enter the report ID in the questionnaire.
4343

@@ -49,7 +49,7 @@ Hackers are also asked to provide a short summary of how they retested the vulne
4949

5050
Upon submission of the questionnaire, you’ll be notified that a hacker has completed a retest of your report within the report timeline and also through email.
5151

52-
![notification that hacker completed retest](./images/retesting-7.png)
52+
![notification that hacker completed retest](./images/retest_update_5.png)
5353

5454
Click on <b>View results</b> to see the status and findings of the retest efforts. If the hacker was able to find a bypass to the vulnerability, you can view the new vulnerability report.
5555

0 commit comments

Comments
 (0)