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

searchsploit informational messages should be sent to stderr #131

Closed
gcmurphy opened this issue Apr 2, 2019 · 2 comments
Closed

searchsploit informational messages should be sent to stderr #131

gcmurphy opened this issue Apr 2, 2019 · 2 comments
Assignees
Labels

Comments

@gcmurphy
Copy link

gcmurphy commented 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.

@gcmurphy
Copy link
Author

gcmurphy commented Apr 2, 2019

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 gcmurphy changed the title Information messages should be sent to stderr? searchsploit informational messages should be sent to stderr Apr 2, 2019
@g0tmi1k g0tmi1k self-assigned this Apr 2, 2019
@g0tmi1k g0tmi1k added the bug label Apr 2, 2019
@g0tmi1k g0tmi1k mentioned this issue Apr 3, 2019
@g0tmi1k
Copy link
Collaborator

g0tmi1k commented Apr 3, 2019

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

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

No branches or pull requests

2 participants