hansdaniels

I've written a small Rust program which only calls `which`: ```rust use std::env; use which::which; fn main() { let args: Vec = env::args().collect(); if args.len() < 2 { println!("executable as...

`$PATH` has nothing to do with this, I've added a hardcoded check for `/usr/bin/tedge_mapper` and neither is this found by `tedge`

After some further analyses, we found out that a symlink alone is not the problem. It has to do with permissions. We're running `tedge` as root confirmed by: ```rust use...

I think I've found the reason. It's in ```rust let _user_guard = user_manager.become_user(tedge_users::TEDGE_USER)?; ``` This boils down to ```rust pub fn switch_user_group(uid: uid_t, gid: gid_t) -> io::Result { ... set_effective_gid(gid)?;...

Do I understand your reduction wish correctly if I rephrase it as follows? > `tedge` should write configuration files of itself and the various cloud connectors and mappers, but not...

Regarding the user&group handling: To my eyes, the current way is both too lax and too restrictive at the same time. Too lax, because `root` doesn't drop all capabilities (supplementary...

I like the idea of customizable "reload" commands 👍