Re: [Burp-users] Niggle: Windows Burp 2.2.4 writes to Program Files folder

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

On Fri, Jun 15, 2018 at 09:50:56AM +0000, Iznohak via Burp-users wrote:
> I don't know if there are rules on this list for putting replies before or after a post. Let me know if I'm not well behaved so I can adjust.

Hello,

My preference is for bottom posting. (Thanks for asking! :))

> I noticed that your Windows installer detects when Burp is already installed, and in this case, it silently installs without prompting for all details of a first-time installation. Which is a very nice touch by the way, there are very few Windows installers that do this, most of them ask again and again the same stupid questions like "Do you want a desktop icon?", "Do you want to check for updates?", "Do you want to run the program now?"... at each fricking installation.
> 
> So I would suggest to leave existing installations alone and not update them to use the %PROGRAMDATA% scheme. Only new installations would be set up to use %PROGRAMDATA%. That would be simpler from an implementation point of view. However this would create a "fork" that could make tech support a bit more difficult. There is a choice to be made between either trade-off.

Yes.

> Regarding the different Windows versions, there is only one difference between Windows XP and all versions that came after. Vista to Windows 10, and all associated Server versions, use the same %PROGRAMDATA% folder (C:\ProgramData by default). So there is not a lot of complication here, if any, unless you want to continue supporting Windows XP in the future. That is of course your choice, but even Microsoft doesn't support it anymore, and hasn't been for a while. You could draw a line in the sand and decide that starting with Burp version 2.x, Windows XP is not supported, but older Burp versions are still available for Windows XP (e.g. 2.1.32).


I wouldn't want to deliberately break it. I wonder, does anybody on the mailing
list still use XP? I haven't heard it mentioned for a long time, until now.


> Can you disclose what installer product you use? Does it have a scripting capability?

Burp uses NSIS (Nullsoft Scriptable Install System).
You can find the code that burp uses inside of src/win32.