• 0 Posts
  • 423 Comments
Joined 2 years ago
cake
Cake day: June 16th, 2023

help-circle






  • You are being prompted because the nobody/nogroup user/group has no password, no shell, and no permissions.

    That tutorial is wrong. Couple of problems immediately:

    • “valid users” specifies “all the users in this group are allowed access”. It is incompatible with “force user/group” directive
    • you should be using the “guest user=” directive, which sets the identity of any public access. Your permissions should match this user.
    • nobody/nogroup are special user and group that (usually) have no access to any file. They exist for processes to run with minimal provileges, or for a fallback default if UID/gid map are invalid. Using this user/group combo for this samba share implies that you will either alter them so that they now DO have privileges to access files, or that you intend samba to never access any files. Create a guest user, set permissions and umask in the directory.





  • I can run app based routing and blocking on my router, but whether that would restrict DNS for those services I don’t know.

    That’s the double-edged sword of DNS over https. It allows us to hide our DNS queries from local ISP and others, but it also allows applications to hide theirs also. It just looks like encrypted web traffic to your router.


  • Not sure what you mean by “network based dns”.

    Hard-coded DNS is in the application, you cannot change this from any dhcp option. Browsers do it, lots of versions of prime video apps do it. Google nest and home devices are famous for this.

    You can write a NAT rewrite rule at your router to catch any UDP or TCP request on port 53 and send it to your ad-blocking DNS server/forwarder, but you won’t be able to stop DoH (DNS over https), which just leaves the subnet encrypted on 443.



  • Thanks for the context. I did read the articles on this, but you’ve summed up the positives well.

    Unfortunately, these articles also point out that putting uutils into the wild of 25.10 will doubtless reveal some hitherto unknown breakages and rough patches.

    Which I agree with. No one is forcing anyone to use 25.10, but there is no better way to smoke test sw than pushing it to prod.

    I’m a Debian user, so I have the luxury of waiting to see the outcome of these efforts for now.






  • Well, it wouldn’t hurt anything to install fail2ban and enable the popular templates, but it sounds like you might need to explain your service layout and how it’s exposed to the web before anyone can suggest a security measure.

    Generally in the self-hosted space there are two common approaches: set up a VPN into your network for your trusted devices, or set up a reverse-proxy with a trusted tunneling proxy like cloudflare.

    That you are seeing “attack attempts” in your caddy logs should be elaborated as well. What exactly are you seeing?