mirror of https://github.com/pbatard/rufus.git
Browse Source
[misc] Fix issue template no longer being processed
[misc] Fix issue template no longer being processed
* Since GitHub broke existing paths and did not bother to alert people. * Closes #2672.pull/2675/head

No known key found for this signature in database
GPG Key ID: 38E0CF5E69EDD671
8 changed files with 73 additions and 57 deletions
-
1.github/ISSUE_TEMPLATE/config.yml
-
105.github/ISSUE_TEMPLATE/issue-report.md
-
1.github/workflows/codeql.yml
-
1.github/workflows/coverity.yml
-
1.github/workflows/mingw.yml
-
1.github/workflows/vs2022.yml
-
10SECURITY.md
-
10src/rufus.rc
@ -0,0 +1 @@ |
|||
blank_issues_enabled: false |
@ -1,48 +1,57 @@ |
|||
<!-- |
|||
PLEASE READ THIS CAREFULLY: |
|||
|
|||
1. You *MUST* read and complete the steps from the checklist below, by placing |
|||
an x into each [ ] (so that it shows '[x]', NOT '[ x]' or '[x ]'), BEFORE |
|||
clicking on 'Submit new issue'. |
|||
|
|||
2. Failure to perform these steps, WHICH ARE ONLY THERE TO HELP *YOU*, will |
|||
usually result in your issue being dismissed without notice. |
|||
|
|||
3. If you are reporting an issue when trying to run Rufus, or when trying to |
|||
boot a media created by Rufus, you *MUST* provide a log, period. Please do |
|||
not assume that the developer(s) will be able to "guess" the specifics of |
|||
your environment, what image you used, what type of media you used it with |
|||
or the many many other critical parameters that the log provides data for. |
|||
To investigate an issue, a log from Rufus is ALWAYS required. |
|||
|
|||
4. If you still *choose* not to provide a log when reporting a problem, you |
|||
agree that your issue will be closed without any further investigation. |
|||
|
|||
YOU HAVE BEEN WARNED. |
|||
--> |
|||
|
|||
Checklist |
|||
--------- |
|||
- [ ] I have been made aware that if my problem can be summarized as _"I've created or tried to create a media using Rufus, and ..."_, and I am not including a log, **this issue will be summarily closed**. |
|||
- [ ] I looked at https://github.com/pbatard/rufus/wiki/FAQ to see if my question has already been answered. |
|||
- [ ] I performed a search in the issue tracker for similar issues using keywords relevant to my problem, such as the error message I got from the log. |
|||
- [ ] I clicked the 'Log' button (🗒️) or pressed <kbd>Ctrl</kbd>-<kbd>L</kbd> in Rufus, or used [DebugView](https://learn.microsoft.com/en-us/sysinternals/downloads/debugview), and copy/pasted the log into the section that says `<FULL LOG>` below. |
|||
- [ ] The log I am copying is the FULL log, starting with the line `Rufus version: x.y.z` - I have NOT removed any part of it. |
|||
|
|||
Additionally (if applicable): |
|||
- [ ] I ran a bad blocks check, by clicking _Show advanced format options_ then _Check device for bad blocks_, and confirmed that my USB is not defective. |
|||
- [ ] I also tried one or more of the following: |
|||
- [ ] Using a different USB drive. |
|||
- [ ] Plugging the USB into a different port. |
|||
- [ ] Running Rufus on a different computer. |
|||
- [ ] If using an image, I clicked on the `(✓)` button to compute the MD5, SHA1 and SHA256 checksums, which are therefore present in the log I copied. I confirmed, by performing an internet search, that these values match the ones from the official image. |
|||
|
|||
Issue description |
|||
----------------- |
|||
<Please describe your issue here> |
|||
|
|||
Log |
|||
--- |
|||
``` |
|||
<FULL LOG> |
|||
``` |
|||
--- |
|||
name: Report an issue with the application |
|||
about: Please make sure you follow the check-list carefully! |
|||
title: '' |
|||
labels: '' |
|||
assignees: '' |
|||
|
|||
--- |
|||
|
|||
<!-- |
|||
PLEASE READ THIS CAREFULLY: |
|||
|
|||
1. You *MUST* read and complete the steps from the checklist below, by placing |
|||
an x into each [ ] (so that it shows '[x]', NOT '[ x]' or '[x ]'), BEFORE |
|||
clicking on 'Submit new issue'. |
|||
|
|||
2. Failure to perform these steps, WHICH ARE ONLY THERE TO HELP *YOU*, will |
|||
usually result in your issue being dismissed without notice. |
|||
|
|||
3. If you are reporting an issue when trying to run Rufus, or when trying to |
|||
boot a media created by Rufus, you *MUST* provide a log, period. Please do |
|||
not assume that the developer(s) will be able to "guess" the specifics of |
|||
your environment, what image you used, what type of media you used it with |
|||
or the many many other critical parameters that the log provides data for. |
|||
To investigate an issue, a log from Rufus is ALWAYS required. |
|||
|
|||
4. If you still *choose* not to provide a log when reporting a problem, you |
|||
agree that your issue will be closed without any further investigation. |
|||
|
|||
YOU HAVE BEEN WARNED. |
|||
--> |
|||
|
|||
Checklist |
|||
--------- |
|||
- [ ] I have been made aware that if my problem can be summarized as _"I've created or tried to create a media using Rufus, and ..."_, and I am not including a log, **this issue will be summarily closed**. |
|||
- [ ] I looked at https://github.com/pbatard/rufus/wiki/FAQ to see if my question has already been answered. |
|||
- [ ] I performed a search in the issue tracker for similar issues using keywords relevant to my problem, such as the error message I got from the log. |
|||
- [ ] I clicked the 'Log' button (🗒️) or pressed <kbd>Ctrl</kbd>-<kbd>L</kbd> in Rufus, or used [DebugView](https://learn.microsoft.com/en-us/sysinternals/downloads/debugview), and copy/pasted the log into the section that says `<FULL LOG>` below. |
|||
- [ ] The log I am copying is the FULL log, starting with the line `Rufus version: x.y.z` - I have NOT removed any part of it. |
|||
|
|||
Additionally (if applicable): |
|||
- [ ] I ran a bad blocks check, by clicking _Show advanced format options_ then _Check device for bad blocks_, and confirmed that my USB is not defective. |
|||
- [ ] I also tried one or more of the following: |
|||
- [ ] Using a different USB drive. |
|||
- [ ] Plugging the USB into a different port. |
|||
- [ ] Running Rufus on a different computer. |
|||
- [ ] If using an image, I clicked on the `(✓)` button to compute the MD5, SHA1 and SHA256 checksums, which are therefore present in the log I copied. I confirmed, by performing an internet search, that these values match the ones from the official image. |
|||
|
|||
Issue description |
|||
----------------- |
|||
<Please describe your issue here> |
|||
|
|||
Log |
|||
--- |
|||
``` |
|||
<FULL LOG> |
|||
``` |
@ -1,7 +1,9 @@ |
|||
# Reporting a Vulnerability |
|||
# Reporting a security vulnerability |
|||
|
|||
To report a vulnerability for Rufus, please e-mail support@akeo.ie. |
|||
To report a **security** vulnerability for Rufus (i.e. an issue that you believe could lead to malicious actors being able to exploit the Rufus application), please e-mail support@akeo.ie. |
|||
|
|||
If you find a vulnerability, we will ask you to respect [responsible disclosure](https://en.wikipedia.org/wiki/Responsible_disclosure) practices. |
|||
Please do **NOT** use the e-mail above if you have a regular issue, such as a problem creating or using a bootable drive. Instead go back to https://github.com/pbatard/rufus/issues and create an issue using the regular *Issue Report* template. |
|||
|
|||
In return, we will endeavour to respond to vulnerability reports within 48 hours. |
|||
For any security vulnerability report, we kindly ask you to respect [responsible disclosure](https://en.wikipedia.org/wiki/Responsible_disclosure) practices. |
|||
|
|||
In return, we will endeavour to respond to security vulnerability reports within 48 hours. |
Write
Preview
Loading…
Cancel
Save
Reference in new issue