Bug 7980 - Mageia Control Center User configuration does not allow Mixed-Case user names.
Summary: Mageia Control Center User configuration does not allow Mixed-Case user names.
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL: https://forums.mageia.org/en/viewtopi...
Whiteboard:
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2012-11-05 12:39 CET by Nick Causton
Modified: 2013-11-23 16:15 CET (History)
6 users (show)

See Also:
Source RPM: userdrake
CVE:
Status comment:


Attachments

Description Nick Causton 2012-11-05 12:39:15 CET
Description of problem:
MCC (Manage Users) does not allow creation or editing of Mixed-Case user names, despite the fact that the underlying 'adduser' command does allow these.  Is there any known reason why MCC places this restriction on user names?

Version-Release number of selected component (if applicable):
userdrake-1.13.6-1.mga2

How reproducible:
Create or edit a MixedCaseUser name

Steps to Reproduce:
1. Create a MixedCaseUser in MCC Users and Groups
2. This is not allowed and returns an error explaining that user names must be in lower-case.
3.
Manuel Hiebel 2012-11-28 23:45:51 CET

Component: Security => RPM Packages
Source RPM: userdrak => userdrake

Comment 1 Samuel Verschelde 2013-09-06 19:14:01 CEST
Hi, thanks for reporting this bug.
As there is no maintainer for this package I added people who worked on it in CC, as well as the drakxtools maintainer.

Keywords: (none) => Triaged
CC: (none) => dmorganec, ennael1, mageia, stormi, thierry.vignaud

Comment 2 Dave Hodgins 2013-09-06 23:11:50 CEST
Using mixed case for user names is not a good idea.

I created two users, tester and TESTER. Then send a message using
mail TESTER. The mail went to tester, not TESTER.

That's correct according to rfc 821, although wrong according to rfc2821.

I think the restriction should be kept.

CC: (none) => davidwhodgins

Comment 3 Manuel Hiebel 2013-10-22 12:18:21 CEST
This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad
Comment 4 Manuel Hiebel 2013-11-23 16:15:10 CET
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.