https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210479
--- Comment #9 from [email protected] --- (In reply to Glen Barber from comment #6) How is sshd supposed to know that blacklistd is enabled but not functioning properly? 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... 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). -- 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]"
