https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210479
--- Comment #10 from Glen Barber <[email protected]> --- (In reply to lidl from comment #9) > (In reply to Glen Barber from comment #6) > > How is sshd supposed to know that blacklistd is enabled but not functioning > properly? > This is why I added DES (and wanted to add you) to the PR. :-) I honestly don't know the answer. I'm still trying to gather more information, in any case. > I suppose I could make the bl_init() code in the blacklist library stat() > the pidfile for the blacklistd daemon, and if not found, not log the > message... But that's pretty fragile and would break if someone moves the > pidfile to a different location... > Agreed on the fragile nature of this. I think this is not a "critical" thing to worry about for 11.0-RELEASE, but it was something I observed as of recent. > The other, much more intrusive, thing would be to add another flag to sshd > (and the other daemons) to specify that blacklist signaling should be used > (and only complain in that configuration, if the connection to the daemon > fails). I think this is far too intrusive, to be honest. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "[email protected]"
