this post was submitted on 19 Mar 2024
131 points (92.3% liked)

Selfhosted

40767 readers
1828 users here now

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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
131
My stupidity saved me from being hacked today! (lemmy.giftedmc.com)
submitted 9 months ago by [email protected] to c/[email protected]
53 comments fedilink hide all child comments
 

I know, I know, clickbaity title but in a way it did. It also brought in the situation in the first place but I'm just going to deliberately ignore that. Quick recap:

  1. I came home at 3pm from the city, my internet at home didnt work.
  2. checked multiple devices, phones worked out of wifi, I figured I need to restart the router
  3. I login to the router and it responds totally normal but my local network doesnt. (Its always dns, I know)
  4. I check the router log and see 100s of login attempts over the past couple of days.
  5. I panic and pull the plug, try to get into my server by installing an old monitor, works, many errors about dns
  6. Wife googles with her phone, seems I had https login from outside on and someone found the correct port, its disabled now
  7. Obviously, local network still down, I replug everything and ssh into the server which runs pihole as dns
  8. pihole wont start dns, whatever I do
  9. I use history and find I "chmod 700"ed the dns mask directory instead of putting it in a docker volume...
  10. I check the pihole.log, nothing
  11. I check the FTL log, there is the issue
  12. I return it to 777, everything is hunky dory again.

Now I feel very stupid but I found a very dangerous mistake by having my lan fail due to a less dangerous mistake so I'll take this as a win.

Thanks for reading and have a good day! I hope this helps someone at some day.

top 50 comments
sorted by: hot top controversial new old
[–] [email protected] 95 points 9 months ago (1 children)

Did you expose your router login page to the open internet? How'd they get access? Why are you chmoding anything to be 777?

[–] [email protected] 11 points 9 months ago (2 children)

There was an option that I had enabled years before and forgotten so yes, I didnt know but it was, on some obscure port.

And yes, pihole in docker makes its files be 777 which is pretty disgusting, I know. Thats why I tried to make it 700 and broke my whole network.

[–] [email protected] 54 points 9 months ago (1 children)

Doubt. You probably need to set the file owners in your volume to the same user running in the container.

[–] [email protected] 22 points 9 months ago (5 children)

I think you are still learning... What you say doesn't make sense, so I think you may have misunderstood what happened.

load more comments (5 replies)
[–] [email protected] 41 points 9 months ago (21 children)

Wipe and start fresh

load more comments (21 replies)
[–] [email protected] 37 points 9 months ago (1 children)

777? Bruh just set the owner?

[–] [email protected] 18 points 9 months ago (2 children)

I'm referring you to my quick "self-hosting guide": https://lemmy.world/comment/7126969

[–] [email protected] 7 points 9 months ago

Thast awesome! Thanks! Bookmarked!

[–] [email protected] 1 points 9 months ago

Saved~~

[–] [email protected] 17 points 9 months ago (2 children)

One of my fears of starting up my homelab.

[–] [email protected] 35 points 9 months ago (2 children)

All you have to do to avoid this is just not open any ports except one for something like wireguard, and only access your network using it externally, and you will never have this problem.

[–] [email protected] 8 points 9 months ago

Exactly. It wasnt on purpose either. I thought there was an additional layer of security, gullible as I was 5 yrs ago. They made it seem like there was.

[–] [email protected] 6 points 9 months ago

Gotta have a firewall that closely resembles swiss cheese.

[–] [email protected] 1 points 9 months ago

One of my home servers was popped once, they stuck a new MOTD on there to let me know how foolish I was and I haven't made that mistake since. So... yay greyhat?

[–] [email protected] 9 points 9 months ago (2 children)

I’ve adopted a policy of always ebetering my password wrong the first time.

It started by accident.

[–] shiiiiiiiiiiiiiiiiiiiiiiiiiiiiiit 3 points 9 months ago (1 children)

Trying to work out why this is a good idea. Please could you explain why?

[–] [email protected] 4 points 9 months ago (1 children)

They can’t swipe your password if it’s wrong

They could of course enter it on the target website and see it’s wrong though, so this only works against the crappiest phishing attempts

[–] [email protected] 2 points 9 months ago

Except how are the swiping your password if it’s https? Unless your being phished but don’t see how that would help because they could just get your second password.

[–] [email protected] 1 points 9 months ago

This is very smart 😃 never thought about that

[–] [email protected] 5 points 9 months ago (2 children)

That's why I love Tailscale, nothing is open to the internet, all my shit is local lan inside Tailscale. Even better I don't have to bother with certificates and reverse proxy.

[–] [email protected] 4 points 9 months ago

Reverse proxy isnt that hard tbh. Btw I have a vpn and my lan isnt open to the web. The router vendor made it look like there was an additional layer of security.

[–] [email protected] 1 points 9 months ago (1 children)

Not sure how reverse proxy is avoided this way

do you enter port numbers for your services when you access them, or have one service per machine?

I have a few publicly accessible services, and a bunch of private services, but everything is reverse proxy'd

I find it very convenient, as for example I can go to https://wap.mydomain.net for my access point admin page, or photos.mydomain.net for my Immich instance. I have a reverse proxy on my VPS for public services, and another one on my lan for private services; WireGuard between VPS, LAN, and my personal devices. Possibly have huge security holes of course...

[–] [email protected] 1 points 9 months ago

Yep correct http://hostname:port por each application, all running in the same host on docker. The only thing it would be that any device that would want to connect to an app needs the Tailscale client. And would take over the VPN slot. That's why they offer exit nodes with mullvad and also DNS privacy resolvers like NextDNS.

[–] [email protected] 3 points 9 months ago* (last edited 9 months ago)

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

Fewer Letters More Letters
DNS Domain Name Service/System
Git Popular version control system, primarily for code
VPN Virtual Private Network
VPS Virtual Private Server (opposed to shared hosting)

4 acronyms in this thread; the most compressed thread commented on today has 11 acronyms.

[Thread #616 for this sub, first seen 20th Mar 2024, 00:15] [FAQ] [Full list] [Contact] [Source code]

load more comments
view more: next ›