lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <iezzxq25mqdcapusb32euu3fgvz7djtrn5n66emb72jb3bqltx@lr2545vnc55k>
Date: Wed, 16 Apr 2025 18:50:00 +0200
From: Alejandro Colomar <alx@...nel.org>
To: linux-kernel@...r.kernel.org, linux-api@...r.kernel.org, 
	linux-man@...r.kernel.org
Subject: newlines in filenames; POSIX.1-2024

Hi,

I'm updating the manual pages for POSIX.1-2024.  One of the changes in
this revision is that POSIX now encourages implementations to disallow
using new-line characters in file names.

Historically, Linux (and maybe all existing POSIX systems?) has allowed
new-line characters in file names.

I guess there's no intention to change that behavior.  But I should ask.
I thought of adding this paragraph to all pages that create file names:

	+.SH CAVEATS
	+POSIX.1-2024 encourages implementations to
	+disallow creation of filenames containing new-line characters.
	+Linux doesn't follow this,
	+and allows using new-line characters.

Are there any comments?


Have a lovely day!
Alex

-- 
<https://www.alejandro-colomar.es/>

Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