-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Beef On Repl It #2717
Comments
Replit cannot run Beef, and this (presumptively) is also against replits terms of service. You can remove the sudo command from the install file, but afaik you cannot obtain most apt packages anyway. You also cannot obtain sudo on replit, as it is disallowed. |
Replit itself is a powerful docker container, could we use this to our advantage to run beef? |
You could try? BeEF is a HTTP(S) server. So long as you have a working Ruby environment and a network connection you should be able to use BeEF. You'll also need nodejs and a handful of system packages such as sqlite. |
@wendellmeset Did you get BeEF working on Replit? |
No not yet |
I found a replit that emulates a linux terminal with sudo however storage is full, so it may be possible wit ha premium repl subscripbtion! |
I was able to get beef working on replit. However, I still working out a few of the bugs right now. |
This issue as been marked as stale due to inactivity and will be closed in 7 days |
Can you link the replit project? |
You don't need sudo. To install:
To decrease network traffic and server load, it would be polite to increase the XHR poll duration: Line 46 in 173d800
You're done. Change the Run command to There is ample storage (1GB) to get a default install running. BeEF only needs about 30MB + database contents over time. |
This comment was marked as off-topic.
This comment was marked as off-topic.
Using Replit for anything other than testing and developing would most likely be against the terms of service. Closing. |
First Steps
Configuration
Steps to Reproduce
How to enable and capture detailed logging
config.yaml
in the root directory/usr/share/beef-xss
client_debug
totrue
~/.beef/beef.log
journalctl -u beef-xss
If we request additional information and we don't hear back from you within a week, we will be closing the ticket off.
The text was updated successfully, but these errors were encountered: