How to get back the 1 line verbosity like v1.5 #645

hang3r · 2023-02-12T06:15:01Z

Now it takes 3 lines for 1 result which to me is quite frustrating

joohoi · 2023-02-12T12:19:43Z

Hi, thanks for opening the issue. This is a bug in case you have no scrapers enabled. With no scrapers it should default to single-line output, but the check for it seems to be broken. However in the case you are using scrapers, the multi-line output is the only possible output format.

…

On Sun 12. Feb 2023 at 8.15, C4lputer ***@***.***> wrote: Now it takes 3 lines for 1 result which to me is quite frustrating [image: image] <https://user-images.githubusercontent.com/93414512/218296059-d04d2ac2-3ca8-41e5-845a-638f1e521b8e.png> — Reply to this email directly, view it on GitHub <#645>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABH6DJPYVFEP5IYVH26QIS3WXB5XDANCNFSM6AAAAAAUZD4RRY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

hang3r · 2023-02-12T14:05:03Z

ffuf -w /opt/SecLists/Discovery/Web-Content/raft-medium-directories-lowercase.txt -u "http://google.com/FUZZ"

I just fuzz like I always do, but when I update to version 2 this happened. So I supposed this is a bug and there will be a fix soon?
Thank you for the quick response.

riramar · 2023-02-14T13:24:10Z

Same problem here. AFAIK it's not possible to create filters like:

(HTTP code 400) OR (HTTP code 404) OR (HTTP code 301 AND Words 456)

So I was filtering out using egrep since the results were present in one line.
Now I'm getting 3 lines per result even with no scrapers.

dhtzs · 2023-02-16T21:26:33Z

I'm experiencing the same issue. Seems like ffuf 2.0 now takes 3 lines for a result without using scrapers, which is frustrating indeed. Thanks for your work!

vionde · 2023-02-17T16:57:30Z

Hope it will be fixed soon, but until that go install github.com/ffuf/ffuf@v1.5.0

Anyway, thanks for your work!

0xGreen · 2023-02-23T03:04:02Z

Hi there,

Fuzzing like i used to do (no -scrapers)

ffuf -u http://example.com -w wordlist.txt -H 'Host: FUZZ.example.com' -mc all -fw 1288

but the output is really weird, like 3 lines for 1 hit.

Just like @C4lputer, too much for me as well.

p0dalirius · 2023-03-03T19:01:53Z

Hi,

I've fixed the bug, proposed a pull request and wrote details on what was happening in #656

It now works awesomely on my end.

Best regards,

cardassian-tailor · 2023-03-17T01:00:00Z

Just wanted to say I also am having this issue and look forward to this being fixed. Thank you.

0xCGonzalo · 2023-03-24T15:59:43Z

Hi,

I've the same issue (previously updated the tool) at this date.

p0dalirius · 2023-03-24T16:03:14Z

Hi,

I've the same issue (previously updated the tool) at this date.

If you need, the issue is fixed in the not-yet-merged #656

Best regards,

0xCGonzalo · 2023-03-24T16:12:21Z

It's work.

Thank you sir Rémi, @p0dalirius.

0xdf223 · 2023-03-30T20:56:40Z

Yeah. This makes ffuf unusable for me. Would love to see it back in a compact line. Back to wfuzz until then.

HeckerBirb · 2023-03-31T21:05:49Z

The PR made by p0dalirius referenced here: #645 (comment) can be build locally by checking out their branch and following the steps for building from source.
Doing so will fix the problem described in here.

AkechiShiro · 2023-04-17T13:56:02Z

Given the nature of the issue and the PR fix that has been submitted, is this project a bit on hold/unmaintained right now ?

p0dalirius · 2023-04-17T14:25:53Z

Hey,

Any progress on this @tomikoski @joohoi ?

Best regards,

