Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Suggestion: increase username buffer size in busybox login
Date: Fri, 17 Aug 2012 14:30:17 +0200	[thread overview]
Message-ID: <20120817143017.65099bd6@skate> (raw)
In-Reply-To: <CADiAo4Jn7525qF0+_mXhDT2j5-k+W-SCsXf1x8oaAEuNvWz66g@mail.gmail.com>

Le Tue, 14 Aug 2012 23:18:16 -0400,
Dmitry Golubovsky <golubovsky@gmail.com> a ?crit :

> Well, the busybox developers stick with the original Unix spec
> limiting username length at 32 chars:
> 
> http://lists.busybox.net/pipermail/busybox/2012-August/078256.html
> 
> So I am repeating my question: is anybody among Buildroot users also
> interested in such patching of busybox: in case longer usernames (like
> firstname.lastname at host.example.org) are desired, increase the
> username buffer in login.c to 256 characters?

This should not be implemented in Buildroot, as we don't want to keep
such "feature" patches on our packages. Make a patch to Busybox that
turns this into a configurable value, so that by default the length of
32 characters is used, but a Busybox configuration option allows to
extend that. Then, Buildroot users interested by this feature can
create a custom Busybox configuration.

Thanks!

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2012-08-17 12:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-14 13:47 [Buildroot] Suggestion: increase username buffer size in busybox login Dmitry Golubovsky
2012-08-14 17:07 ` Yann E. MORIN
2012-08-15  3:18   ` Dmitry Golubovsky
2012-08-17 12:30     ` Thomas Petazzoni [this message]
2012-08-17 12:46       ` Dmitry Golubovsky
2012-08-17 13:17         ` Thomas Petazzoni
2012-08-17 13:40           ` Dmitry Golubovsky

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=20120817143017.65099bd6@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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