https://qa.mandrakesoft.com/show_bug.cgi?id=1179





------- Additional Comments From [EMAIL PROTECTED]  2003-02-20 16:20 -------
I notice this bug is marked as "INVALID", yet it was only after I suggested in this 
bug 
report to put the "new" kdm in mdkkdm as a separate package that it was done--before 
that it was the default, and you *did* remove the old kdm. (Mind you, it wasn't my 
idea--it was suggest in cooker--but I did post it here several days before it was 
implemented that way--using exactly the package name I made up on-the-spot). 
 
Anyway, thank you for fixing this bug -- as in, thank you for putting mdkkdm in it's 
own 
package. I think it's great that Mandrake is taking steps to fill a need that they see 
for 
a simpler dm that can be used by default without *replacing* the more "advanced" 
features of the original kdm. 
 
However, keep in mind that what you have done is fixed a lot of the bugs people 
reported, acted like they never were there in the first place, then replied 
annoymously 
([EMAIL PROTECTED] is ... who?) while trivializing the valid concerns of club 
members, volunteers, and stockholders, and then called the whole thing INVALID. 
The way to get better participating and input is to thank people for reporting bugs, 
not 
trivialize and scoff. 
 
Again, even though I think you've been a bit rude, thank you for fixing this bug -- 
separating the packages and perserving the original kdm is exactly what the point of 
this bug was. 
 
Now, let's get back to work. We've got other bugs to fix. ;) 
 
-- Wes  



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: RESOLVED
creation_date: 
description: 
I've openned this as a bug because I think it has real usability and security 
problems, 
and because there is an easy solution: 
 
The new Mandrake "kdm" that removes the login text field, forces users to login in 
only 
if they are listed, and makes loging in a two-stage process is a big usability and 
security 
problem. 
 
A good solution would probably be: 
 
1) A mdkkdm package (that can be installed by default) that has this new kdm in it 
(although, I surely hope that it is improved before it's used anywhere!) 
 
2) The original unmodified (but it can be branded, as usual--we have no problem with 
that) kdm being installed by kdebase, and used if mdkkdm is not installed. 
 
Others have made plenty of comments in the cooker ML and can add comments here 
as appropriate.

Reply via email to