This mail is an automated notification from the bugs tracker
of the project: Savane.
/**************************************************************************/
[bugs #851] Latest Modifications:
Changes by:
Mathieu Roy <[EMAIL PROTECTED]>
'Date:
mer 06.10.2004 � 10:45 (Europe/Paris)
What | Removed | Added
---------------------------------------------------------------------------
Priority | A - Later | C - Normal
/**************************************************************************/
[bugs #851] Full Item Snapshot:
URL: <http://gna.org/bugs/?func=detailitem&item_id=851>
Project: Savane
Submitted by: Sylvain Beucler
On: mar 05.10.2004 � 23:12
Category: Backend
Severity: 3 - Average
Priority: C - Normal
Resolution: None
Privacy: Public
Assigned to: None
Status: 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: 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.
For detailed info, follow this link:
<http://gna.org/bugs/?func=detailitem&item_id=851>
_______________________________________________
Message post� via/par Gna!
http://gna.org/
_______________________________________________
Savane-dev mailing list
[EMAIL PROTECTED]
https://mail.gna.org/listinfo/savane-dev
