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.
@dessalines@lemmy.ml @nutomic@lemmy.ml 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.
The funny part about this post is that @dessalines@lemmy.ml literally will not post on this instance (or most instances besides the tankie triad) because he is a coward.
spits on @dessalines@lemmy.ml
You speak truth, and the proof is that coward will not even aknowledge this news. Mark my words… tankies are just fascists of a different degeneracy.
They did acknowledge and fix it.
They didn’t acknowledge it. They just silently fixed it (or, someone did, at least).
They’re not obligated to come in here and get yelled at, of course, and what would it accomplish. But, on the other hand, it is relevant that they can’t handle being in any environment where people can just speak freely to them, and respect is earned rather than demanded by force. There’s a certain type of mentality that just can’t cope with being in any role other than “the boss” and being able to talk down to or punish whoever they want, with no one allowed to express anything other than respect and obedience in the other direction. That is, in fact, the exact mentality that makes people suspicious of this otherwise maybe innocent issue with the software.
They responded to the pull request saying “good catch, thanks”
If there’s one tribal degenerate here it’s you my friend. They fixed this minor issue that’s been turned into a big conspiracy by you degenerate while there’s 0 actual consequence or admin saying they’ve been hacked. Please get away from internet, speak to people in real life and come back when you’re socially adpated.