Request to add options in the chroot permissions check.

Hello,


I am using Openssh as part of a file transfer system running inside a
container. I am writing here to request some flexibility in the
ChrootDirectory functionality. At present, it checks that all directories
leading to the root are root owned.

This forces me to reduce the security inside the containers. I would prefer
all the directories being owned by the root of the container, which is seen
as nobody inside the container. This improves security, as it protects
against a possible bug in Openssh making the container stronger.

I propose two solutions that I am willing to implement:
- An option ChrootDirectorySkipCheckIUnderstandThisIsRisky, that disables
the checks. But with that name, the system administrator is taking full
responsibility if something goes wrong, and the Openssh team cannot be
blamed. For situations like mine, it could work.
- An option ChrootCheckInsideContainer, that accepts the uid and gid found
in /proc/sys/kernel/overflowuid as acceptable owners for chroot
directories. This would be a focused approach.

Would any of these options be acceptable?