这是indexloc提供的服务,不要输入任何密码
Skip to content

Add support for random user agents with each request #837

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

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

Crelic1
Copy link

@Crelic1 Crelic1 commented Mar 31, 2025

Description

Users may add a -random-agent flag followed by a wordlist containing user agents, FFUF will then pick a user agent at random for each request.
Will be over-ridden by -H "User-Agent: fizzbuzz"
Will revert the default FFUF User-Agent if the wordlist provided is empty.

Additonally

  • If this is the first time you are contributing to ffuf, add your name to CONTRIBUTORS.md. ✅
    The file should be alphabetically ordered. ✅
  • Add a short description of the fix to CHANGELOG.md ❌ - Sorry unsure how I should structure this

Thanks for contributing to ffuf :)

@Crelic1 Crelic1 marked this pull request as ready for review March 31, 2025 12:06
@Crelic1
Copy link
Author

Crelic1 commented Mar 31, 2025

New to Go and open-source. Please let me know if I am missing something.

Copy link

@ManU4kym ManU4kym left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

GetRandomLine function in pkg/ffuf/util.go

@Crelic1
Copy link
Author

Crelic1 commented May 22, 2025

GetRandomLine function in pkg/ffuf/util.go

Sorry, I'm not sure what you mean

@danielmotaleite
Copy link

why this? this is really just a black hacker feature!
Random user-agent is just to attack some site and trying to evade detection and block.
A valid white hacker scan will want a stable and known user-agent

We can stop people from using this tool with bad intentions, but we should not help them too.
My vote is not to merge this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants