install burp-2.2.18 via package ("pkg install burp"). Edit /usr/local/etc/burp/burp*.conf to suit your needs.
Reinstalling or updating burp will overwrite usr/local/etc/burp*.conf with defaults, without warning, without creating backups.
Expected behaviour: package installs only burp.conf.sample and burp-server.conf.sample and leaves burp.conf and burp-server.conf as is.
Workaround: save .conf files before updating, or reference own .conf files in /etc/rc.conf and crontab jobs.
(In reply to Benedikt Hochstrasser from comment #0)
Thanks for reporting! I will fix it as soon as possible.
I could not reproduce your issue.
The problem was indeed present before, but it should have been fixed with https://svnweb.freebsd.org/ports?view=revision&revision=530237 i.e. since 2.2.18_3.
Is it possible that you were updating from a version earlier than 2.2.18_3 to version 2.2.18_3 or 2.2.18_4? Can you please repeat your test removing and installing burp-2.2.18_3 or burp-2.2.18_4? Or updating from 2.2.18_3 to 2.2.18_4? Whichever is easier for you is fine.
(In reply to Lorenzo Salvadore from comment #2)
2.2.18_4 (off the 'latest' branch) is fine. Thing is, my system by default went to 'quarterly' where we're still on 2.2.18_2.
So everything is ok. You may close the case.
A commit references this bug:
Date: Mon May 4 19:21:56 UTC 2020
New revision: 533970
sysutils/burp-devel: Update to 2.3.24
- Protocol 2: warn and skip on verify/restore of unsupported file types.
- Resurrect, improve and use sysutils/burp/files/burp.in instead of the rc
script from distfile, both for sysutils/burp (master port) and for
sysutils/burp-devel (slave port): this is necessary because, while
sysutils/burp's distfile still distributes the script, sysutils/burp-devel's
distfile does not anymore starting with version 2.3.24. I also made a few
modifications to the file so that it behaves well with non standard PREFIX
- Fix bug #246062.
Reviewed by: 0mp, gerald, dbaio, adamw
Approved by: tcberner (co-mentor)
Differential Revision: https://reviews.freebsd.org/D24104
Reported by: email@example.com
Approved by: ports-secteam (joneum), gerald (mentor)
It is now fixed in the quarterly branch as well.
Thanks for reporting!