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!

  • quick_snail@feddit.nl
    link
    fedilink
    English
    arrow-up
    0
    arrow-down
    1
    ·
    edit-2
    12 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.zip
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      12 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?

      • quick_snail@feddit.nl
        link
        fedilink
        English
        arrow-up
        0
        arrow-down
        2
        ·
        13 days ago

        Checksums are not for security. You need signatures. I’m not making claims that aren’t clearly documented.