Jamie, I've been discussing this with the local LUG and the response is unanimous that this should be considered a security issue.
I would like to ask you to reconsider your re-classification, and if possible explain to us why this is not considered a security problem. Regards, Vik Olliver On Mon, 2008-11-10 at 14:26 +0000, Jamie Strandboge wrote: > ** This bug is no longer flagged as a security issue > > -- > blueproximity has no locking option for KDE4.1/Plasma > https://bugs.launchpad.net/bugs/296085 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in “blueproximity” source package in Ubuntu: New > > Bug description: > With the current Intrepid release 8.10, blueproximity comes with no > option for locking the KDE4.1 desktop, only gnome desktops. > > The old bodge of using dcop to notify kdesktop no longer works with > Plasma: > > [EMAIL PROTECTED]:~$ dcop kdesktop KScreensaverIface > ERROR: Couldn't attach to DCOP server! > > blueproximity 1.2.5-3 > > This causes workstations not to be automatically locked when they were > before the upgrade, and in a way that would be transparent to the user > as they never actually see their workstation locked when carrying > their phone. Hence the security vulnerability. > > -- blueproximity has no locking option for KDE4.1/Plasma https://bugs.launchpad.net/bugs/296085 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
