On 24/07/2022 20:56, Johannes Löthberg wrote:
Excerpts from David Runge's message of July 23, 2022 18:38:
Currently the timer which triggers this service is supposed to be vendor
enabled (i.e. symlink in /usr/lib/systemd/system/timers.target.wants/)
and run daily with a deviation of up to 12h.
M
On 2022-07-24 10:53:24 (-0700), Brett Cornwall wrote:
> Just wanna point out that just because we already do something it
> doesn't validate doing a similar thing. :)
No. That was not the point I was trying to make. :)
It serves as a good example as to why such a thing does not have to be a
privac
On 2022-07-24 21:56:28 (+0200), Johannes Löthberg wrote:
> I'm fine with it existing, and I would be fine with it being enabled
> in a vendor preset, but I'm against it being statically enabled in
> /usr. This is not something that's critical for the regular
> functioning of the system, and so is
On 2022-07-25 09:23:53 (+0100), Leonidas Spyropoulos wrote:
> I'm aligning probably against such systemd unit. Mainly because or
> privacy issues and given the options users will probably set something
> like refresh every 1 hour and then we need to go into rate-limiting
> just to keep our gitlab u
On Sat, 2022-07-23 at 18:38 +0200, David Runge wrote:
> Hi all,
>
> I currently have a MR open against archlinux-keyring [1], that adds a
> systemd service and timer, which would automatically refresh valid and
> existing keys on user systems. For people without access to the
> repository's ticket
