ansible, golang, R
#automateallthethings
Personal: https://pat-s.me
Business: https://devxy.io
go version -m
and
govulncheck -mode=binary -show verbose <binary>
that perfectly verify and do what I was searching for.
Confirmed the findings of Trivy & MS Defender
go version -m
and
govulncheck -mode=binary -show verbose <binary>
that perfectly verify and do what I was searching for.
Confirmed the findings of Trivy & MS Defender
I am in a weird spot where multiple scanners flag (multiple) binaries, the company says "nothing there, error on your (scanner) side" and I need to report to the sec team with 2:1 scanners in favor of the vuln being present.
I am in a weird spot where multiple scanners flag (multiple) binaries, the company says "nothing there, error on your (scanner) side" and I need to report to the sec team with 2:1 scanners in favor of the vuln being present.
I am somewhat skeptical about this argument. What are my best chances to find a verifiable proof to this (other than attempting to exploit the vuln?)
I am somewhat skeptical about this argument. What are my best chances to find a verifiable proof to this (other than attempting to exploit the vuln?)
- Non-admin users can now see all instance agents in a fully redesigned agent list view
- Docs now contain a feature comparison list to #woodpeckerci (www.crowci.dev/3.7/index.ht...)
- Scrolling to selected pipelines steps now works for shared links
- Support for dynamic page titles
- Non-admin users can now see all instance agents in a fully redesigned agent list view
- Docs now contain a feature comparison list to #woodpeckerci (www.crowci.dev/3.7/index.ht...)
- Scrolling to selected pipelines steps now works for shared links
- Support for dynamic page titles
Sometimes it is time for change. Maybe we arrived at such a moment ;)
Sometimes it is time for change. Maybe we arrived at such a moment ;)
r-project.org is not in scope for the TLD as CRAN is not interested in the project (and probably sees it as competition?). I asked them some time ago to possibly collaborate, specifically for the Alpine binaries.
r-project.org is not in scope for the TLD as CRAN is not interested in the project (and probably sees it as competition?). I asked them some time ago to possibly collaborate, specifically for the Alpine binaries.
Due to some other (related) philosophies, such as not using any cloud service and self-hosting hardware, uptime and service availability has not always been great in the past.
And in general, it's always good having multiple alternatives ;)
Due to some other (related) philosophies, such as not using any cloud service and self-hosting hardware, uptime and service availability has not always been great in the past.
And in general, it's always good having multiple alternatives ;)
I personally have some projects on Codeberg.
I am also currently working on a public Forgejo-based platform, which will also be open for companies (as CBs ToS are very strict). Beta will be available soon.
I personally have some projects on Codeberg.
I am also currently working on a public Forgejo-based platform, which will also be open for companies (as CBs ToS are very strict). Beta will be available soon.