Skip to content
This repository was archived by the owner on Nov 28, 2022. It is now read-only.
This repository was archived by the owner on Nov 28, 2022. It is now read-only.

searchsploit informational messages should be sent to stderr #131

Closed
Closed
searchsploit informational messages should be sent to stderr#131
Assignees
g0tmi1k
Labels
bug
@gcmurphy

Description

@gcmurphy
gcmurphy
opened on Apr 2, 2019

When running searchsploit against nmap output the json output is not really useful / usable because it is mixed in with info messages below even with redirect to 2>/dev/null.

▶ searchsploit --nmap portscan.xml --json 2>/dev/null | egrep  '^\[i\]'  
[i] SearchSploit's XML mode (without verbose enabled).   To enable: searchsploit -v --xml...
[i] Reading: 'portscan.xml'

Would be nice if you could pipe the output to jq or redirect to json file etc.

Activity

gcmurphy

gcmurphy commented on Apr 2, 2019

@gcmurphy
gcmurphy
on Apr 2, 2019
Author

fwiw a workaround is:

searchsploit --nmap portscan.xml --json 2>/dev/null| egrep -v '^\[i\]' | sed -e 's/^\}$/\},/'  | tr -d '\n' | sed -e 's/^/[/' -e 's/,$/]/' | jq```
gcmurphy
changed the title Information messages should be sent to stderr? searchsploit informational messages should be sent to stderr on Apr 2, 2019
g0tmi1k
self-assigned this
on Apr 2, 2019
g0tmi1k
added
bug
on Apr 2, 2019
g0tmi1k
mentioned this on Apr 3, 2019
g0tmi1k
closed this as completedin #132on Apr 3, 2019
g0tmi1k

g0tmi1k commented on Apr 3, 2019

@g0tmi1k
g0tmi1k
on Apr 3, 2019
Collaborator

Solution is in place now.
Please update and try again!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bug

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions
    searchsploit informational messages should be sent to stderr · Issue #131 · offensive-security/exploitdb