Is FreeBSD10 the only other OS version that is still supported for building /usr/ports
and the only one that needs to be listed this way?

Ok, I see where my testing lead me to believe this worked. Turns out the 'make config'
stage was picking up an options file that I did not believe existed.

Pretty much, yes.

Since the blacklistd support now needs to be enabled at runtime,
it is safe to turn on support for it in all cases, so do that in the Makefile.

The point I'm making is the Phabricator review calls it "usbformat", NOT "ufdformat".
Both in the subject of the review, as well as the summary of the review.

The command is actually 'ufdformat', not 'usbformat'.

As much as I agree in spirit with the removal of gets(), or maybe just calling abort2() with
an appropriate message, I think a better course of action is to immediately change
the manpage to say that the function is inherently unsafe to use, deprecated in C11,
and will be removed in the future.

Address emaste's comment about mips64

This change, or one of the others related to it, breaks the operation of zfsloader on sparc64.

The BLACKLIST_BAD_USER and BLACKLIST_ABUSIVE_BEHAVIOR actions are original work by me. I sent these patches to Christos and his only comment was that it looked useful and he wanted documentation changes. So I documented the new actions in the manpage.

Updated man page changes according to review comments.

Well, I reverted the last patch, and then applied the second patch to the /usr/src
tree and rebuilt (via a dependency build) everything.

Survived a buildworld/buildkernel/installkernel/installworld cycle, running on the new kernel (on my V240).

I forwarded this diff to 'des' (who doesn't use phabricator).

While certainly bdes has no place in being used for a new crypto anything,
I think it is a useful tool to have around, for being able to read old files
that have been encrypted that way.

Thanks for updating. Looks good to me.

I forgot to put the Phabricator review URL in the commit message. Manually closing.

I have taken all the third-level indents and turned them into 4 spaces, as per emaste's request. There was also one line longer than 80 characters that I manually wrapped.

This review can be closed. The change to the code has been committed.

Address review comment about error messages when the pf anchor isn't defined.