Bug 202752

Summary:	use fully qualified path to binary in desktop file
Product:	[Applications] akregator	Reporter:	Maciej Pilichowski <bluedzins>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Unspecified
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Maciej Pilichowski 2009-08-06 07:45:04 UTC

Version:            (using KDE 4.3.0)
Installed from:    SuSE RPMs

When you take a look into akregator's .desktop file you will notice it defines "execute" as just akregator. With such approach there are two issues:
a) security -- it launches as the matter of fact some (ambiguous) akregator binary
b) managament of the system -- akregator relies on content of PATH; to set proper binary each KDE user has to redefine (add the path) on his/her own

In the case of .desktop file there is no need to rely on PATH, there could be and should be fully qualified path, so executing binary won't be ambigous.

Because of (b) I am setting status as bug -- no app should leave holes in the system, even small one.

Comment 1 Pino Toscano 2009-08-06 16:10:23 UTC

Bla bla... the same non-reasons periodically; please learn to search in your very own reports.

*** This bug has been marked as a duplicate of bug 196464 ***

Comment 2 Maciej Pilichowski 2009-08-06 16:21:24 UTC

Do you see "akregator" in the other report? I don't. 

And about reasons -- it is your call, I couldn't care less about _your_ system security, but I care about mine.

Comment 3 Pino Toscano 2009-08-06 16:24:20 UTC

(In reply to comment #2)
> Do you see "akregator" in the other report? I don't.

https://bugs.kde.org/show_activity.cgi?id=196464
It was moved from "akregator" to "kde"; but, originally YOU reported it for "akregator".

> And about reasons -- it is your call, I couldn't care less about _your_ system
> security, but I care about mine.

If something in yoru system is able to change your PATH, you are _already_ compromised, and avoid akregator to be replaced is the very last of your worries at that moment.

Comment 4 Maciej Pilichowski 2009-08-06 16:36:07 UTC

> It was moved from "akregator" to "kde"; but, originally YOU reported it for
> "akregator".

Exactly.

Comment 5 Pino Toscano 2009-08-06 16:40:26 UTC

That still proves my points:
a) you are not able to search within your bugs, even when not specific to a product you think to have reported them
b) akregator and kate (the bugs merged in #196464) have nothing particular to have their .desktop file changed (eventually) while not for all the other kde applications; either it is done globally for all, or (more plausable) it is not; that's why it has been moved in kde

Comment 6 Maciej Pilichowski 2009-08-06 17:02:22 UTC

> That still proves my points

Really? I hope some day you will be finally happy.

Comment 7 Pino Toscano 2009-08-06 17:08:42 UTC

(In reply to comment #6)
> > That still proves my points
> 
> Really? I hope some day you will be finally happy.

Happy to have a reporter which can search in their own bugs? Cannot be, with you I lost my hopes.