So if you do the Docker setup, obeying the instructions and substituting everything that needs to get substituted, but don’t proofread the files in detail and so miss that line 40 of docker-compose.yml doesn’t have the variable {{domain}} like in every other location you need to write your domain, but instead just says LEMMY_UI_LEMMY_EXTERNAL_HOST=lemmy.ml and so you fail to change it away from lemmy.ml… then, everything will work, until you type in your admin password for the first time, at which point your browser will send a request to lemmy.ml which includes your admin username, your email address, and the admin password you’re trying to set. And, also, of course your IP address wherever you are sitting and setting up the server.

I have no reason at all to think the Lemmy devs have set their server up to log this information when it comes in. nginx will throw it away by default, of course, but it would be easy for them to have it save it instead, if they wanted to. And my guess is most people won’t use a different admin password once they figure out why creating their admin user isn’t working and fix it.

@[email protected] @[email protected] I think you should fix the docker-compose.yml file not to do this.

Edit: Just to increase the information-to-rudeness ratio of my post. The docs are at:

https://join-lemmy.org/docs/administration/install_docker.html

And they recommend using wget to download:

https://raw.githubusercontent.com/LemmyNet/lemmy-docs/main/assets/docker-compose.yml

Which is pulled from:

https://github.com/LemmyNet/lemmy-docs/tree/main/assets

Which is what has the wrong line 40 in it.

Edit: They fixed it. Good stuff.

  • PhilipTheBucket@ponder.catOP
    link
    fedilink
    arrow-up
    19
    arrow-down
    18
    ·
    edit-2
    22 hours ago

    Within the last hour, dessalines has posted three things about communism that are longer than the fix for this issue.

    Edit: Everyone’s got the right to do whatever they want to do. I’m not trying to accuse anyone of not spending enough time making software for me, just because occasionally they might want to do some other things with their life. The thing I’m trying to emphasize with this is how short the fix is. It’s seconds. It’s not one of those “but you have to recompile, what about this other branch” or anything like that. It’s literally a fairly critical security fix with 100% of the fix in a one-line change to a documentation file.

    • locuester@lemmy.zip
      link
      fedilink
      English
      arrow-up
      28
      arrow-down
      11
      ·
      22 hours ago

      Wow you typed a LOT to defend not making a GitHub issue. That energy redirected to writing a GitHub issue would be stellar.

    • dastanktal@lemmy.ml
      link
      fedilink
      arrow-up
      18
      arrow-down
      8
      ·
      22 hours ago

      Go fix it yourself. You’re correct that’s the admin’s problem but if you’re so insistent that it takes a minute go submit a merge request real quick.

      Also it’s only a security breach if you don’t change the admin password or your domain which should be standard for setting things up on the Internet anyway.

    • limer@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      18
      arrow-down
      8
      ·
      22 hours ago

      Why don’t you a pull request and fix it yourself ? If you have the ability to recognize and know what to fix, and if you care, do it!

      I know I’m too lazy to help them, what is your excuse ?

      I swear, I might just get off the fence and help them myself on unrelated issues, it’s making me that unsettled