• carrylex@lemmy.worldOP
      1·
      4 months ago

      Well from my personal PoV there are a few problems with that

      1. You can’t detect all credentials reliably, they could be encoded in base64 for example
      2. I think it’s kind of okay to commit credentials and configuration used for the local dev environment (and ONLY the local one). E.g. when you require some infrastructure like a database inside a container for your app. Not every dev wants to manually set a few dozen configuration entries when they quickly want to checkout and run the app
      • bleistift2@sopuli.xyzEnglish
        1·
        4 months ago

        You can’t detect all credentials reliably,

        Easy. You check in the password file first. Then you can check if the codebase contains any entry on the blacklist.

        Wait…

        • pfm@scribe.disroot.org
          1·
          4 months ago

          You were so close! The right solution is of course training an AI model that detects credentials and rejects commits that contain them!

          • MajorHavoc@programming.dev
            1·
            4 months ago

            I need one of those reminder bots, so I can share a link to an inevitable startup, six months from now, based on your humorous comment.

          • tyler@programming.dev
            1·
            4 months ago

            You joke, but GitHub advanced security does this and more. On top of the AI component, they check the hash of all things that look like an api key and then also check them against their integrated vendors to see if they’re non-expired. I don’t know how well it works, but they claim like a .1% false positive rate or something like that.

      • dohpaz42@lemmy.worldEnglish
        1·
        4 months ago

        I think it’s kind of okay to commit credentials and configuration used for the local dev environment (and ONLY the local one).

        No. Never.

        E.g. when you require some infrastructure like a database inside a container for your app. Not every dev wants to manually set a few dozen configuration entries when they quickly want to checkout and run the app

        In this situation, it would be better to write a simple script that can generate fresh and unique values for the dev.

        Laziness is not an excuse.