Re: [Burp-users] First new client after upgrade to 2.0.52

[Graham K. <gr...@gr...>]

On Thu, Nov 10, 2016 at 07:32:47AM +0000, Brian Hickey wrote:
> I've noticed this too on an install that had been upgraded from 1.4.40 
> to 2.0.46 (and which is now at 2.0.52). When I create a new client, it 
> doesn't work  the first time I run 'burp -a b'. To workaround, I delete 
> the .crt and .csr files on the server for the new client in /etc/burp/CA 
> and then 'burp -a b' runs okay the next time and scheduled backups run 
> fine too for the new client. All original backups have continued to run 
> fine after the upgrade, so this behaviour is only noticed for new 
> clients created since the upgrade.
> 
> One thing I noticed is that the permissions and date for .csr files for 
> any new client are different than they used to be when the client first 
> connected to 1.4.x :
> 
> 2.0.52 client :
> 
> -rw-r--r-- 1 root root 3683 Nov 10 06:48 Client02.crt
> ---------- 1 root root  891 Jan  1  1970 Client02.csr
> 
> 1.4.x client :
> 
> -rw-r--r-- 1 root root 3690 Jul 15 06:47 Client01.crt
> -rw-r--r-- 1 root root  895 Jul 15 06:47 Client0.csr

Hello,

I tried starting from 1.4.40, going to 2.0.52, and adding a new client.
I didn't have any problem - it worked fine for me.

But I did see the same permissions oddity as you.
After some investigation, I now know what causes it.

https://github.com/grke/burp/issues/512

I don't think this needs to be fixed for the stable release.