-
Notifications
You must be signed in to change notification settings - Fork 77
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
Can't pipe "burp -a S" output #870
Comments
hm, I haven't been able to reproduce the issue yet using the "same" setup:
Can you check that your |
Hi. I have Here's the whole
There's nothing extravagant in it. Thanks. |
Is burp the only tool affected by this situation? Can you try some dummy things like: Example: |
So no issues with other pipe commands. I tried the It's running in a LXC container (using Proxmox) maybe the buffering mode is already setup differently in it, I don't know. Thanks. |
Hello, How can I reproduce the issue? I have never used lxc/proxmox before. |
Hi. In case it's needed, I can spawn a clone of my burp server instance and give you SSH access to it. BTW, one of the clients is a Raspberry Pi 4 running Raspberry Pi OS (previously called Raspbian, based on Debian Buster) with burp 2.1.32 and I have the same issue as on LXC and the stdbuf magic also fixes the issue. Thanks. |
I'll try to find a moment during the weekend to find a way to reproduce the issue but if I fail, then I'd be interested by your offer to provide us a container to connect to. Of course if @grke prefers to have a look as he knows best the codebase then I'll leave it here. My feeling is we just need to force flush stdout at some point prior returning from the |
Hello, Burp uses fileno() to get stdout's file descriptor, then does the writes Maybe the containerisation somehow means that it needs an fsync instead? Maybe try 'fsync(*fd);' before the 'close(*fd);' in src/fsops.c:close_fd()? I will look to see if I can install lxc and try to reproduce. |
Thanks for the insights @grke I guess having access to your environment would speed things up if that's not a big deal for you @davromaniak |
I can spin up a clone of the my burp server instance, send me your SSH key on IRC and I'll do it over the next few days. Thanks. |
Hello, I've been toying with |
|
Hi.
I'm trying to send a daily status email using the output from "burp -a S" but I can't seem to be able to "pipe" it.
Here's the output of "burp -c /etc/burp/burp.conf -a S"
When I try to pipe the output to any other tool (even cat), there's nothing, like :
I discovered this issue when using the summary_script as it sends me an empty email.
I'm using burp 2.2.18 on Debian Buster (using Ziirish package repository).
Don't hesitate to ask me for any information needed.
Thanks.
The text was updated successfully, but these errors were encountered: