Hacker News Reader

Comment by jlawer | Hacker News Reader

The only thing worse is the tone deaf customer service responses. Such as: - Wanting root SSH access to someone's device to investigate? - Suggesting getting a higher spec Synology device would be able to fix the problem

I use a DS918+ at home which I got after having deployed Clustered RS units for VM storage in a previous role. The recent moves from the company (not certifying their devices with non first party hard disks, pushing more user licensed features (VPN/Email)) and a feeling that software quality is in decline (acknowledged bug in Apple TV app hasn't been fixed in at least 8 months).

It a real shame that both Synology seems to be following the ubiquiti route to smash their reputation to increase revenue.

View on HN

Oh I hate that “grant access” so much, at least to date they have never pushed back when I’ve said no thank you and it’s not been required

You must have lucked out. I tried getting them to fix hyperbackup issue and sent them detailed logs of exactly what was breaking and how. It wasn't honoring the port setting from what I recall.

They refused to even look at the logs if I wasn't willing to give them root access to the primary system. I told them that wasn't an option but I was happy to provide any log they wanted and they just never responded to the case again.

At the same time the security advisor in Synology DSM spams you with notifications to disable the admin user account after creating another account with admin rights first

I’ve used synology for 10 years and really liked them. But there’s quite a few annoying things popping up more frequently.

This is an example of a stupid error that I can’t turn off.

They’re starting to assume that all devices are internet connectable and subject to brute force. That seems insane to me and my synology is on a private network with no inbound connectivity. I don’t want to change from admin.

Your Maginot line is only providing imaginary security.

Actual IT security is in depth, and the simple task of having an admin account that is not the default user ID makes sense to me.

What zero days are out there that rely on a known user ID, and a known process ID for that user’s first process? You could defeat that by just following the advice from people that know better.

I’m not trying to provide absolute security as it’s for my home network.

If there’s a zero day ravaging my kids iPad then that’s the risk I take. And it’s acceptable given my situation.

“People that know better” for my situation seems pretty hard to qualify. I’m glad it makes sense to you, but since you have zero insight to my config and the changes required to implement I think it says more about the quality of your recommendations that you can give a recommendation without understanding the usability trade offs.

Maginot lines suck for protecting countries, but simple, clear defenses are pretty darn handy for protecting home networks. I’ll take a disconnected NAS over a wonderfully synced, fully compliant NAS following every recommendation (that also includes making it network accessible).

Isn’t there a Config page somewhere the let’s you pick what warnings to show?

Not that I’ve found through searching their docs and walking through the UI, but I haven’t really dig deeply into the internals.

Reply on news.ycombinator.com