Date: Tue, 31 Aug 2021 05:21:41 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 258179] security/sshguard: Stack Overflow on i386 (stable/13) on startup. sshg-blocker dumps core. Message-ID: <bug-258179-7788-Y5kOHW643r@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-258179-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-258179-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D258179 --- Comment #2 from John Marshall <john@jmarshall.id.au> --- (In reply to Kevin Zheng from comment #1) Thank you Kevin, Following your suggestion, I did some troubleshooting around the whitelist = and blacklist. The problem is the whitelist. The whitelist file on this server is identica= l to the whitelist on the 64-bit server which has no problem. I have three IPv4 address blocks and one IPv6 prefix in that whitelist file. If I comment out= the IPv6 prefix the problem disappears. I have confirmed that I can reproduce t= he problem with a single-line whitelist file: rwsrv04# cat sshguard.whitelist 2001:DB8::/32 rwsrv04#=20 [The IPv6 prefix quoted above is the documentation prefix described in RFC3849.] If I comment out that single line, the service runs. If I remove the commen= t, sshg-blocker aborts with the stack overflow message. Again, I see no problem on the 64-bit system. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-258179-7788-Y5kOHW643r>