Re: [Burp-users] burp -a S needs a terminal for stdout (burp 2.0.54)
Brought to you by:
grke
Menu
▾
▴
Re: [Burp-users] burp -a S needs a terminal for stdout (burp 2.0.54)
|
From: Frans C. <coo...@gm...> - 2017-03-29 18:51:03
|
Hi. Thanks Pablo. I never setup the server as a client as well, in burp 1.x. I read it was changed, but the summary_script in burp 2.x still calls "burp -c /etc/burp/burp-server.conf -a S". I think this needs to be updated... I will test this tomorrow and also set the restore_client=<server cname> in burp-server.conf and then try to run "burp -a S" using the client. Regards, Frans On Wed, Mar 29, 2017 at 8:36 PM, Pablo Daniel Estigarribia Davyt < pab...@gm...> wrote: > Hello Frans, > > burp2 have changed the monitor, you need to use a client that connect with > status_port to burp status server. > > So new command line is: > > burp -c /etc/burp/burp.conf -a S > > The burp.conf is client config with status_port set. > > > El mié., 29 mar. 2017 a las 15:12, Frans Coomans (<coo...@gm...>) > escribió: > >> Hi. I have a similar issue with 2.0.54 on CentOS 7. >> >> Burp monitor displays absolutely nothing, when I run: >> # burp -c /etc/burp/burp-server.conf -a S >> >> I have no idea why this is happening. >> >> Is there a way to run burp in verbose mode to see why this is happening? >> >> Regards, >> Frans >> >> On Wed, Jan 18, 2017 at 10:56 PM, Tobias Brink <tob...@gm...> >> wrote: >> >> Hello! >> >> I upgraded to burp 2.0.54 and almost everything works well so far. The >> only thing I found was that I run >> >> burp -a S >> >> from a script to get a list of backups. >> >> This now fails without output and a return code of 1. This can be easily >> reproduced using the following in a bash shell: >> >> # (burp -a S ; echo $?) | cat >> 1 >> >> When stdout is not a pipe, it works: >> >> # burp -a S >> burp status 2017-01-18 21:50:18 >> >> XXXX idle last backup: 0000104 2017-01-17 19:51:00 >> ..... >> >> I'm on Debian jessie and compiled burp myself. I assume it may be >> connected to ncurses support, so here the summary for ./configure: >> >> configure: >> configure: Configuration summary >> configure: ===================== >> configure: >> configure: Host: x86_64-unknown-linux-gnu >> configure: Burp version: 2.0.54 >> configure: Install binaries: /opt/burp-2.0.54/sbin >> configure: Install config files: /etc/burp >> configure: C Compiler: gcc -std=gnu99 >> configure: Preprocessor flags: >> configure: Compiler flags: -Wall -g -O2 >> configure: Linker flags: >> configure: >> configure: acl: yes >> configure: crypt: yes >> configure: ipv6: yes >> configure: ncurses: yes >> configure: openssl: yes >> configure: xattr: yes >> configure: zlib: yes >> configure: >> >> >> And the version of ncurses: >> >> Package libncurses5-dev: 5.9+20140913-1+b1 >> >> >> Is that something weird in my setup (which does not seem too weird to >> me) or a bug in burp? Can somebody reproduce it? >> >> Thanks, >> >> Tobias >> >> ------------------------------------------------------------ >> ------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, SlashDot.org! http://sdm.link/slashdot >> _______________________________________________ >> Burp-users mailing list >> Bur...@li... >> https://lists.sourceforge.net/lists/listinfo/burp-users >> >> >> ------------------------------------------------------------ >> ------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot______ >> _________________________________________ >> Burp-users mailing list >> Bur...@li... >> https://lists.sourceforge.net/lists/listinfo/burp-users >> > -- > Pablo. > |
