Christian Buhtz

> because while trying to restore the data (having uid=1000) to my account (with uid=1001), I tried "BiT root mode" and it modified my {/home , /home/$USER/ , /home/$USER/.config, etc.}...

Again I struggle to reproduce the problem. When I try to modify a config not owned by my current user BIT gives a proper error message about missing permissions. So...

Interesting. Can't we just handle the path like it is done in the none-root start script? https://github.com/bit-team/backintime/blob/34359ca72e29f944dd6cfff9380aa1404c6bac26/common/backintime#L20-L27 **EDIT**: I don't like having to much labels but isn't it a good...

Fixing #1575 will make this problem go away. Put this Issue on-hold.

#1575 won't get solved in the next year(s). 😄 So what else can we do? I read the thread but I don't get every detail. Maybe someone can scetch up...

It would really be a valid and valuable contribution if someone would summarize the issue and suggesting a reasonable solution.

This is a security related issue. Because of that I take it really serious. Without understanding all details I am not willing to modify anything and risk to introduce more...

Thank you very much. I appreciate your contributions. The test is failing on TravisCI because it waits for a passphrase entered by a user. Do you have any idea about...

> Is there a way to enable debug logs in Travis? Not sure. I'll try. # EDIT Got it. `-s` is the option. ``` $ pytest test/test_sshtools.py::General::test_unlockSshAgentKeyWithPassword -s ============================= test...

Hello David, Thank you for analyzing this. > I can replicate the failure with `unset DISPLAY`. Makes sense somehow. When running regular BIT (not the tests) on a headless server...