Change vhost used for pixel tracking

[fraf0]

Hi,

The tracking pixel is implemented on the pf vhost.

This have consequences :

• The logs are in 2 different places (/var/log/apache2 and /var/www/phishing-frenzy/log).
• The pixel tracking logs are not include in the "View raw Apache logs from campaign" and "download raw Apache logs form campaign".
• The pf vhost must be exposed to the victims (on internet).

I think it would be better if the pixel tracking land on the phsihing vhost.

Ps : I work on the docker image.

Regards,
fraf.

[Meatballs1]

I think I implemented this a while ago in fork:

https://github.com/pentestgeek/phishing-frenzy/compare/master...Meatballs1:redirect_to_parent?expand=1

[fraf0]

Thanks, I'll check this.

I'm not very easy with RubY/Ror/... :)
If I change code in dev mode, how it is taken in account ?
Idem in prod mode ?

Regards, fraf

[zeknox]

Changes made in dev mode are instantly noticed since each request is loaded from the file. Production mode requires a restart of the application server to see any changes. This is because production mode will load everything into memory as part of the initialization process.