Why does chfn not escape "illegal" characters to render them legal?
#3589
-
|
As an example, Footnotes |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
POSIX defines the /etc/passwd format, but not the GECOS subfields and separators. The use of commas is just a commonly supported convention. It's possible that the field is parsed not only by chfn but also by other tools or third-party scripts. I have doubts that changing the format is a good idea, as it will very likely introduce regressions for some users. |
Beta Was this translation helpful? Give feedback.
-
@karelzak, the current format is already error-prone, since I've seen anecdotes from other users stating that they've utilised software which indeed doesn't parse the commas. When I ascertain how to contact the Austin Group Chair, I'll take this to the Open Group. Thanks for the assistance. |
Beta Was this translation helpful? Give feedback.
-
|
@karelzak, it turns out that this might be impossible, per |
Beta Was this translation helpful? Give feedback.
POSIX defines the /etc/passwd format, but not the GECOS subfields and separators. The use of commas is just a commonly supported convention. It's possible that the field is parsed not only by chfn but also by other tools or third-party scripts. I have doubts that changing the format is a good idea, as it will very likely introduce regressions for some users.