Between account system groups (bearing the same GID number
than the UID they pertain to) and bastion groups, there
might be collisions on bastions with a very high amount
of both accounts and groups.
This is only of importance if you're using fixed UIDs
to create accounts, and can't let the system pick the
UIDs itself (for example because these UIDs are referenced
in some other system of your company).
This fix applies a GID shifting to all the bastion groups
to ensure they can never take a GID that would pertain to
a later-to-be-created account with a fixed GID.
This shift amount is configurable in bastion.conf as
``accountGidMin``, 500000 by default.
Use the updated bin/admin/fix-group-gid.sh script to shift any
preexisting group GID that would be out of the new groupGidMin range.
To avoid confusion, we now use 'subnet' to talk about a subnet
represented with the CIDR notation, such as 10.0.0.0/8.
In in that case:
- 10.0.0.0/8 is a 'subnet'
- 10.0.0.0 is the 'prefix'
- 8 is the 'prefix length', or by extension the 'subnet length'
Use these words everywhere in the code and documentation for clarity.
Before 932e72e, plugin-scoped stealthStdout was ignored, which was
fixed by 932e72e which in turn made ssh ignore the pattern-based egress ssh
stealthStdout option.
This fix ensures stealthStdout is honored for both plugins and egress ssh.
Replace --sftp --scpup --scpdown by --protocol PROTOCOL.
Also take the opportunity to replace --user-any by --user * and --port-any by --port *.
All the legacy options are still supported but are now undocumented.