Almost every program that we run has access to the environment, so nothing stops them from curling our credentials to some nefarious server.

Why don’t we put credentials in files and then pass them to the programs that need them? Maybe coupled with some mechanism that prevents executables from reading any random file except those approved.

  • Max-P@lemmy.max-p.me
    link
    fedilink
    arrow-up
    29
    ·
    1 year ago

    I have a rule that credentials in environment variables are to only ever be loaded as needed via some sort of secrets manager, optionally adding a wrapper script to do so transparently.

    The whole point of passing secrets as environment variables is to avoid having things in files in plain and in known locations easy to scrape up by any malware.

    Now we have people going full circle and slapping those into a .env file.

    • selawdivad@lemm.ee
      link
      fedilink
      arrow-up
      3
      ·
      1 year ago

      But how do you authenticate to your secret manager? How do you prevent evil scripts from also doing this?

    • _e____b@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      I’d be very thankful for an example of your setup. I’m using Bitwardern for browser-related password management, but for convenience scripts I load the credentials as env vars at login through .bash_profile 😅

      • Max-P@lemmy.max-p.me
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        Basically just have each sets of credentials in a script, and whenever you need to use something that needs a key, you source the script you need first.

        Then each of those scripts are something like

        export MY_API_KEY="$(bw get password whatever)"