All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: "Thaddeus H. Black" <thb@debian.org>
Cc: linux-man@vger.kernel.org,
	Alejandro Colomar <alx.manpages@gmail.com>,
	"G. Branden Robinson" <g.branden.robinson@gmail.com>,
	Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: [PATCH v3] filename.7: new manual page
Date: Wed, 20 Oct 2021 10:12:02 +0200	[thread overview]
Message-ID: <87lf2oxgh9.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <YW6mcn0uMW3FWUu6@b-tk.org> (Thaddeus H. Black's message of "Tue, 19 Oct 2021 11:05:22 +0000")

* Thaddeus H. Black:

>> What does this mean?  I think only byte 0x2f is reserved.  The UTF-8
>> comment is misleading.  A historic/overlong encoding of / in multiple
>> UTF-8 bytes is *not* reserved.
>
> I had not known that UTF-8 had an alternate encoding for any ASCII
> character.  Does it indeed have an alternate encoding?  If so, where
> can I learn more?

See the Security Considerations section in the RFC:

  <https://datatracker.ietf.org/doc/html/rfc3629#section-10>

Most file systems do not treat file names as UTF-8, so they do not
perform any validation.

Thanks,
Florian


  parent reply	other threads:[~2021-10-20  8:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-17 23:07 [PATCH v2] filename.7: new manual page Thaddeus H. Black
2021-10-18 16:25 ` Thaddeus H. Black
2021-10-18 16:33 ` [PATCH v3] " Thaddeus H. Black
2021-10-19  8:54   ` Florian Weimer
2021-10-19 11:05     ` Thaddeus H. Black
2021-10-19 13:55       ` Alejandro Colomar (man-pages)
2021-10-20  8:12       ` Florian Weimer [this message]
2021-10-21 12:18         ` Thaddeus H. Black
2021-10-19 13:38   ` Alejandro Colomar (man-pages)
2021-11-07 14:36     ` Thaddeus H. Black

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lf2oxgh9.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=alx.manpages@gmail.com \
    --cc=g.branden.robinson@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=thb@debian.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.