sorted by: new top controversial old
Container Vulnerability Management in c/selfhosted@lemmy.world
Container Vulnerability Management in c/selfhosted@lemmy.world
[–] [S] 5 points 2 days ago*

PHP hardened (distroless) images

That's a good point, maybe I'll change that at some point. The reason, haven't done so yet is that I wanna have the whole supply chain under my control. And know exactly what has been changed since a release.

Why build your own images at all?

Because of different reasons:

  • Flexibility: I can modify a container to my needs.
  • Trust: I don't wanna rely on something that I don't have under control. An image might contain some breaking changes in the next version, and that could cause me problems when I apply them.
  • Learning: By doing everything myself I learn about how to do it.
  • permalink
  • fedilink
  • source
  • parent
  • context
    • 2
    47 Networks, 68 Seconds (nheinz.eu)
    submitted 1 month ago by [M] to c/honeypot@infosec.pub
    comment fedilink
     

    47 different chunks of the internet, each a full /24 block of up to 256 addresses, started scanning my infrastructure within 68 seconds of each other. 47 entire networks, most of them belonging to a single hosting provider. 6 months of logs turned up more than a dozen of these synchronized waves, and at least 3 of them weren't one-time events. The same operators came back days later and ran the exact same target list again, like clockwork.