Re: [Burp-users] Windows client log file location?

[Michael K. <mh...@ko...>]

I'd just say that 'syslog' should fire to the windows event log on
Windows instead of doing nothing. That would make perfect sense, but
might well be annoying to implement (I no longer remember the details
of sending messages to the windows event logs - as I remember you just
had to setup your resources correctly and then it wasn't too bad? Not
sure.)

On Fri, Sep 4, 2015 at 5:02 PM, Larsen <lar...@we...> wrote:
> Perhaps there should be a config option "logfile" for Windows?
> I guess this would make it more intuitiv.
>
>
> Lars
>
>
> On Fri, 04 Sep 2015 16:38:37 +0200, Michael Kohne <mh...@ko...>
> wrote:
>
>> 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!
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Burp-users mailing list
> Bur...@li...
> https://lists.sourceforge.net/lists/listinfo/burp-users



-- 
Michael Kohne
mh...@ko...