Feature: Phishlet-Specific redirect URL #932
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added parameter redirect_url to the Phishlets model. Added configuration to the ConfigPhishlet struct.
Added check for Phishlet redirect_url parameter in the blockRequest function. The redirect_url defined in the phishlet configuration file will supersede the global redirect_url parameter.
Added redirect_url parameter to the example phishlet yaml config file.
…et url override logic in the http_proxy/blockRequests
fixed URL
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This feature adds the ability to define phishlet-specific redirect URLs in the phishlet's .yaml file.
If a phishlet-specific redirect URL is available for the current request's host it will supersede the global redirect URL.
Redirect URLs continue to work as normal otherwise.
When running multiple campaigns or phishlets it may be useful to have the ability to present different redirect pages for unauthorized requests. Presenting different redirect_url pages may help with limiting the association of the redirect_url page for one phishlet with the overall campaign.
This feature was built into the core/http_proxy.go/blockRequest() function as to modify as little as possible.
The core/phishlets.go file was modified to accept a new variable from the phishlet .yaml configuration.
The phishlets/example.yaml was also modified to include "https://example.com" as the example for the redirect_url parameter.
Linked to feature request #915
Test Cases: