From: Andreas Schwab <schwab@suse.de>
To: Florian Weimer <fweimer@redhat.com>
Cc: GNU C Library <libc-alpha@sourceware.org>,
"linux-man@vger.kernel.org" <linux-man@vger.kernel.org>
Subject: Re: Are ut_user and ut_host in struct utmp NUL-terminated?
Date: Mon, 13 Aug 2018 14:44:25 +0200 [thread overview]
Message-ID: <mvmeff2o2qe.fsf@suse.de> (raw)
In-Reply-To: <11742781-3872-5bbf-55d6-8ce597f21e53@redhat.com> (Florian Weimer's message of "Mon, 13 Aug 2018 14:10:52 +0200")
On Aug 13 2018, Florian Weimer <fweimer@redhat.com> wrote:
> Can ut_user be exactly UT_NAMESIZE bytes long? Or is it necessary to set
> aside a byte with the NUL terminator?
login from util-linux doesn't null terminate.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2018-08-13 12:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 12:10 Are ut_user and ut_host in struct utmp NUL-terminated? Florian Weimer
2018-08-13 12:44 ` Andreas Schwab [this message]
2018-08-21 8:47 ` Michael Kerrisk (man-pages)
2018-08-21 11:06 ` Florian Weimer
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=mvmeff2o2qe.fsf@suse.de \
--to=schwab@suse.de \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.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 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 NNTP newsgroup(s).