-
Notifications
You must be signed in to change notification settings - Fork 235
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
Cannot use -S enable_report=NO in write protected directory #242
Comments
Neat. Have you tried running under a debugger to get the stack trace?
…----
Sent from my phone.
On Apr 22, 2021, at 5:48 AM, erik4711 ***@***.***> wrote:
I sometimes read capture files from write protected media and pipe the output to grep in order to look for specific content. I'd like to use -S enable_report=NO since I'm not interested in getting a report.xml file and because the XML file cannot be written to the write protected media anyway. However, unfortunately tcpflow crashes when issuing -S enable_report=NO from a write protected directory. See output below:
/media/readonly$ tcpflow -v -S enable_report=NO -r evidence.pcap -c > /dev/null
tcpflow[12940]: printing packets to console only
tcpflow: TCPFLOW version 1.4.5
terminate called after throwing an instance of 'std::invalid_argument*'
Aborted (core dumped)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Here's the tail from strace's output:
|
That's great. If you can compile it with debug symbols, we will get a full stack trace. Without it, it looks like the problem is coming from here: tcpflow/src/be13_api/feature_recorder_set.cpp Lines 50 to 53 in 04b0dab
Can you try running with |
Yes changing output dir to a writeable one with It would also make sense setting |
You have disabled the report, but you have not disabled the output of the feature recorders. It seems that you want to disable all output except what goes to stdout. That will require code modification to how the feature recorders work.
… On Apr 22, 2021, at 7:52 AM, erik4711 ***@***.***> wrote:
Yes changing output dir to a writeable one with -o resolves the problem.
Would it be possible to avoid throwing that exception when -c or -C is used together with -S enable_report=NO, since nothing will be written to disk in these cases?
It would also make sense for setting -S enable_report to NO by default when -c or -C is used (feature request).
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#242 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAMFHLBKC5DGCIJXTXW7QJTTKAEYHANCNFSM43MDEAMQ>.
|
Okay, thanks. I understand. |
I sometimes read capture files from write protected media and pipe the output to grep in order to look for specific content. I'd like to use
-S enable_report=NO
since I'm not interested in getting a report.xml file and because the XML file cannot be written to the write protected media anyway. However, unfortunately tcpflow crashes when issuing-S enable_report=NO
from a write protected directory. See output below:The text was updated successfully, but these errors were encountered: