Project

General

Profile

Actions
Copy link

Bug #29

closed
EJ JB

Permission to open /dev/ttymxc2 is denied to bms2orp-binding

Bug #29: Permission to open /dev/ttymxc2 is denied to bms2orp-binding

Added by Emmanuel Jubera [SAFT] over 3 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
Low
Assignee:
José Bollo
Target version:
arz-1.0.2
Start date:
09/06/2022
Due date:
% Done:

0%

Estimated time:
Hardware platform:
Solidrun (aarch64)
OS Affects Version/s:
arz-1.0
OS Fix Version/s:
Labels:

Description

Although urn:AGL:permission::partner:scope-platform and urn:AGL:permission::system:capability:keep-all are set for bms2orp-binding, the latter is denied the right to open /dev/ttymxc2.

A workaround was found, consisting in editing /etc/udev/rules.d/55-udev-smack-default.rules and changing line

SUBSYSTEM=="tty", KERNEL=="tty", GROUP="tty", MODE="0666", SECLABEL{smack}="*" into line
SUBSYSTEM=="tty", KERNEL=="tty*", GROUP="tty", MODE="0666", SECLABEL{smack}="*"

VR Updated by Vincent Rubiolo over 3 years ago Actions
Copy link
 #1

  • Assignee changed from Vincent Rubiolo to José Bollo

SD Updated by Sebastien Douheret [IoT.bzh] over 3 years ago Actions
Copy link
 #2

  • OS Affects Version/s arz-1.0.0 added

SD Updated by Sebastien Douheret [IoT.bzh] over 3 years ago Actions
Copy link
 #3

  • OS Affects Version/s arz-1.0 added
  • OS Affects Version/s deleted (arz-1.0.0)

SD Updated by Sebastien Douheret [IoT.bzh] over 3 years ago Actions
Copy link
 #4

  • Target version set to arz-1.0.2

JB Updated by José Bollo about 3 years ago Actions
Copy link
 #5

  • Status changed from New to Resolved

Modifications for solving this issue are pushed internally and will land in arz-1.0.2 and arz-1.1.1

Waiting final verification for closing

JB Updated by José Bollo almost 3 years ago Actions
Copy link
 #6

  • Status changed from Resolved to In Progress

JB Updated by José Bollo almost 3 years ago Actions
Copy link
 #7

reopened.

I'm working on a solution where

  1. the device ttymc2 is correctly detected and permission to rw it given to group "dialout"
  2. the supplementary group dialout is given to application requiring the permission "urn:AGL:permission::partner:dialout"

So the config.xml of orp-binding has to be modified to request that permission

JB Updated by José Bollo almost 3 years ago Actions
Copy link
 #8

  • Status changed from In Progress to Resolved

JB Updated by José Bollo almost 3 years ago Actions
Copy link
 #9

integration of sec-lsm-manager 1.0 fixed the issue

Actions
Copy link

Also available in: PDF Atom