Re: [Burp-users] Windows client log file location?
Brought to you by:
grke
|
From: Michael K. <mh...@ko...> - 2015-09-04 14:38:45
|
OK, so basically the answer is 'nowhere', so it's not that I'm missing anything. I poked around a little, and redirection of scheduled task output is ever so slightly non-obvious on windows. I found a discussion here: http://richarddingwall.name/2009/01/26/capture-the-output-from-a-scheduled-task/ What I ended up with was "C:\Windows\system32\cmd.exe" /C "C:\Program Files\Burp\bin\burp.exe" -a t > C:\burpclient.log 2>&1 Note that when entering this into the Windows Task Scheduler GUI, you put "C:\Windows\system32\cmd.exe" as the program and all the rest as the arguments. It works fine, and it'll be perfect for debugging problems in the future. Thanks all! On Fri, Sep 4, 2015 at 9:41 AM, Peter Maloney <pet...@br...> wrote: > On 09/04/2015 03:32 PM, Ziirish wrote: >> * On Friday, 04 September 2015 15:22, Michael Kohne <mh...@ko...> wrote: >>> I've got burp running, and the backups are working on a fully >>> automatic basis. I wanted to look at the log files on the client, and >>> I can't seem to find them anywhere. I'm probably missing something >>> obvious, but could someone point me in the right direction? >>> >>> In my burp.conf on the client (Windows 7, x64), I've got the following lines: >>> stdout = 1 >>> syslog = 1 >>> >>> I checked all around the burp directory and the only log I see is the >>> installation log. >>> >>> I looked in event viewer and can't see anything there. >>> There's no 'Burp' directory under c:\ProgramData. >>> >>> So where (if anywhere) do the log files go? >> Hi, >> >> I don't think syslog is available on Windows so only stdout will be effective. >> I think Windows is able to handle redirections so you could try editing the >> scheduled task that runs burp and add this at the end of the command: >> >> ">C:\Burp.log" >> >> (you can of course choose another path if you prefer) >> >> P.S.: I am absolutely not a windows specialist so I may be totally wrong. >> > If syslog=1 was implemented on windows, you'd expect to find it in the > system event viewer. > > Also, if the client doesn't crash too early, you can find the server > side client log in the backup directory. (different from the server log) > > ------------------------------------------------------------------------------ > _______________________________________________ > Burp-users mailing list > Bur...@li... > https://lists.sourceforge.net/lists/listinfo/burp-users -- Michael Kohne mh...@ko... |