Martin-Éric RACINE
Martin-Éric RACINE
That still doesn't tell us which one is which or what configure keys to use for either case.
The variables' name remains opaque. It leaves downstream guessing. `--with-hooks="timesyncd.conf"` ...apparently results in: `HOOKSCRIPTS = 50-timesyncd.conf` I emphasize **apparently** because it I wouldn't have known without experimenting with the configure...
Looking into the source code for dhcpcd-run-hooks, I notice: ``` for hook in \ @SYSCONFDIR@/dhcpcd.enter-hook \ @HOOKDIR@/* \ @SYSCONFDIR@/dhcpcd.exit-hook do ``` Could this possibly be converted to: ``` for hook...
Let's ask @DanielG since he's the one who initially requested this.
> packages can drop their stuff into /libexec/dhcpcd-hooks or where-ever Debian installed the hooks and example hooks to. /etc/dhcpcd is solely for the administrator, not packages. Infact, do we even...
1) We need separate enter/exit directories because packages install separate scripts depending on what they need done when the network is brought up or down, and thus need separate directories...
Could this be rebased with master?
@Sime-Zupanovic Does the 10.3.0 that was released a few days ago fix the issue?
In all of them. I would treat aes192-ctr the same as ssh-audit currently treats cert-v01 variants as merely nice to have.
The point is that a policy should fail just because the 192-bit variant was omitted.