From: Leo Famulari <leo@famulari.name>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 53743@debbugs.gnu.org, Tsarina Baelarina Nina <bills.jared@outlook.com>
Subject: bug#53743: Using spaces in names doesn't have complete sanitization
Date: Thu, 3 Feb 2022 23:18:57 -0500 [thread overview]
Message-ID: <YfypMc+GOTssfmTg@jasmine.lan> (raw)
In-Reply-To: <8bb8bafc10f66aafda6487552c3a76f9663c42e5.camel@telenet.be>
On Thu, Feb 03, 2022 at 06:32:51PM +0000, Maxime Devos wrote:
> Tsarina Baelarina Nina schreef op wo 02-02-2022 om 20:49 [-0800]:
> > I put my name as Tsarina Baelarina Nina, as opposed to my real name.
> > It created the correct home profile, but also included the two extra
> > empty directories in my home directory as included in the attachment
> > for proof. I think I remember reading something about camel casing
> > for user names on the system, as in the name can't start with a
> > capital letter, but I thought you could get away with spaces if you
> > escaped the strings properly \(space).
>
> I can reproduce with the attached configuration.
> I'm wondering what software is creating these 'Baelarina' and 'Nina'
> subdirectories of '/home/Tsarina Baelarina Nina/' ... is it Guix, is it
> GDM, is it the GNOME desktop ...?
I'm not very familiar with this part of the system, but I think that
user home directories are created here, in ((gnu build activation)
activate-users+groups):
https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/build/activation.scm?id=ff093f5739a61e77b296feccc48d260b9bb574c0#n160
next prev parent reply other threads:[~2022-02-04 4:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 4:49 bug#53743: Using spaces in names doesn't have complete sanitization Tsarina Baelarina Nina
2022-02-03 18:32 ` Maxime Devos
2022-02-04 4:18 ` Leo Famulari [this message]
2022-02-04 4:50 ` Leo Famulari
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YfypMc+GOTssfmTg@jasmine.lan \
--to=leo@famulari.name \
--cc=53743@debbugs.gnu.org \
--cc=bills.jared@outlook.com \
--cc=maximedevos@telenet.be \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).