…645) (#656) * Fixed incorrect len() in pkg/output/stdout.go::PrintResult() * Fixed incorrect iteration on res.Input in pkg/output/stdout.go::prepareInputsOneLine(), Fixes #645 * Update CONTRIBUTORS.md * Update pkg/output/stdout.go --------- Co-authored-by: Joona Hoikkala <5235109+joohoi@users.noreply.github.com>

joohoi · 2023-04-21T14:25:17Z

This fix has now been merged. Thanks @p0dalirius !

Given the nature of the issue and the PR fix that has been submitted, is this project a bit on hold/unmaintained right now ?

Nope, but I've been very busy recently. Now back to it.

AkechiShiro · 2023-04-22T23:02:31Z

Thanks a lot @joohoi !

Maybe there should be a way for some serious/recurrent/trusted contributors to the project (after for instance 5/10/15 good PRs) that they could ask to be set as co-maintainers (or recommended by other users) in order to avoid this kind of situation, maybe @p0dalirius could want to have those rights since he fixed this bug pretty fast and he is maintaining quite a lot of tools on GitHub already, but I can't just speak for him like this, he might be very busy and not a right fit for that.

But it would be something to consider as an improvement for contributors/contributions, I'd guess !

HeckerBirb · 2023-04-23T07:41:17Z

I'd personally rather have to compile a pull request from sources rather than see random folks be allowed to simply merge changes to the main repo without vetting by the owner. This tool is primarily used by people who hack in one way or another. If all I takes is 15 good PRs before they can sneak in their own agenda.... 😂

AkechiShiro · 2023-04-23T18:51:04Z

Yeah you're not incorrect @HeckerBirb, then the hacker would need to have a provable record of being someone "ethical" in the community, but this was just an idea, it can be expanded, or there should be at least 2 others contributors who have 100 PRs merged in vouching for him. But I understand it's risky.

Policies can be thought of or we can look how does anyone join the security team for Debian/ArchLinux and so on ? If someone bad got into those team, hell could ensue has well.

p0dalirius mentioned this issue Mar 3, 2023

[Fix] Fixed multiline output when using only one fuzz variable (issue #645) #656

Merged

joohoi closed this as completed in #656 Apr 21, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

How to get back the 1 line verbosity like v1.5 #645

How to get back the 1 line verbosity like v1.5 #645

hang3r commented Feb 12, 2023

joohoi commented Feb 12, 2023 via email

hang3r commented Feb 12, 2023

riramar commented Feb 14, 2023

dhtzs commented Feb 16, 2023 •

edited

Loading

vionde commented Feb 17, 2023

0xGreen commented Feb 23, 2023

p0dalirius commented Mar 3, 2023

cardassian-tailor commented Mar 17, 2023

0xCGonzalo commented Mar 24, 2023 •

edited

Loading

p0dalirius commented Mar 24, 2023

0xCGonzalo commented Mar 24, 2023

0xdf223 commented Mar 30, 2023

HeckerBirb commented Mar 31, 2023

AkechiShiro commented Apr 17, 2023

p0dalirius commented Apr 17, 2023

joohoi commented Apr 21, 2023 •

edited

Loading

AkechiShiro commented Apr 22, 2023 •

edited

Loading

HeckerBirb commented Apr 23, 2023

AkechiShiro commented Apr 23, 2023 •

edited

Loading

How to get back the 1 line verbosity like v1.5 #645

How to get back the 1 line verbosity like v1.5 #645

Comments

hang3r commented Feb 12, 2023

joohoi commented Feb 12, 2023 via email

hang3r commented Feb 12, 2023

riramar commented Feb 14, 2023

dhtzs commented Feb 16, 2023 • edited Loading

vionde commented Feb 17, 2023

0xGreen commented Feb 23, 2023

p0dalirius commented Mar 3, 2023

cardassian-tailor commented Mar 17, 2023

0xCGonzalo commented Mar 24, 2023 • edited Loading

p0dalirius commented Mar 24, 2023

0xCGonzalo commented Mar 24, 2023

0xdf223 commented Mar 30, 2023

HeckerBirb commented Mar 31, 2023

AkechiShiro commented Apr 17, 2023

p0dalirius commented Apr 17, 2023

joohoi commented Apr 21, 2023 • edited Loading

AkechiShiro commented Apr 22, 2023 • edited Loading

HeckerBirb commented Apr 23, 2023

AkechiShiro commented Apr 23, 2023 • edited Loading

dhtzs commented Feb 16, 2023 •

edited

Loading

0xCGonzalo commented Mar 24, 2023 •

edited

Loading

joohoi commented Apr 21, 2023 •

edited

Loading

AkechiShiro commented Apr 22, 2023 •

edited

Loading

AkechiShiro commented Apr 23, 2023 •

edited

Loading