Re: [Burp-users] Burp crashes on Windows Server 2008 x64

[Graham K. <ke...@sp...>]

On Wed, Mar 02, 2011 at 09:33:27PM +0100, Sebastiano Pilla wrote:
> You're gonna either laugh, or cry... First, 1.1.5 doesn't crash anymore
> on my Windows Server 2008 x64.
>
> I was still having a problem with the certificate, which was:
>
> 2011-03-02 20:41:21: bin\burp[3928] "G:/System Volume Information"
> 2011-03-02 20:41:21: bin\burp[3928] before client
> 2011-03-02 20:41:21: bin\burp[3928] begin client
> Can't read certificate file
> 2976:error:0200107B:system library:fopen:Unknown
> error:bss_file.c:356:fopen('"C:/Program
> Files/Burp/seba.home.lan.pem"','rb')
>
> 2976:error:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:358:
> 2976:error:140DC002:SSL
> routines:SSL_CTX_use_certificate_chain_file:system lib:ssl_rsa.c:722:
> 2011-03-02 20:41:22: bin\burp[3928] error initialising ssl ctx
> 2011-03-02 20:41:22: bin\burp[3928] after client
>
> It took me a while to realize that fopen() was trying to open a file
> whose name started and ended with a double quote character... As soon as
> I removed the quotes, putting
>
> ssl_cert_ca = C:/Program Files/Burp/ca.crt
> ssl_cert = C:/Program Files/Burp/seba.home.lan.pem
>
> in burp.conf, the certificate was read and the backup started.
>
> I was *so* convinced that I needed the double quotes when there are
> spaces in the file name, it looks like that at least for burp on Windows
> it is not the case.
>
> I was then having another double-quote moment in the include/exclude
> lines of the configuration file, it may be worth mentioning this point
> in the documentation for the future versions.
>
> Thank you very much for your help.
>
> Sebastiano Pilla

Excellent!
I will probably put a note in the FAQ part of the website.
Thanks for sticking with it, it has definitely been very useful.

If you have time or the inclination, I would much appreciate any of your
thoughts about new features, or ideas for improvements.