PlatSec warnings: Qt wants AllFiles?

[daou]

I'm using 4.5.0-garden with 3rd FP2 SDK. Whenever I run a Qt application on the emulator, it floods the emulator debug output with PlatSec warnings about AllFiles missing. Is this an issue only with the emulator builds? I haven't tried running any phone builds on a device yet.

The output from one of the Qt examples:

  693.805	*PlatSec* WARNING - Capability check would have failed - A Message (function number=0x00000016) from Thread chart[a000a647]0001::chart, sent to Server !FileServer, was checked by Thread EFile.exe[100039e3]0001::Main and was found to be missing the capabilities: AllFiles .  Additional diagnostic message: \private Used to call: Entry
   693.805	*PlatSec* WARNING - Capability check would have failed - A Message (function number=0x00000016) from Thread chart[a000a647]0001::chart, sent to Server !FileServer, was checked by Thread EFile.exe[100039e3]0001::Main and was found to be missing the capabilities: AllFiles .  Additional diagnostic message: \private Used to call: Entry
   693.805	*PlatSec* WARNING - Capability check would have failed - A Message (function number=0x00000016) from Thread chart[a000a647]0001::chart, sent to Server !FileServer, was checked by Thread EFile.exe[100039e3]0001::Main and was found to be missing the capabilities: AllFiles .  Additional diagnostic message: \private\ Used to call: Entry
   693.810	*PlatSec* WARNING - Capability check would have failed - A Message (function number=0x00000016) from Thread chart[a000a647]0001::chart, sent to Server !FileServer, was checked by Thread EFile.exe[100039e3]0001::Main and was found to be missing the capabilities: AllFiles .  Additional diagnostic message: \private\a000a647 Used to call: Entry
   693.810	*PlatSec* WARNING - Capability check would have failed - A Message (function number=0x00000016) from Thread chart[a000a647]0001::chart, sent to Server !FileServer, was checked by Thread EFile.exe[100039e3]0001::Main and was found to be missing the capabilities: AllFiles .  Additional diagnostic message: \private\a000a647 Used to call: Entry
   693.855	*PlatSec* WARNING - Capability check would have failed - A Message (function number=0x00000016) from Thread chart[a000a647]0001::chart, sent to Server !FileServer, was checked by Thread EFile.exe[100039e3]0001::Main and was found to be missing the capabilities: AllFiles .  Additional diagnostic message: \private Used to call: Entry
   693.860	*PlatSec* WARNING - Capability check would have failed - A Message (function number=0x00000016) from Thread chart[a000a647]0001::chart, sent to Server !FileServer, was checked by Thread EFile.exe[100039e3]0001::Main and was found to be missing the capabilities: AllFiles .  Additional diagnostic message: \private Used to call: Entry
   693.860	*PlatSec* WARNING - Capability check would have failed - A Message (function number=0x00000016) from Thread chart[a000a647]0001::chart, sent to Server !FileServer, was checked by Thread EFile.exe[100039e3]0001::Main and was found to be missing the capabilities: AllFiles .  Additional diagnostic message: \private\ Used to call: Entry
   693.860	*PlatSec* WARNING - Capability check would have failed - A Message (function number=0x00000016) from Thread chart[a000a647]0001::chart, sent to Server !FileServer, was checked by Thread EFile.exe[100039e3]0001::Main and was found to be missing the capabilities: AllFiles .  Additional diagnostic message: \private\a000a647 Used to call: Entry
   693.865	*PlatSec* WARNING - Capability check would have failed - A Message (function number=0x00000016) from Thread chart[a000a647]0001::chart, sent to Server !FileServer, was checked by Thread EFile.exe[100039e3]0001::Main and was found to be missing the capabilities: AllFiles .  Additional diagnostic message: \private\a000a647 Used to call: Entry
   693.890

[daou]

After thinking about it, this is probably just Qt setting the path to the application's private directory. Which is necessary, and the Qt phone build probably has the AllFiles capability it needs.

If so, this shouldn't create any problems for deploying self-signed applications on the phone.

[jakoskin]

After thinking about it, this is probably just Qt setting the path to the application's private directory. Which is necessary, and the Qt phone build probably has the AllFiles capability it needs.

If so, this shouldn't create any problems for deploying self-signed applications on the phone.

You got it almost right

Errors come from QSettings accessing files from private directory. When checking that your private directory (SID) exists we access /private/ which isn't allowed and thus generating plat-sec AllFiles capability warning.

You don't have to worry about this warning. Qt works even if that warning is there.
It is on low priority as this is cosmetic issue, but eventually should be fixed.