Different ways to invoke and execute bash

zeebra · 06-09-2022, 04:12 AM

Quote:

Originally Posted by pan64

there is no other way to start a process, but clone/fork and exec.
Subshell is just a new [bash] process started by the parent process.

Well, the I would recommend that you give auditd a go to check for youself. Like I said, context matters and how you invoke exec and this execute bash. Results vary widely as well, and I even gave you a practical example.

A simpler example if you don't know what I'm talking about is cgexec.

pan64 · 06-09-2022, 04:21 AM

so you want to examine cgexec? That is a quite different things. You need to pay attention to at least these two things:
1. what (app/process/binary) is executed or started
2. how is it started (= what environment is used to start it)

zeebra · 06-09-2022, 02:30 PM

Quote:

Originally Posted by pan64

so you want to examine cgexec? That is a quite different things. You need to pay attention to at least these two things:
1. what (app/process/binary) is executed or started
2. how is it started (= what environment is used to start it)

Why are you just arguing and being difficult? Perhaps a more constructive approach would give you more joy?

zeebra · 06-11-2022, 06:30 AM

It might be useful to add these concepts in this thread:

Sandboxing Applications with Landlock (OSS 2021):
https://www.youtube.com/watch?v=ohoofZ62O98

In particular there is a section addressing how this could work for shells and nested shells, which might be interesting to some.