Details
-
Suggestion
-
Resolution: Fixed
-
P2: Important
-
None
-
None
-
Linux
-
-
3b1416784ef0a209493edeb5c86ea1a347213880 (qt/tqtc-qtremoteobjects/6.2) 9e221d546a0dd4d1cb493cd093f98c07ec650f5c (qt/tqtc-qtremoteobjects/dev)
Description
Fix for https://bugreports.qt.io/browse/QTBUG-16090 introduces an option (AbstractNamespaceOption) allowing using abstract namespaces for QLocalSocket/QLocalServer classes.
Currently, QtRO, for urls starting from "local:", uses the generic sockets which rely on creating temporary files.
In some secured Linux systems (chrooted environment, cgroup, nfs and so on) there is no writable places at all. So some Qt programs does not work. For instance, communication between Android activity and service within the same app using RO with "local:*" url is not possible.
Therefore, I think that using AbstractNamespaceOption for QLocalSocket/QLocalServer in RO's local backend implemention should be considered.
Attachments
Issue Links
- relates to
-
QTBUG-16090 QLocalSocket should support the abstract namespace on Linux
- Closed
For Gerrit Dashboard: QTBUG-96006 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
366916,8 | Provide a schema for abstract local sockets | dev | qt/qtremoteobjects | Status: MERGED | +2 | 0 |
367952,2 | Provide a schema for abstract local sockets | 6.2 | qt/qtremoteobjects | Status: MERGED | +2 | 0 |