vsftpd: handle migration and fix secure_chroot_dir error #25720
Merged
+20
−8
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mhusaam
force-pushed
the
for_vsftpd_mdns
branch
from
e3814d8 to
2e7498e
Compare
BKPepe
reviewed
Jan 10, 2025
mhusaam
force-pushed
the
for_vsftpd_mdns
branch
from
2e7498e to
d137f07
Compare
BKPepe
reviewed
Jan 10, 2025
* update UCI to use the traditional vsftpd.conf so that people migrating from non-uci version do not face problems * if secure_chroot_dir is not provided specifically, then create an empty directory where vsftpd usually expects it Signed-off-by: Mohd Husaam Mehdi <[email protected]>
mhusaam
force-pushed
the
for_vsftpd_mdns
branch
from
d137f07 to
cd6c31b
Compare
|
LGTM @Alexey71 Can you check this changes? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Mohd Husaam Mehdi [email protected]