Bug#972573: RFP: crowdsec -- lightweight agent to detect and respond to bad behaviours. It also automatically benefits from our global community-wide IP reputation database
On 2021-01-16 05:55:48, Cyril Brulebois wrote:
> Hi anarcat,
>
> And thanks for the swift answer.
>
> Antoine Beaupré <anarcat@debian.org> (2021-01-14):
>> I guess that if it's made clear in the package description, it's fair
>> to phone home by default. After all, you could argue you opt in by
>> installing the package, and can still opt out.
>
> Yeah, I've tried to make that pretty obvious. Since it doesn't seem
> entirely out of line, I think I'll go with this approach.
>
>> Or it could be split into a separate binary package which would
>> explicitly act as an opt-in?
>
> I think I'd rather avoid having to handle different binaries to
> distinguish between those two modes.
Oh I didn't mean *binaries* (e.g. /bin/foo and /bin/bar) but different
binary *packages* (e.g. crowdsec and crowdsec-phones-home). The latter
could have a special config file that would get dropped somewhere and
enable the possibly controversial behavior.
> Upstream already has a wizard to detect various services and perform
> some configuration accordingly. I haven't dived into it yet, but it
> could be a nice basis for some debconf prompt(s), so that one can
> dpkg-reconfigure at will for both the “which mode do you want to be
> in?” and the “which services do you want to handle?” aspects.
I was arguing against debconf and for just a different package, but I
guess debconf would definitely work too! :)
> We will likely make progress on further integration next week. If we
> indeed rely on debconf, that would also mean that people wanting to
> install crowdsec in some automated/non-interactive fashion could just
> preseed some setting to make sure the right mode is picked from the
> get-go. (No pun intended, they just write themselves…)
go get? get go? :)
makes sense, thanks!
a.
--
Everyone is a terrorist.
You're just not pissed enough.
Reply to: