16e14c6f2e
* updated version to 5.0.1.0 in package.json * updated version to 5.0.1.0 in VERSION * updated version to 5.0.1.0 in config.yml * removed Active Record section * cleanup bundle related folders and added to .gitignore * bumped tag url in ISSUETEMPLATE * updating version to 0.5.1.0 * readding .bundle/config as we do not want users to automatically install dev/test gems * fixed spelling mistake of .bundle
2.2 KiB
Submit Issue
Verify first that your issue/request has not been posted previously:
Ensure you're using the latest version of BeEF.
Please do your best to provide as much information as possible. It will help substantially if you can enable and provide debugging logs with your issue. Instructions for enabling debugging logs are below:
- In the
config.yamlfile of your BeEF root folder set debug and client_debug (lines 11 & 13 respectively) totrue- If using a standard installation of
beef-xssthe root folder will typically be/usr/share/beef-xss
- If using a standard installation of
- Reproduce your error
- Retrieve your client-side logs from your browser's developer console (Ctrl + Shift + I)
- Retrieve your server-side logs from
~/.beef/beef.log - If using
beef-xss: Retrieve your service logs usingjournalctl -u beef-xss
Thank you, this will greatly aid us in identifying the root cause of your issue :)
If we request additional information and we don't hear back from you within a week, we will be closing the ticket off. Feel free to open it back up if you continue to have issues.
Summary
Q: Please provide a brief summary of the issue that you experienced. A:
Environment
Please identify the environment in which your issue occurred.
-
BeEF Version:
-
Ruby Version:
-
Browser Details (e.g. Chrome v81.0):
-
Operating System (e.g. OSX Catalina):
Configuration
Q: Have you made any changes to your BeEF configuration? A:
Q: Have you enabled or disabled any BeEF extensions? A:
Expected vs. Actual Behaviour
Expected Behaviour:
Actual Behaviour:
Steps to Reproduce
Please provide steps to reproduce this issue.
Additional Information
Please provide any additional information which may be useful in resolving this issue, such as debugging output and relevant screen shots. Debug output can be retrieved by following the instructions towards the top of the issue template.