mandiant/flare-fakenet-ng

More flexibility in HTTP CustomResponse criteria

Open

#148 opened on Oct 2, 2021

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Python (359 forks)batch import
featuregood first issue

Repository metrics

Stars
 (1,626 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Software that calls out with varying/random/non-RFC compliant host headers and/or URIs can be difficult to control with the HTTP CustomResponse feature.

It would be nice to be able to enable custom responses unconditionally, or to be able to use wildcards or regex in the host or URI specifications to achieve a similar result.

Contributor guide

Research direction
Examine the current HTTP CustomResponse implementation in FakeNet NG's source code, understand how host and URI matching works, and design a solution that allows unconditional responses or regex matching.
Tech stack
python
Domain
security
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Python
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65