Revisit blacklistd support in ftpd
ClosedPublic
Actions

Authored by • lidl on Oct 28 2016, 2:40 PM.

Details

Reviewers

emaste
cem

Group Reviewers

manpages

Commits

rS308175: Revisit blacklistd support in ftpd

Summary

Enhance blacklistd support to not log anything by default,
unless blacklistd support is enabled on the command line.
Document new flag in man page, cleanup patches to be less
intrusive in code.

Diff Detail

Repository

rS FreeBSD src repository - subversion

Lint

Lint Not Applicable

Unit

Tests Not Applicable

Event Timeline

• lidl updated this revision to Diff 21769.Oct 28 2016, 2:40 PM

• lidl retitled this revision from to Revisit blacklistd support in ftpd.

• lidl updated this object.

• lidl edited the test plan for this revision. (Show Details)

• lidl added a reviewer: emaste.

• lidl set the repository for this revision to rS FreeBSD src repository - subversion.

Herald added a reviewer: manpages. · View Herald TranscriptOct 28 2016, 2:40 PM

Herald added a subscriber: imp. · View Herald Transcript

cem accepted this revision.Oct 28 2016, 4:45 PM

cem added a reviewer: cem.

cem added a subscriber: cem.

cem added inline comments.

libexec/ftpd/ftpd.c
335 ↗	(On Diff #21769)	Should this be err() instead?

This revision is now accepted and ready to land.Oct 28 2016, 4:45 PM

• lidl added inline comments.Oct 28 2016, 6:33 PM

libexec/ftpd/ftpd.c
335 ↗	(On Diff #21769)	I would argue 'no'. The blacklist support is just supposed to notify the blacklist daemon, not alter the flow of execution of the augmented program. If someone specified the -B flag in their config, but then managed to get a binary installed without blacklist support, I don't think it is appropriate to start failing just because the configuration via rc.conf or inetd.conf has gone stale.

cem added inline comments.Oct 28 2016, 6:38 PM

libexec/ftpd/ftpd.c
335 ↗	(On Diff #21769)	The counterargument might be: The user has elected to start the daemon with a security mitigation enabled. If we can't support that, we have no business silently running without the mitigation. If we abort, the user can fix their configuration (if it is a stale configuration problem).