LFCS · Question #408
An administrator has just configured vsftp and notices that she cannot follow symbolic links when connected to the FTP server. What is the most likely reason for this?
The correct answer is B. vsftpd is running in a chroot environment. The most likely reason for not being able to follow symbolic links in vsftpd is that the server is configured to run in a chroot environment, which restricts access to files outside the user's jailed directory.
Question
Options
- AThe follow_symlinks=no option has been set in vsftpd.conf.
- Bvsftpd is running in a chroot environment.
- CThis installation of vsftpd was not compiled with support for symbolic links.
- DThe user account she is connecting with is not listed in /etc/security/ftpusers.
How the community answered
(29 responses)- A3% (1)
- B76% (22)
- C7% (2)
- D14% (4)
Why each option
The most likely reason for not being able to follow symbolic links in vsftpd is that the server is configured to run in a chroot environment, which restricts access to files outside the user's jailed directory.
The `follow_symlinks=no` option explicitly disables following symbolic links, but it defaults to `YES`; if symbolic links are entirely inaccessible, a chroot environment is a more fundamental cause.
When vsftpd runs a user in a `chroot` environment (e.g., via `chroot_local_user=YES`), the server's view of the file system is restricted to that jail, preventing symbolic links from pointing to locations outside of the chroot directory.
Standard installations of vsftpd are compiled with support for symbolic links; this is not a common issue for a properly installed server.
If a user account is listed in `/etc/security/ftpusers`, it means the user is explicitly denied FTP access, preventing them from logging in at all, not just from following symbolic links.
Concept tested: vsftpd chroot security and symbolic links
Source: https://linux.die.net/man/5/vsftpd.conf
Topics
Community Discussion
No community discussion yet for this question.