fixed sorting inside a jail. No amount of LC_ALL and related settings makes it work outside. thanks!

use jailed sorting

In D48245#1100054, @bofh wrote:

I don't think this is the correct approach for dns/p5-Zonemaster-Backend port. This port should have flavors; if not at least options to configure DB backends like sqlite, mysql and pgsql. A quick example for flavors might be postfix or freeradius.

The rest looks alright to me.

while testing jls output with new tags, I noted that the manpage says " Each jail is represented by one row which contains space-separated values of the listed parameter". Which is not quite the case as many parameters could have an embedded new line, that's not trimmed out.

In D47668#1095802, @igoro wrote:

In D47668#1095800, @jamie wrote:

In D47668#1095796, @igoro wrote:

• The allowed chars for each buffer are very limited by default, it covers Base64, k=v\n format, and some extra bytes. It can be changed via security.jail.meta_allowedchars sysctl. For convenience (as it seems to me for now), setting it to an empty string allows everything.

Why is this a kernel issue? Aside from NUL, because it preserves the C-string nature, allowed characters would seem only to be a concern on the user side.

Yes, that's a good point. Indeed, it feels like a user-land concern by default. If we agree to limit it by default for extra security, then having it in a single place covers all use cases and entry points: jail(8), flua, libjail, direct syscall, and so on -- it seems preferable to addressing it separately for each existing and future syscall consumer. What do you think? Does this approach offer additional benefits for us?

fixed!

add \n for bcr, fix a prior hugo error (duplicate id)

thanks Franco for the heads-up. The correct place for bugs is bugzilla, please report it there. As usual, it helps if you can provide a kgdb/backtrace with line numbers, and more details on the scenario, ideally with a reproducible test case on stock FreeBSD.

text LGTM, I'm not familiar with this markup flavour tho.

There seems to be strong support for separating tags. I am
indifferent to either approach (I can do what I need either way)
but there is a strong tradeoff:

dealt with in ports & eventually upstream as well.

add extra ports logic, drop -devel as we do not need it for release
and haven't maintainer approval for it.

thanks, this one's ready to go now.

updated for 14.2

• trim license
• embiggen VMSIZE
• rejig patch after OCI->ORACLE rename

embiggen the image again for 13.x sitting at 6.7GiB

I submitted https://reviews.freebsd.org/D47338 to fix the port directly.

bump

add cloud-init-devel also