3 ms·

I wonder how this will affect ssh. OpenSSH recently restricted more characters for valid usernames: https://github.com/openssh/openssh-portable/commit/7ef3787c8

• cedws 2y ago
  This is a great example of how one poor decision, or one piece of code that is too liberal cascades into an avalanche of shitty workarounds.
• throw0101a 2y ago
  It should be noted that shell metacharacters are also not allowed under POSIX: * https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_437 https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1... A B C D E F G H I J K L M N O P Q R S T U V W X Y Z a b c d e f g h i j k l m n o p q r s t u v w x y z 0 1 2 3 4 5 6 7 8 9 . _ - * https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_282 https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1... (Hyphen forbidden as first character.)
• linuxftw 2y ago
  I think it will be fine. Everyone will quickly learn the lesson "Use something other than ASCII letters and numbers at your own peril." Similar to people who put spaces in file names, it should be a fire-able offense.
  • deleted 2y ago
    [deleted]
  • lexicality 2y ago
    any software that can't handle spaces in filenames is broken
    • Muromec 2y ago
      All of the software is broken (including security wise) all the time anyway.
      • bdangubic 2y ago
        this is exactly right... I spoke a few years ago with a mate who is a software dev at one of the major car companies... since then I wouldn't sit in the car from that company if my life depended on it... then I thought - if I spoke any dev in any industry I would also stop doing whatever their software is controlling and end up moving to live with amish or some wilderness without electricity
  • hiccuphippo 2y ago
    Was that the fireable offense? I always thought the offense was not putting quotes around filenames in scripts.