Peter Bex

As I pointed out in [#4675](https://github.com/jeremylong/DependencyCheck/issues/4675#issuecomment-1187359752), I believe the [RipudamanKaushikDal/projects repo](https://github.com/RipudamanKaushikDal/projects/issues/21#ref-issue-1306427775) is the main culprit, matching an overly generic name "projects". In our project at work, we use a dependency...

We're using this suppression, which should be general-purpose enough for anyone: ``` cpe:2.3:a:projects_project:projects:*:*:*:*:*:*:*:* CVE-2022-31569 ```

> > That may be true, but CVE-2022-31514 for instance is not. > > True, sorry. What a mess this guy create...sigh. The CVE process is surprisingly ill-prepared to deal...

A binary in the package repos would be great, especially if you see how many people are having trouble compiling it.

It's June now, and still no official release. I find this really frustrating; many people reporting that the application obviously is working, yet @hlandau is MIA. One of the reason...

I need CentOS (and also plain Debian) packages, not Ubuntu ones. But making it an official release instead of a beta version would definitely signal to package maintainers that it's...

I also just noticed that if you bring up one box and then halt it again, the corresponding entry in `/etc/exports` isn't removed (for either provider). Not sure if that's...

Thanks for replying so quickly! My initial approach looked like this, but I thought it would be cleaner to annotate the options of `:map` with the exclusive keys, as it...

This is quite an issue for us too. We have a background task that synchronises information with Exact Online, but due to the token becoming outdated, the user needs to...

> If the problem is that changes in the spec made the diagrams invalid and it was too much work to update all those detailed diagrams, I understand that. I...