I setup an example where a service is expecting a secret to be
available in its user's persistent keyring. It can crash and restart
or maybe it is a timer and it does not want to bother asking/reading
secrets.
It works, but I hoped to be able to remove access to the secret from
the user that had
On Mo, 24.12.18 23:23, Pratyush Das (reik...@gmail.com) wrote:
> OS - Gentoo
> Kernel - 4.14.83-gentoo
> My laptop is an optimus laptop if that is relevant.
>
> Configuration-
> reik@localhost ~ $ systemctl --version
> systemd 239
> +PAM -AUDIT -SELINUX +IMA -APPARMOR +SMACK -SYSVINIT +UTMP
On So, 23.12.18 02:17, Reindl Harald (h.rei...@thelounge.net) wrote:
> http://0pointer.net/blog/ip-accounting-and-access-lists-with-systemd.html
>
> "All traffic from and to this address will be prohibited for processes
> of the service" is nice in theory but let's say we have a internal
>
Am 27.12.18 um 12:38 schrieb Lennart Poettering:
> On So, 23.12.18 02:17, Reindl Harald (h.rei...@thelounge.net) wrote:
>
>> http://0pointer.net/blog/ip-accounting-and-access-lists-with-systemd.html
>>
>> "All traffic from and to this address will be prohibited for processes
>> of the service"
