|
3 | 3 | Thanks for your interest in making Metasploit -- and therefore, the
|
4 | 4 | world -- a better place!
|
5 | 5 |
|
6 |
| -Are you about to report a bug? If so, please use our [Redmine Bug |
7 |
| -Tracker](https://dev.metasploit.com/redmine/projects/framework). An |
8 |
| -account is required but it only takes a minute or two. |
| 6 | +Are you about to report a bug? Sorry to hear it. |
9 | 7 |
|
10 |
| -Are you about to report a security vulnerability in Metasploit? |
11 |
| -If so, please take a look at Rapid's [Vulnerability |
12 |
| -Disclosure Policy](https://www.rapid7.com/disclosure.jsp) policy. |
| 8 | +Here's our [Issue tracker](https://github.com/rapid7/metasploit-framework/issues). |
| 9 | +Please try to be as specific as you can about your problem, include steps |
| 10 | +to reproduce (cut and paste from your console output if it's helpful), and |
| 11 | +what you were expecting to happen. |
| 12 | + |
| 13 | +Are you about to report a security vulnerability in Metasploit itself? |
| 14 | +How ironic! Please take a look at Rapid7's [Vulnerability |
| 15 | +Disclosure Policy](https://www.rapid7.com/disclosure.jsp), and send |
| 16 | +your report to [email protected] using [our PGP key ](http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x2380F85B8AD4DB8D). |
13 | 17 |
|
14 | 18 | Are you about to contribute some new functionality, a bug fix, or a new
|
15 | 19 | Metasploit module? If so, read on...
|
@@ -64,18 +68,14 @@ Pull requests [#2940](https://github.com/rapid7/metasploit-framework/pull/2940)
|
64 | 68 | #### Bug Fixes
|
65 | 69 |
|
66 | 70 | * **Do** include reproduction steps in the form of verification steps.
|
67 |
| -* **Do** include a link to the corresponding [Redmine](https://dev.metasploit.com/redmine/projects/framework) issue in the format of `SeeRM #1234` in your commit description. |
| 71 | +* **Do** include a link to any corresponding [Issue](https://github.com/rapid7/metasploit-framework/issues) in the format of `See #1234` in your commit description. |
68 | 72 |
|
69 | 73 | ## Bug Reports
|
70 | 74 |
|
71 | 75 | * **Do ** report vulnerabilities in Rapid7 software directly to [email protected].
|
72 |
| -* **Do** create a Redmine account and report your non-vulnerability bugs there. |
73 | 76 | * **Do** write a detailed description of your bug and use a descriptive title.
|
74 | 77 | * **Do** include reproduction steps, stack traces, and anything else that might help us verify and fix your bug.
|
75 | 78 | * **Don't** file duplicate reports - search for your bug before filing a new report.
|
76 |
| -* **Don't** report a bug on GitHub. Use [Redmine](https://dev.metasploit.com/redmine/projects/framework) instead. |
77 |
| - |
78 |
| -Redmine issues [#8762](https://dev.metasploit.com/redmine/issues/8762) and [#8764](https://dev.metasploit.com/redmine/issues/8764) are a couple good examples to follow. |
79 | 79 |
|
80 | 80 | If you need some more guidance, talk to the main body of open
|
81 | 81 | source contributors over on the [Freenode IRC channel](http://webchat.freenode.net/?channels=%23metasploit&uio=d4)
|
|
0 commit comments