Let’s say I self-host something like wefwef (Lemmy front end) locally, so I can see it on http://localhost:port on the machine where it’s running with Docker, and also on my other devices on my same local network by accessing http://192.168.something.something:port
Now, if I were to input my login credentials on that (so without HTTPS), how dangerous is this?
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
Your LAN router/switch will see the credentials unencrypted. An untrusted device on your network could perform ARP spoofing, pretend to be
192.168.something.something
, and intercept the credentials. Do you trust all devices on your network?It’s better practice (and simple enough) to setup HTTPS with self-signed certificates and have the browsers manually accept the cert on first connection.
I do trust the devices on my network but I guess I’ll probably look into how to setup HTTPS.
deleted by creator
IMHO, HTTPS is not necessary in a small home network.
deleted by creator
deleted by creator