Vincent Riesop

``` NEEDRESTART-KCUR: 6.5.0-1015-azure NEEDRESTART-KEXP: 6.5.0-1015-azure crun version 0.17 ```

using the `runs-on: ubuntu-latest` in github actions will resolve to Ubuntu 22.04 (Jammy Jellyfish) This indeed has run 0.17 https://packages.ubuntu.com/jammy/crun

We have this issue on a bootstrap stage (arm64 only) build pipeline for the PR #1962 https://github.com/gardenlinux/gardenlinux/actions/runs/8110179750/job/22166892875?pr=1962 This PR is rebased and contains commit from #1982

Workaround is for amd64 only, right? Looks like this setup action is skipped here https://github.com/gardenlinux/gardenlinux/actions/runs/8110179750/job/22166892875?pr=1962 anyway 🤔

fyi: Fail2ban is back in testing https://tracker.debian.org/news/1515355/fail2ban-102-3-migrated-to-testing/

maybe we can use https://man.openbsd.org/sshd_config#PerSourcePenalties

Hi @fwilhe, sorry I could not find a good solution yet and forget to follow up on it. This is a general issue, and I think for this to work...

@nkraetzschmar added `strace` https://gitlab.com/gardenlinux/gardenlinux-package-build/-/merge_requests/378 I will test tomorrow

Unassigned myself. We discussed it a bit in chat. I would say we need to document what we have discussed: - pin priority handling - recommended settings if you add...

garden-feat does not exist anymore in favour of the [parse_features](https://github.com/gardenlinux/builder/blob/main/builder/parse_features) from the new builder. If I understand the [gardenlinux/tests/local/test_garden_feat.py](https://github.com/gardenlinux/gardenlinux/blob/34bb8c96fcda3c53a5573e320ab5534141915c6e/tests/local/test_garden_feat.py#L1) test correctly, it tested if the garden_feat script reduced the cname...