https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210479
Glen Barber changed:
What|Removed |Added
Resolution|--- |Overcome By Events
Statu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210479
--- Comment #13 from commit-h...@freebsd.org ---
A commit references this bug:
Author: gjb
Date: Fri Jun 24 23:22:43 UTC 2016
New revision: 302182
URL: https://svnweb.freebsd.org/changeset/base/302182
Log:
Revert r301551, which added bla
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210479
--- Comment #12 from l...@pix.net ---
(In reply to Dag-Erling Smørgrav from comment #11)
The original review was posted on April 11, and you were one of the reviewers
from the initial creation of the review. (I put you there because you'r
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210479
--- Comment #11 from Dag-Erling Smørgrav ---
This was rushed in before the code freeze, without my knowledge and approval,
by a new committer whose mentor holds a personal grudge against me for reasons
I have never been able to determine.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210479
--- Comment #10 from Glen Barber ---
(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 (an
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210479
--- Comment #9 from l...@pix.net ---
(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()
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210479
--- Comment #8 from Glen Barber ---
The below times are with blacklistd running, and a subsequent try without it
running:
gjb@nucleus:~ % time ssh ref11-amd64.freebsd.org exit
0.019u 0.000s 0:01.18 0.8% 576+444k 4+0io 0pf+0w
gjb@nu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210479
--- Comment #7 from l...@pix.net ---
(In reply to Glen Barber from comment #3)
As for the timing differences on your hosts -
Can you please do a 'service blacklistd onestart' on the remote host and
re-do the timings to that host?
I'm curi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210479
--- Comment #6 from Glen Barber ---
(In reply to lidl from comment #5)
> (In reply to Glen Barber from comment #3)
>
> It would be easy enough to remove the logging of the failure to to talk to
> the blacklist daemon, but then how is a use
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210479
--- Comment #5 from l...@pix.net ---
(In reply to Glen Barber from comment #3)
It would be easy enough to remove the logging of the failure to to talk to the
blacklist daemon, but then how is a user supposed to debug the case where they
wan
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210479
--- Comment #4 from Glen Barber ---
(In reply to Glen Barber from comment #3)
> (In reply to lidl from comment #2)
> > The debug logging is expected.
> >
>
> I think this makes auditdistd(8) unhappy.
>
> > I'm unclear by your comment abo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210479
--- Comment #3 from Glen Barber ---
(In reply to lidl from comment #2)
> The debug logging is expected.
>
I think this makes auditdistd(8) unhappy.
> I'm unclear by your comment about delays - delays due to the error state, or
> delay du
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210479
l...@pix.net changed:
What|Removed |Added
CC||l...@pix.net
--- Comment #2 from l..
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210479
--- Comment #1 from Glen Barber ---
I apparently can't add lidl@ to this PR
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing lis
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210479
Bug ID: 210479
Summary: blacklistd(8) and sshd(8) causes login delays and
syslog(8) spam
Product: Base System
Version: 11.0-CURRENT
Hardware: Any
OS:
15 matches
Mail list logo
