Since #1919, mosaic accounts init refuses accounts-unsafe when any folder above the config directory is not root's or the stack user's, or is group or other writable without the sticky bit. Step 3 of the SSO migration now says so and gives a read-only stat loop to run first, so a host with a group-writable .config finds out before the live step, not at it.
Doc only. No test reads this text (stack-upgrade.test.mjs names the file path only).
Run sheet follow-up to #1919 (#1873).
Since #1919, `mosaic accounts init` refuses `accounts-unsafe` when any folder above the config directory is not root's or the stack user's, or is group or other writable without the sticky bit. Step 3 of the SSO migration now says so and gives a read-only `stat` loop to run first, so a host with a group-writable `.config` finds out before the live step, not at it.
Doc only. No test reads this text (`stack-upgrade.test.mjs` names the file path only).
mosaic accounts init refuses accounts-unsafe since #1919 when a folder above the
config directory is writable by another user. Step 3 now gives the read-only check.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Run sheet follow-up to #1919 (#1873).
Since #1919,
mosaic accounts initrefusesaccounts-unsafewhen any folder above the config directory is not root's or the stack user's, or is group or other writable without the sticky bit. Step 3 of the SSO migration now says so and gives a read-onlystatloop to run first, so a host with a group-writable.configfinds out before the live step, not at it.Doc only. No test reads this text (
stack-upgrade.test.mjsnames the file path only).