LX0-104 · 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 inability to follow symbolic links in vsftpd is often caused by security configurations that restrict filesystem access, such as chrooting users.
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
(61 responses)- A3% (2)
- B82% (50)
- C10% (6)
- D5% (3)
Why each option
The inability to follow symbolic links in vsftpd is often caused by security configurations that restrict filesystem access, such as chrooting users.
While follow_symlinks=no (or allow_symlinks=NO) in vsftpd.conf would prevent following symbolic links, it's typically set to 'yes' by default, and a chroot environment (B) is a more common default security measure that inherently restricts external symlinks.
If vsftpd is running in a chroot environment, symbolic links that point to files or directories outside of the user's jailed directory will not be resolvable or followable, due to the restricted filesystem view and security isolation.
vsftpd is almost always compiled with support for symbolic links, as it's a fundamental filesystem feature, making lack of compilation support highly unlikely.
If the user account were listed in /etc/security/ftpusers, the user would be completely denied FTP access, not just prevented from following symbolic links.
Concept tested: vsftpd chroot and symbolic link behavior
Source: https://man7.org/linux/man-pages/man5/vsftpd.conf.5.html
Topics
Community Discussion
No community discussion yet for this question.