joulethief
@joulethief@discuss.tchncs.de
- Comment on Visibility of NFS exports 1 week ago:
Even with bar exported to this client, it cannot see its contents. What the hell is going on? Just to be clear, I did run
exportfs -arvafter every change to /etc/exports. - Comment on Visibility of NFS exports 1 week ago:
Thank you. I’m closer to what I want now. Can you help me explain this behavior though:
For testing purposes, I commented out every line in /etc/exports but these:
/srv/nfsv4 192.168.0.10(ro,sync,secure,root_squash,subtree_check,fsid=0) \ 192.168.0.20(ro,sync,secure,root_squash,subtree_check,fsid=0)
Client 192.168.0.20 can mount nfs-server:/ and listing the contents gives both directories foo and bar. It cannot see the contents of foo, as intended, but it can see what’s inside bar. I cannot figure out why? I rebooted the machine in hopes it was just a caching thing, to no avail.
Apart from that, I was hoping 192.168.0.20 could not even mount foo, but as long as its contents are hidden, I can live with that for now.
- Comment on Visibility of NFS exports 1 week ago:
That can’t be right. For exposing it to a whole subnet, it would have to be 192.168.0.0/24, wouldn’t it?
- Submitted 1 week ago to selfhosted@lemmy.world | 7 comments
- Comment on Drop OSS - an open-source, self-hosted alternative to platforms like Steam and Epic. 3 weeks ago:
Non-sysadmin here, I could only find some generic info on ISO 27002/27001, what does it say about containerized applications?