From fbee580da0f06b3d375c12438858fae25827aab6 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Sun, 17 Mar 2019 11:18:57 -0400 Subject: comment --- ...comment_1_794b11f84e0dcb29eba36bdfe1220191._comment | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/forum/Support_writing_as_owner__63__/comment_1_794b11f84e0dcb29eba36bdfe1220191._comment (limited to 'doc/forum/Support_writing_as_owner__63__') diff --git a/doc/forum/Support_writing_as_owner__63__/comment_1_794b11f84e0dcb29eba36bdfe1220191._comment b/doc/forum/Support_writing_as_owner__63__/comment_1_794b11f84e0dcb29eba36bdfe1220191._comment new file mode 100644 index 00000000..8edcefaa --- /dev/null +++ b/doc/forum/Support_writing_as_owner__63__/comment_1_794b11f84e0dcb29eba36bdfe1220191._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2019-03-17T15:13:20Z" + content=""" +If propellor could fork and then setuid, that would allow this. But.. + +* forking is problimatic in haskell since the RTS state gets shared + and bad things happen +* the result of the setuid action would need to be communicated back to the + main process somehow + +The other way would be to re-exec propellor as the user +with a parameter that somehow tells it what action to run. But I don't know +a general way to do that, without some way to name the property. +(A problem which has also complicated some other parts of propellor eg +running inside chroots.) +"""]] -- cgit v1.2.3