this post was submitted on 25 Jun 2024
39 points (95.3% liked)

Selfhosted

39365 readers
453 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 1 year ago
MODERATORS
39
NAS vulnerabilities (www.theregister.com)
submitted 3 months ago* (last edited 3 months ago) by Cyber@feddit.uk to c/selfhosted@lemmy.world
 

Just stumbled across this (overly dramatic?) article and thought I'd just post it here...

It's more to act as a reminder that if you've got a NAS that is serving content to the interwebs, then make sure it's behind a proxy of some kind to prevent weaknesses (ie in the management Web UI) being exposed.

Obvz, this article is pointing to Zyxel, but it could be your DIY home-built NAS with Cockpit: CVE-2024-2947 - just an example, not bashing that project at all.

I've used Squid and HAProxy over the years (mostly on my pfSense box) - but I'd be interested to know if there's other options that I've not heard of

top 11 comments
sorted by: hot top controversial new old
[–] schizo@forum.uncomfortable.business 16 points 3 months ago (2 children)

As someone who isn't a fan of e-waste, I really hate these little "appliance" type NASes. Companies abandon them while they're still perfectly usable and meeting someone's needs, and tell you oh sorry, I guess you should buy a new one and throw your current one away. (Which, annoyingly, the article also does.)

[–] HumanPerson@sh.itjust.works 2 points 3 months ago (1 children)

I agree, though I wouldn't blame the article. If it is insecure, you shouldn't be using it unless it is set up to allow you to run a real os on it.

[–] schizo@forum.uncomfortable.business 7 points 3 months ago (1 children)

I mean I'm not blaming anyone other than the manufacturers who make things and then arbitrarily decide to stop supporting them while they're still perfectly usable, leaving basically no choice other than trashing and buying a new one.

[–] Cyber@feddit.uk 3 points 3 months ago

Agreed.

If the hardware's standard, then it's possible for people (us) to keep these things out of the ground / incinerator for a few more years, but if it's custom / proprietary stuff, then that's just terrible.

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

Totally agree! Also, at work we have some Synology and their web UI is soooo slow that it's almost unusable

[–] Moonrise2473@feddit.it 15 points 3 months ago (1 children)

I had one of those NAS (NSA320). Even when they were new and suppoted they were using some ancient custom version of linux with ancient packages. It would be insane to expose them on the internet.

[–] zer0squar3d@lemmy.dbzer0.com 1 points 1 week ago

Yeah, I actually finally got rid of mine a year ago, but it never was allowed to access the Internet. Also didn't support smbv3 when those huge issues came out so has to use custom package sources to get updates. Never buying something unless it can have open source firmware flashed any time for my NAS hardware. Using TrueNAS now on slightly old custom built PC I upgraded from.

[–] mhzawadi@lemmy.horwood.cloud 4 points 3 months ago (1 children)

Depending on the login flow, I have a lot of stuff behind an oauth proxy. So that you have to have a working 2fa account to see the non 2fa system behind.

[–] Cyber@feddit.uk 4 points 3 months ago (1 children)

I must get around to looking into 2FA / MFA sooooon (next ~5 years)

Did you find it really straight forward to get setup?

I think the fear of getting started with these things is sometimes worth it (home system offline for days) but often it's quite simple...?

[–] mhzawadi@lemmy.horwood.cloud 2 points 3 months ago

It is very simple, I run it from docker and it can plug into all sorts of places, I have nginx config that I could share if it helps.

This is the tool https://oauth2-proxy.github.io/oauth2-proxy/

[–] Decronym@lemmy.decronym.xyz 1 points 3 months ago* (last edited 1 week ago)

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

Fewer Letters More Letters
HTTP Hypertext Transfer Protocol, the Web
NAS Network-Attached Storage
nginx Popular HTTP server

2 acronyms in this thread; the most compressed thread commented on today has 3 acronyms.

[Thread #831 for this sub, first seen 26th Jun 2024, 05:55] [FAQ] [Full list] [Contact] [Source code]