This is an automated notification sent by Gna!.
It relates to:
bugs #851, project Savane
==============================================================================
LATEST MODIFICATIONS of bugs #851:
==============================================================================
Posted by: Mathieu Roy <yeupou>
Posted on: mar 09.11.2004 à 17:34 (Europe/Paris)
What | Removed | Added
---------------------------------------------------------------------------
Priority | C - Normal | A - Later
Status | None | Later
------------------ Additional Follow-up Comments ----------------------------
In fact, ',' was allowed both at registration and name change. I modified the
frontend so it removes any commas found, until the backend is modified in this
regard.
==============================================================================
OVERVIEW of bugs #851:
==============================================================================
URL:
<http://gna.org/bugs/?func=detailitem&item_id=851>
Project: Savane
Submitted by: Sylvain Beucler
Submitted on: mar 05.10.2004 à 23:12
Category: Backend
Severity: 3 - Average
Priority: A - Later
Status: Later
Privacy: Public
Assigned to: None
Open/Closed: Open
Release:
Planned Release:
Summary: Commas in Real Name not supported
_______________________________________________________
Original Submission:
The code that parses the MySQL query result in DB.pm joins everything with a
","; hence, when there is a comma in the Real Name of a user account, things
are shifted.
What is pretty unfortunate is that scripts seem to rely on this structure, eg
sv_users.pl splits the result using split(","). As a consequence the SSH keys
are replaced by a part of the Real Name and the account is not updated well.
It seems the GetDB() procedure as well as its calls should be rewritten
thorough Savane so as to return a table instead of a string.
_______________________________________________________
Commentaires :
-------------------------------------------------------
Date: mar 09.11.2004 à 17:34 By: Mathieu Roy <yeupou>
In fact, ',' was allowed both at registration and name change. I modified the
frontend so it removes any commas found, until the backend is modified in this
regard.
-------------------------------------------------------
Date: mer 06.10.2004 à 10:56 By: Sylvain Beucler <beuc>
The user name was something like "Jim Lowe, Jr.", so the use of the comma was
justified IMHO.
Currently I do not have the time to do that task, since I am still working on
the merge with the Savannah changes, but I could do it after if nobody did.
-------------------------------------------------------
Date: mer 06.10.2004 à 10:45 By: Mathieu Roy <yeupou>
"It seems the GetDB() procedure as well as its calls should be rewritten
thorough Savane so as to return a table instead of a string."
In my opinion, the problem is the fact that an user was able to enter a real
name (or whatever field) with a comma.
I think the account creation process disallow that already. But maybe the
"change name" page does not do the appropriate checks.
"It seems the GetDB() procedure as well as its calls should be rewritten
thorough Savane so as to return a table instead of a string."
That could be something interesting to do. When I wrote GetDB, I just grabbed
the way things were done in sv_cvs, the original backend. The point was to
having more or less the same code reorganized. This step being achieved, we can
perfectly improve it.
And I think that each time GetDB() is called, we transform it into a list with
split(). So if GetDB() returning a list, that would be definitely cleaner and
would avoid this bug.
==============================================================================
This item URL is:
<http://gna.org/bugs/?func=detailitem&item_id=851>
_______________________________________________
Message posté via/par Gna!
http://gna.org/
