Feature Request: BeEF Proxy Configuration File

[Meatballs1]

Poke @antisnatchor

It would be super helpful to have a template site configuration which uses mod_proxy to forward appropriate external requests to a BeEF server. Or template configuration to add to an existing site so that BeEF is served over the same domain/port etc.

I'm starting to look into this but not sure if theres any gotchas with BeEF that need sorting? Ideally would still want to hide /ui/panel, and I think it would break BeEFs access control for this (e.g. everything would appear to be from 127.0.0.1?).

[antisnatchor]

I'm already using mod_proxy with BeEF behind from at least 2 years.

See here: https://github.com/antisnatchor/phishing-frenzy/blob/master/app/views/campaigns/virtual_host_beefproxy.txt.erb (same for SSL). BeEF is on the same machine as PhishingFrenzy, configured with "public/public_port" settings in his own config.yaml.