Morten Linderud

Weird! I assume something has broken here https://gitlab.archlinux.org/archlinux/archlinux-docker/-/blob/master/Dockerfile.template#L27

Should be fixed in future builds of the image, which should be daily. https://gitlab.archlinux.org/archlinux/archlinux-docker/-/commit/74dc761af835b7fe091db387c5cdca472813dc6c

Not super odd really. Fedora Rawhide and OpenSUSE Tumbleweed also do this with their container images. And part of the idea is to have an indicator when it was built.

I think we should go over all possible verbal ways of defining a syntax. We might be missing other functions aswell. When it comes too the Not method: :shipit:

I disagree with calling it "Verbose", we are essentially just making regex verbal, where you can "speak" or pronounce a regex without sounding wierd. It obviously means it will be...

- [x] Ruby gems `strong_password` https://withatwist.dev/strong-password-rubygem-hijacked.html - [ ] Canonical Github repo compromised - https://github.com/CanonicalLtd (need more sources i reckon) - [ ] Pale moon archive server - https://www.bleepingcomputer.com/news/security/hackers-infect-pale-moon-archive-server-with-a-malware-dropper/

@dkwo fwiw, the config file is the internal defaults `sbctl` will use if there is no config file. It will also merge the internal state with the `/etc/sbctl/sbctl.conf` file if...

After the initial documentation is done we could also try figure out which providers use which format as a form of example.

Right, that was another thing we should document. But I was more thinking of pointing at which standard are in use where. As an example Red Hat uses CVRF 1.2...

A Github ID does not accomplish the same thing, and it's extremely important to realize. There is a security framework built around having one agreed upon way to communicate vulnerabilities....