3 ms·

homed is a purely optional, independent tool, for use in situations where you’d use roaming home directories on windows, or similar technology. No one is forci

• throw0101a 7y ago
  > No one is forcing you to change your broken buggy 30-year old shell scripts, you can always continue using them. How about usernames that start with a digit? Am I still allowed to use those? * https://ma.ttias.be/giving-perspective-systemds-usernames-start-digit-get-root-privileges-bug/ https://ma.ttias.be/giving-perspective-systemds-usernames-st...
  • kuschku 7y ago
    POSIX says that any tool should always translate usernames into userids at the earliest possible point, and pass UIDs to children it spawns. Now assuming I have a user called 1000 with UID 2000, and a user called 2000 with UID 1000. Now what do you think is gonna happen if multiple POSIX-compliant tools call each other? This is clearly broken, and the reason why BSDs don’t actually implement POSIX cleanly, instead allowing all their tools to take unambiguous identifiers on the CLI, with the # prefix to mark a UID, and have all their tools call all their children with this format. The POSIX standard is clearly suboptimal here, and the set of valid usernames, and the set of valid UIDs should never have been allowed to overlap.
    • throw0101a 7y ago
      The weblog post has an user called '0day', i.e., "zero day". This breaks systemd as outlined in the post. This is a WONTFIX per the systemd folks.
      • kuschku 7y ago
        That’s one of the possible options, the other would be replacing chown, chmod, ls, etc (as the BSDs do)