Re: [Burp-users] autoupgrade not working
Brought to you by:
grke
|
From: Miha V. <ml...@kr...> - 2016-11-15 18:40:42
|
On 15. 11. 2016 01:20, Graham Keeling wrote: > On Tue, November 15, 2016 9:56 am, Miha VerliÄ wrote: >> Hello, >> >> I've noticed that some of the clients are not upgrading themselves. >> They're stuck at 2.0.48 even though I have 2.0.52 win64 binary and >> script located at /etc/burp/autoupgrade/server/win64/2.0.52/. >> >> According to log it seems server can't detect architecture of client - >> it matches to "toupg" which probably comes from autoupgrade, instead of >> "win64": >> >> burp[12240]: Want to autoupgrade client, but no file at: >> burp[12240]: /etc/burp/autoupgrade/server/toupg/script >> burp[12240]: or: >> burp[12240]: /etc/burp/autoupgrade/server/toupg/2.0.52/script >> >> I've noticed this in 2.0.52 changelog, so it may already be fixed: >> * Fix for client side autoupgrade. > > Hello, > > Yes, it is broken in 2.0.48 and earlier 2.0.x versions. > The fix means that you should be able to use it to go from 2.0.52 to > future versions. > This is unfortunate, but nobody spotted the bug until 2.0.50. Hello, not a big problem - since I only have 64bit clients, I just copied win64 dir to toupg and the clients fixed themselves :) -- Miha |