On Wed, 9 Aug 2023 01:13:40 +0000
"Gu, Jay" <j...@sap.com> wrote:
> I'm running the R within docker container.
In that case (depending on the way the container is set up, of course),
your /etc/passwd shouldn't even be a privacy concern. It's most likely
identical that in other containers running R. You can read it yourself
(either by getting a separate shell inside the container or by running
readLines("/etc/passwd")) and check for identifying information. There
should be no harm in letting an R package read it.
If you are curious to know which part is trying to access it, we still
need a backtrace at the point where AppArmor crashes the process,
either from a core file or from a live process. (Other techniques are
fine too, but setting conditional breakpoints on open() and openat() is
more involved.)
--
Best regards,
Ivan
______________________________________________
R-help@r-project.org mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
