Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-96006

QtRO should use the abstract namespace option for QLocalSocket/Server when using the local backend on Linux

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • Icon: P2: Important P2: Important
    • 6.2.0 Beta4
    • None
    • Remote Objects
    • None

    • Linux

    • Android
    • 3b1416784ef0a209493edeb5c86ea1a347213880 (qt/tqtc-qtremoteobjects/6.2) 9e221d546a0dd4d1cb493cd093f98c07ec650f5c (qt/tqtc-qtremoteobjects/dev)

      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.

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            bstottle Brett Stottlemyer
            mcieslak Michał Cieślak
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved:

                There are no open Gerrit changes