Re: Simplifying Support of Virtual and System Users

2022-03-29 Thread Patrick Domack
I just use all virtual user accounts. these virtual users have a flag that I set, if I want that account to be a system account, for things such as ssh/shell/... usage. But a single user registry makes things much simpler than having several, and then attempting to integrate them into a sin

Re: Simplifying Support of Virtual and System Users

2022-03-29 Thread Nikolai Lusan
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, I do have a solution for this - one which you probably don't want to hear ... I keep all email separate from system accounts, for any system accounts that are going to generate, or receive email I alias them. On Sat, 2022-03-26 at 17:32 +,

Re: Simplifying Support of Virtual and System Users

2022-03-28 Thread Sami Ketola
> On 26. Mar 2022, at 19.32, Mark Olbert wrote: > > Apologies if this has already been raised here (which I suspect it has 😊). I > tried to raise it as an issue over on github but issues are not enabled for > the repository. > > The support for mixing virtual users, with fully-qualified ema

RE: Simplifying Support of Virtual and System Users

2022-03-28 Thread Marc
> > > The support for mixing virtual users, with fully-qualified email > addresses, and system users could be simpler. Assuming it doesn’t mess > up other stuff in the code base, of course 😊. > You can define multiple passdb's not? > > The problem appears to be that the PAM passwd module requ

Simplifying Support of Virtual and System Users

2022-03-28 Thread Mark Olbert
Apologies if this has already been raised here (which I suspect it has 😊). I tried to raise it as an issue over on github but issues are not enabled for the repository. The support for mixing virtual users, with fully-qualified email addresses, and system users could be simpler. Assuming it doe