Project

General

Profile

Actions
Copy link

Bug #182

open

cynagora service not accessible because directory of its sockets badly labelled for SMACK

Added by José Bollo 4 days ago. Updated 1 day ago.

Status:
In Progress
Priority:
High
Assignee:
José Bollo
Target version:
-
Start date:
11/20/2024
Due date:
% Done:

0%

Estimated time:
Hardware platform:
Renesas H3ULCB (aarch64), Raspberry PI 4 (aarch64), Qemu (x86_64), Up Board (x86_64), Renesas H3ULCB+Kingfisher (aarch64), Renesas M3ULCB (aarch64), Renesas M3ULCB+Kingfisher (aarch64), AGL Reference Hardware (aarch64), Other Renesas board (aarch64), Other Raspberry Hardware (aarch64), Other AMD/Intel Hardware (x86_64), Solidrun (aarch64), Nitrogen8M i.MX8M (aarch64), NXP i.MX 8 (aarch64), Other, Desktop SDK (Debian 10), Desktop SDK (Debian 11), Desktop SDK (Fedora 33), Desktop SDK (Fedora 34), Desktop SDK (Ubuntu 20.04), Desktop SDK (openSUSE Leap 15.2), Desktop SDK (openSUSE Leap 15.3)
OS Affects Version/s:
arz-1.0, arz-1.0-update, arz-1.0.1, arz-1.1, arz-1.1-update, arz-1.2, batz-2.0
OS Fix Version/s:
Labels:

Description

Cynagora version 2.2.5 and earlier have issue when exposing its sockets. The directory /run/cynagora is labelled 'System' and can't be accessed by user applications. The correct labelling is done in the service cynagora sin version 2.2.5 but it does not work because that service is only activated when socket are accessed. It is a kind of circle dependency.

Actions
Copy link

Also available in: Atom PDF