Hi guys, I’ve been working on a self-hostable web analytics platform since the start of this year after being frustrated with Google Analytics and Plausible.

I’ve packed a bunch of cool web analytics features into Rybbit, but I’ve tried very hard to keep the interface simple to use,

https://github.com/rybbit-io/rybbit

Check it out!

  • partofthevoice@lemmy.zipEnglish
    0·
    6 days ago

    Docker is a security risk? … excuse me, what? Can’t you just, idunno, secure the environment that docker runs in? Use rootless images? Use immutable images?

    And, are you asking for something that runs on bare metal? Couldn’t you just install the ISO that the dockerfile uses, then convert the dockerfile logic to an sh script?

      • partofthevoice@lemmy.zipEnglish
        0·
        6 days ago

        You can verify the checksum to ensure the contents pulled are exactly the same as what was published. You can also use a private container registry.

        How exactly would docker pull be any more insecure than something like pip install? Or, really anything… Let’s go with your preferred alternative, how are you going to get it on your machine in a more secure way than docker provides?

        Docker uses TLS with registries, layers and manifests have cryptographic digests, checksums, and you can verify the publisher yourself. Push it into your own registry if you want, or just don’t use latest.

        • quick_snail@feddit.nlEnglish
          0·
          6 days ago

          Yeah, that’s the insecurity I’m talking about.

          If you want to know how to implement this properly, look at apt. Its a known issue in docker; they just haven’t prioritized the fix yet (DCT)

          • partofthevoice@lemmy.zipEnglish
            1·
            6 days ago

            What are you talking about, “yeah that’s the insecurity I’m talking about.”

            I didn’t mention an insecurity and neither have you. Would you mind being a little more clear than “Docker pull is insecure?”

            Frankly, I was expressing confidence in dockers security. It goes without saying though, any user can do insecure things like download from untrusted sources. That’s not dockers problem though, it’s the users.

            Edit: I see now that you added “it’s the download that’s not verified.” Integrity is verified, so I assume you mean authorship (via signing)? I guess you’re saying that, if admin credentials are stolen from a container publisher and the thief force pushes malicious code into the registry under a pre-existing tag—then you would be exposed to that?

            Even in that case, though, a digest cannot be overwritten. Tags can. So you’d just pin the digest to avoid this one attack vector?