• Ignotum@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    27 days ago

    I remember when a senior developer where i worked was tired of connecting to the servers to check its configuration, so they added a public facing rest endpoint that just dumped the entire active config, including credentials and secrets

    That was a smaller slip-up than exposing a database like that (he just forgot that the config contained secrets) but still funny that it happened

    • PattyMcB@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      27 days ago

      That’s not a “senior developer.” That’s a developer that has just been around for too long.

      Secrets shouldn’t be in configurations, and developers shouldn’t be mucking around in production, nor with production data.

      • Ignotum@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        26 days ago

        Yeah the whole config thing in that project was an eldritch horror of a legacy, too ingrained in both the services and tooling to be modified without massive rewrites