Maxime Dirksen
Maxime Dirksen
And the 3.2.0 of `linux-enable-emitter` will support multiple infrared camera configuration. (I don't know if it is possible with Howdy, but in case it will be fine)
> Isn't it risky though to use an environment variable to get the library path? An attacker would just have to override the variable to point to a script which...
Workflow test fixed in 0bc0c2c3681b626805365fdacd58002d5b60e6e0 Edit: there is a way to know if the test will pass before pushing on GitHub ?
But I mean, is there any reason to talk about PAM at user level? Since the module is (I think) executed at root level. And because howdy's env variable is...
> Instead, you should use meson's configure_file() to define that path while setting up meson, and replacing @HOWDY_LIB@ in the files with the correct path during the build. Not only...
Yes it is a good idea to use meson, but `howdy_gtk` which is another package needs to access to the howdy's files. Here I have only created one variable, but...
Although, I agree that if we can do without using environment variables, we might as well do it.
> ... can be configured with -Dpam-securitydir=/lib/security, just like this package can be. But how it can know where is installed Howdy because it is installed before. Ok, the maintainer...
> Why is this a bad thing? :) An update of the main package could break the others
The problem is not about where is installed the howdy's pam module (and anyway we don't need to know), but about where are `compare.py`, `models/`, `config.ini` and `dlib-data/`