Date: Tue, 27 Jun 1995 20:04:09 -0700 (PDT) From: Wes Santee <wsantee@wsantee.oz.net> To: freebsd-questions@freebsd.org Subject: Re: Any way to get hard links to directories? Message-ID: <199506280304.UAA03277@wsantee.oz.net> In-Reply-To: <9506271649.AA03027@cs.weber.edu> from "Terry Lambert" at Jun 27, 95 10:49:03 am
next in thread | previous in thread | raw e-mail | index | archive | help
Terry Lambert sez: > Suffice it to say, I would *strongly* urge you to reexamine why you > want a hard linked directory and to choose another soloution to > your problem. Just an update for the curious as to why I'd ever want to hard link a directory. My provider is trying to setup ftp access so users can't even see other users directories, let alone the system directories. One idea that came up was to chroot to the users home directory on ftp login, thereby locking out access to places they didn't need to go. Only problem is gaining access to /bin/ls, and other files needed by the ftp daemon. Since symlinks under a chroot'ed directory don't work, the idea of hard links came up and I said I would investigate the possibility. Needless to say, hard links will not be the solution. Before you cock your head and ask why my ISP would want to take this course of action, shell accounts on the server are *not* permitted, so there is no reason anybody would need access to other directories on the system. They are a SLIP/PPP provider only. Server security is of utmost importance to these people. Still, they need to give ftp access to users home directories so they can dump required files for web pages, etc. That said, anybody have any ideas on how to have the ftp daemon allow users who are logged in to see only their home (and below) directories without the ftp daemon losing access to the files it needs to operate? Cheers, -- ( -Wes Santee | You're never dead 'til you're ) ( wsantee@wsantee.oz.net | out of quarters. --InSoc ) ( http://www.oz.net/~wsantee \------------------------------ ) ( O S / 2 W A R P F r e e B S D )
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199506280304.UAA03277>