Johannes Meixner

https://github.com/rear/rear/issues/3186#issuecomment-2026899680 shows at least what Dell hardware it is

In https://github.com/rear/rear/issues/3285#issuecomment-2244545130 I wrote ``` I won't try to mitigate that now based on guesses about a software that I neither have nor know about i.e. DUPLICITY with BACKUP=DUPLICITY. ```...

@loyeyoung great that you responded! FIY first my generic "boilerplate" regarding third-party backup tools: ``` In general regarding third-party backup tools: Usually we at ReaR upstream do not have or...

For ReaR 2.8 I will now clean up things with sourcing DUPLY_PROFILE_FILE for BACKUP=DUPLICITY to get that code reasonably simple and straightforward which will make that stuff reasonably secure to...

Sourcing files in ReaR does not escalate privileges because usr/sbin/rear runs already as 'root'. But sourcing files in ReaR that are not trustworthy to be executed by 'root' is the...

@loyeyoung regarding testing my current changes, see https://github.com/rear/rear/pull/3345#issuecomment-2491107351

With https://github.com/rear/rear/pull/3345 merged this issue should be sufficiently mitigated for now, cf. https://github.com/rear/rear/issues/3293#issuecomment-2491085941

@loyeyoung with https://github.com/rear/rear/pull/3345 merged my DUPLICITY code changes are in GitHub master code so for testing it you do no longer need to do a ``` git checkout jsmeix-source-DUPLY_PROFILE ```...

@tolimar FYI to avoid expectations that I cannot fulfill: I am not a booting expert and I know basically nothing about POWER architecure specific things - I only know that...

My pleasure! I wish you a relaxed and recovering weekend.