relative paths in Exec= in .desktop and .service files
thiago at kde.org
Wed Sep 10 11:40:18 PDT 2014
On Tuesday 09 September 2014 18:01:55 Jon Watte wrote:
> > Simon's email explained the use-case: relocatable installations,
> > especially on
> > Windows.
> I don't think that's strong enough to open up a security can of worms.
> If you want relocation, use some token system (like how Scons has "#" for
> "root of build")
> And if the main use case is for Windows, then again I'd look carefully at
> actual numbers of users/installs and ability to capture that market, and
> discount the value of that support appropriately.
> Maybe not everyone agrees with that sentiment, but it's a largely
> observable truth :-)
If you feel there are security implications, please say so. If there are
issues, then the desktop spec needs to address them one way or another. We
could choose one of Simon's three suggestions or outright ban the practice.
But all desktops need to be fixed to deal with this correctly.
I also fail to see how having a token is any better than declaring relative
paths to be searched from $PWD. Can you shed more light on this suggestion?
In any case, D-Bus would like to follow the same specification as .desktop
files, but it could diverge if necessary to meet its unique requirements.
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Software Architect - Intel Open Source Technology Center
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
More information about the xdg