Re: Blacklistd Issues - Problem Identified

From: Doug Hardie <bc979_at_lafn.org>
Date: Tue, 18 Apr 2023 18:18:49 UTC
> On Apr 18, 2023, at 04:21, Michael Grimm <trashcan@ellael.org> wrote:
> 
> Norman Gray <gray@nxg.name> wrote:
>> 
>> On 18 Apr 2023, at 11:08, Michael Grimm wrote:
> 
>>> This has been discussed before [1], and I will definitely support your patch or a solution that makes BADUSER configurable.
>> 
>> I'd be willing to have a go at implementing a configurable version of this change, for consideration (I'm the one who raised the query on the list earlier).
> 
> Yes, I remember.
> 
>> However, that would be my first time with the FreeBSD sources.  Is there a standard process for this?
> 
> I am not an expert either, but I would first of all open a PR. Their you can publish your patches against sources. Someone else will later commit your patch if accepted.
> 
>> I notice that the blacklistd sources aren't in <https://github.com/freebsd/freebsd-src/tree/main/usr.sbin/blacklistd>, so I'm stuck at step 1.
> 
> The sources are at:
> 
> /usr/src/contrib/blacklist
> 
> In /usr/src/contrib/blacklist/bin you'll find blacklistd.conf and the config files in /usr/src/contrib/blacklist/etc
> 
>> Is there an upstream this comes from?  I don't see any mention of such a thing in that directory, but I'm very aware I may be looking in completely the wrong location at this point.
> 
> I am using a git repository (STABLE) to recompile world and kernel from sources. 


Quick answers as I have to leave very soon.

Blacklistd source is in /usr/src/contrib/blacklistd/bin

Apply the patch there.

To recompile it go to /usr/src/usr.sbin/blacklistd and do the make there.

To find the new execuitable go to /usr/obj/usr/src/amd64.amd64/usr.sbin/blacklistd and put the blacklistd there into /usr/libexec

Note the amd64.amd64 directory will be different if you are not on an amd64 machine.  There will probably be only one directory there and it will be the right one.

-- Doug