Hi Nilson,
I did not see your answer earlier since I was not subscribed to this bug
(I am now). I am sorry for that.
>> I also noticed that local changes in report_template.html are not
>> preserved on package upgrades as required by Debian Policy 10.7.3.
> To avoid mistaken corrections, could you clarify this point with a
> practical example?
Luckily Debian tooling comes to your help. dpkg will take care of it for
all files installed below /etc. Thus if you change sploitscan packaging
to install all configuration files under /etc/sploitscan, dpkg will do
the rest and make sure local changes are preserved on package upgrades.
You can find more information on this topic (including more complicated
situations) on [0].
>> . Looking at the sploitscan code [1], I suppose that the link
>> /usr/lib/python3/dist-packages/sploitscan/config.json ->
>> /etc/sploitscan/config.json
>> is not necessary (although I have not tested this).
>
> Will this answer your question?
> https://github.com/xaitax/SploitScan/issues/23
This confirms what I saw in the code.
If you have further questions, do not hesitate to ask.
Best regards,
Peter
[0] https://www.debian.org/doc/debian-policy/ap-pkg-conffiles.html
