aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAlex Merry <alex.merry@kde.org>2014-03-21 18:13:46 +0000
committerAlex Merry <alex.merry@kde.org>2014-03-24 11:22:38 +0000
commita9ac60da055e108d153e265190ebd870cecb9f6f (patch)
treec36709438b01e10edcb53f30907eb9d7f7eff6d4
parent2cb32b4dc0ed9aed3ae705d34269f99d82c3c6dc (diff)
downloadkconfig-a9ac60da055e108d153e265190ebd870cecb9f6f.tar.gz
kconfig-a9ac60da055e108d153e265190ebd870cecb9f6f.tar.bz2
Update docs for KDesktopFile::isAuthorizedDesktopFile()
The fact that it changed in KDE 4.3 is not so relevant any more. REVIEW: 116962
-rw-r--r--src/core/kdesktopfile.h9
1 files changed, 4 insertions, 5 deletions
diff --git a/src/core/kdesktopfile.h b/src/core/kdesktopfile.h
index df8eff1a..2190051d 100644
--- a/src/core/kdesktopfile.h
+++ b/src/core/kdesktopfile.h
@@ -87,11 +87,10 @@ public:
* the KIOSK framework can be used to activate certain restrictions.
* See README.kiosk for more information.
*
- * Note: Since KDE 4.3, there are more restrictions on authorized
- * desktop files to prevent users from inadvertently running trojan
- * desktop files. Your application launchers should have the executable
- * bit set to prevent issues. To see if a restriction is due to
- * KIOSK, see KAuthorized.
+ * Note that desktop files that are not in a standard location (as
+ * specified by XDG_DATA_DIRS) must have their executable bit set
+ * to be authorized, regardless of KIOSK settings, to prevent users
+ * from inadvertently running trojan desktop files.
*
* @param path the file to check
* @return true if the user is authorized to run the file