diff options
author | Sebastien RAILLET <sebastien.raillet@marelli.com> | 2021-09-22 16:54:31 +0200 |
---|---|---|
committer | Saya Sugiura <39760799+ssugiura@users.noreply.github.com> | 2021-10-12 14:55:32 +0900 |
commit | 1919000c897ccf0f88a5584faf3a2efc1a7a3c30 (patch) | |
tree | 2e10abe01f75c9ac2a3427b3a3d5ecf893a800e9 /automotive-dlt-c++.pc.in | |
parent | 9214f892302615beed95222b56065655a40ff2a7 (diff) | |
download | DLT-daemon-1919000c897ccf0f88a5584faf3a2efc1a7a3c30.tar.gz |
dlt-daemon: create sockets using "android way"
* Before this commit, dlt-daemon sockets were created inside
/data/local/tmp. This works but have many drawbacks:
- /data/local/tmp isn't always a tmpfs depending of the android
system you have. Means sockets are potentially created on a
filesystem which binds to a real device
- as the sockets are created by the dlt-daemon itself, this
prevent the usage of specific SELinux labels / contexts as
they will inherit the label / context from its parent
location (e.g the ones from /data/local/tmp). This prevent a
fine control of the SELinux label / context that you would like
to apply on them
* This commit adapts the dlt-daemon in such way:
- application and control sockets are now created inside
/dev/socket which is the standard path for sockets on android
- these sockets are now created by init (see dlt-daemon.rc) and
their fds are recovered by dlt-daemon through a specific android
API (dlt_daemon_unix_android_get_socket). If the fds can't be
recovered, we fallback to the previous mechanism by creating
by ourself the sockets (even if this will prevent SELinux
label / context on this socket)
- all these modifications have been put under compilation flag
for android
Signed-off-by: Sebastien RAILLET <sebastien.raillet@marelli.com>
Diffstat (limited to 'automotive-dlt-c++.pc.in')
0 files changed, 0 insertions, 0 deletions