You should not tell people to wrangle down their Windows security

[Suedkiez (Just a fellow user like you)]

@Alexander_Holy

That is exactly my point: ROCK/Nucleus are untrusted shares on my private network.

This is only a problem if you have untrusted users on your private network who will place malware on the share. Like I said, you have bigger problems in this case. Normally, a share on your own private LAN is trusted by definition.

It’s not going to cause a CVE or anything.

(By the way, even draconian Apple allows anonymous access to shares by default)

@Alexander_Holy

What I am asking for: Roon can fix this most easily and provide a documented/ controlled/ supported way how this should be handled by users who wish to secure their systems.

FYI, Roon OS 3.0 is currently in Early Access testing, which will fix the annoying issue of having to change the Windows configuration to allow anonymous access by requiring a username/password for the Roon OS share:

@ivan

Network Sharing (Samba 4 Upgrade)

RoonOS 3.0 upgrades the file sharing stack from Samba 3 to Samba 4, bringing updated technology and improved security. All existing network folders carry over seamlessly — no reconfiguration needed.

Action required for RoonOS Data Share: Samba 4 no longer allows fully anonymous access to the RoonOS Data share. To access the RoonOS Data folder, you will now need to enter credentials when prompted:

• Username: guest
• Password: guest

Here’s an article which can guide you through the process – link

Of course, this does nothing for protection against untrusted users on your private LAN.