update: default to follow all symlinks
MPD 0.13 and older followed all symbolic links. Although this can be a security problem (as it has always been), 0.14 should offer the same default behaviour as 0.13.
This commit is contained in:
parent
5b11d5a332
commit
a25b8acd82
@ -38,7 +38,7 @@ This specifies the directory where saved playlists are stored.
|
|||||||
.B follow_outside_symlinks <yes or no>
|
.B follow_outside_symlinks <yes or no>
|
||||||
Control if MPD will follow symbolic links pointing outside the music dir.
|
Control if MPD will follow symbolic links pointing outside the music dir.
|
||||||
You must recreate the database after changing this option.
|
You must recreate the database after changing this option.
|
||||||
The default is "no".
|
The default is "yes".
|
||||||
.TP
|
.TP
|
||||||
.B follow_inside_symlinks <yes or no>
|
.B follow_inside_symlinks <yes or no>
|
||||||
Control if MPD will follow symbolic links pointing outside the music dir, potentially
|
Control if MPD will follow symbolic links pointing outside the music dir, potentially
|
||||||
|
@ -7,7 +7,7 @@ playlist_directory "~/.mpd/playlists"
|
|||||||
db_file "~/.mpd/mpd.db"
|
db_file "~/.mpd/mpd.db"
|
||||||
log_file "~/.mpd/mpd.log"
|
log_file "~/.mpd/mpd.log"
|
||||||
error_file "~/.mpd/mpd.error"
|
error_file "~/.mpd/mpd.error"
|
||||||
#follow_outside_symlinks "no"
|
#follow_outside_symlinks "yes"
|
||||||
#follow_inside_symlinks "yes"
|
#follow_inside_symlinks "yes"
|
||||||
################################################################
|
################################################################
|
||||||
|
|
||||||
|
@ -59,7 +59,7 @@ static struct condition delete_cond;
|
|||||||
|
|
||||||
enum {
|
enum {
|
||||||
DEFAULT_FOLLOW_INSIDE_SYMLINKS = true,
|
DEFAULT_FOLLOW_INSIDE_SYMLINKS = true,
|
||||||
DEFAULT_FOLLOW_OUTSIDE_SYMLINKS = false,
|
DEFAULT_FOLLOW_OUTSIDE_SYMLINKS = true,
|
||||||
};
|
};
|
||||||
|
|
||||||
static bool follow_inside_symlinks;
|
static bool follow_inside_symlinks;
|
||||||
|
Loading…
Reference in New Issue
Block a user