Dimitri Papadopoulos Orfanos

I had a look at the [openresolv package for Fedora 36:](https://packages.fedoraproject.org/pkgs/openresolv/openresolv/fedora-36.html), indeed it does not provide executables: ``` $ rpm -qlpv ./openresolv-3.12.0-3.fc36.noarch.rpm [...] -rw-r--r-- 1 root root 0 Jan 20...

The whole point of **resolvconf**, whether the [original Debian implementation](https://salsa.debian.org/debian/resolvconf) or the [openresolv](https://roy.marples.name/projects/openresolv/) one, is to do the right thing. My understanding is that it knows when to modify `/etc/resolv.conf`...

I know that since Fedora 36, the DNS entries added to `/etc/resolv.conf` are ignored. What I do not know, is whether `resolvconf` only modifies `/etc/resolv.conf`. I was under the impression...

Yes, the Fedora package needs to be fixed with that respect. I suggest you add comments about the Fedora package to this existing open issue: https://bugzilla.redhat.com/show_bug.cgi?id=2024565

I'll have a closer look at [Unity](http://www.throwtheswitch.org/unity) unless you have other suggestions.

> Now good question is how i should deal with coding style for ifaddrs.c? Just skip the file when testing, see [`run.sh`](https://github.com/adrienverge/openfortivpn/blob/master/tests/lint/run.sh).

Ah, after changing from Travis CI to GitHub Actions, we do not use `tests/lint/run.sh` any more, see [`.github/workflows/openfortivpn.yml`](https://github.com/adrienverge/openfortivpn/blob/master/.github/workflows/openfortivpn.yml). Thinking about it, it's a confusing regression: manual checks and GitHub Actions...

Dependabot creates **merge requests**, whether to update GitHub Actions or to update other dependencies. These are **not** fully automatic updates. [Keep all your packages up to date with Dependabot](https://github.blog/2020-06-01-keep-all-your-packages-up-to-date-with-dependabot/)

Dependabot is not a GitHub Action as far as I can tell. Strictly speaking, you wouldn't be giving write access to a GitHub Action. But I get the idea. Fortunately,...

I was merely referring to permissions as a way to mitigate the risk of running 3rd party GitHub Actions. However, Dependanbot is not a GitHub Action, so GitHub Actions permissions...