Add a --mode option to chmod the mount point of the maps
Subsystems (2)
PATCH 1/1 Add a --mode option to chmod the mount point of the maps
Hello,
It looks like the mount point of the maps have fixed permissions, 755. I need to have different permissions: in my use case, I want /home (which is handled by autofs) to be set to 751.
The initial permissions of /home are overwritten when autofs is started, so changing those doesn't help.
I can change the permissions of /home after autofs has started, but it's really not convenient: there's no easy way to do that automatically with either sysvinit or systemd.
For instance, with systemd, I could create a new service that depends on autofs and does the chmod, but it will be started once automount has been started, and there's guarantee it's already mounted the maps. And if it's started after the mounts, there's a small period of time when the permissions would be incorrect.
My solution was to add a --mode option to autofs, with the included patch. I'm not familiar with autofs's code or even Lex and Yacc, so my code is probably more of a proof of concept. It seems to work fine in my use case, though.
Signature · 1 line
Cyril B.
daemon/direct.c +4 -0
@@ -433,6 +433,10 @@ int do_mount_autofs_direct(struct autofs_point *ap, goto out_umount; } +if (ap->mode !=-1 ) { +chmod (me->key, ap->mode); + } + ops->open (ap->logopt, &ioctlfd, st.st_dev, me->key);if (ioctlfd <0 ) {crit (ap->logopt,"failed to create ioctl fd for %s" , me->key);
daemon/indirect.c +4 -0
@@ -163,6 +163,10 @@ static int do_mount_autofs_indirect(struct autofs_point *ap, const char *root) goto out_umount; } +if (ap->mode !=-1 ) { +chmod (root, ap->mode); + } +if (ops->open (ap->logopt, &ap->ioctlfd, st.st_dev, root)) {crit (ap->logopt,"failed to create ioctl fd for autofs path %s" , ap->path);
include/automount.h +1 -0
@@ -492,6 +492,7 @@ struct kernel_mod_version {struct autofs_point {pthread_t thid;char *path;/* Mount point name */ +mode_t mode;/* Mount point mode */ char *pref;/* amd prefix */ int pipefd;/* File descriptor for pipe */ int kpipefd;/* Kernel end descriptor for pipe */
lib/master.c +1 -0
@@ -129,6 +129,7 @@ int master_add_autofs_point(struct master_mapent *entry, unsigned logopt,free (ap);return 0 ; } + ap->mode =-1 ; entry->ap = ap;
lib/master_parse.y +9 -1
@@ -63,6 +63,7 @@ static unsigned ghost; extern unsigned global_selection_options; static unsigned random_selection; static unsigned use_weight; +static mode_t mode; static char **tmp_argv; static int tmp_argc; static char **local_argv;
@@ -101,7 +102,7 @@ static int master_fprintf(FILE *, char *, ...); %token COMMENT %token MAP %token OPT_TIMEOUT OPT_NTIMEOUT OPT_NOBIND OPT_NOGHOST OPT_GHOST OPT_VERBOSE -%token OPT_DEBUG OPT_RANDOM OPT_USE_WEIGHT OPT_SYMLINK +%token OPT_DEBUG OPT_RANDOM OPT_USE_WEIGHT OPT_SYMLINK OPT_MODE %token COLON COMMA NL DDASH %type <strtype> map %type <strtype> options
@@ -126,6 +127,7 @@ static int master_fprintf(FILE *, char *, ...); %token <strtype> MAPXFN %token <strtype> MAPNAME %token <longtype> NUMBER +%token <longtype> OCTALNUMBER %token <strtype> OPTION %start file
@@ -192,6 +194,7 @@ line: | PATH OPT_GHOST { master_notify($1); YYABORT; } | PATH OPT_NOGHOST { master_notify($1); YYABORT; } | PATH OPT_VERBOSE { master_notify($1); YYABORT; } + | PATH OPT_MODE { master_notify($1); YYABORT; } | PATH { master_notify($1); YYABORT; } | QUOTE { master_notify($1); YYABORT; } | OPTION { master_notify($1); YYABORT; }
@@ -576,6 +579,7 @@ daemon_option: OPT_TIMEOUT NUMBER { timeout = $2; } | OPT_DEBUG { debug = 1; } | OPT_RANDOM { random_selection = 1; } | OPT_USE_WEIGHT { use_weight = 1; } + | OPT_MODE OCTALNUMBER { mode = $2; } ; mount_option: OPTION
@@ -644,6 +648,7 @@ static void local_init_vars(void) ghost = defaults_get_browse_mode(); random_selection = global_selection_options & MOUNT_FLAG_RANDOM_SELECT; use_weight = 0; + mode = -1; tmp_argv = NULL; tmp_argc = 0; local_argv = NULL;
@@ -847,6 +852,9 @@ int master_parse_entry(const char *buffer, unsigned int default_timeout, unsigne entry->ap->flags |= MOUNT_FLAG_SYMLINK; if (negative_timeout) entry->ap->negative_timeout = negative_timeout; + if (mode != -1) { + entry->ap->mode = mode; + } /* source = master_find_map_source(entry, type, format,
lib/master_tok.l +19 -1
@@ -84,7 +84,7 @@ unsigned int tlen; %option nounput -%x PATHSTR MAPSTR DNSTR OPTSTR +%x PATHSTR MAPSTR DNSTR OPTSTR OCTAL WS [[:blank:]]+ OPTWS [[:blank:]]*
@@ -95,6 +95,7 @@ OPTIONSTR ([\-]?([[:alpha:]_]([[:alnum:]_\-])*(=(\"?([[:alnum:]_\-\:])+\"?))?)+) MACROSTR (-D{OPTWS}([[:alpha:]_]([[:alnum:]_\-\.])*)=([[:alnum:]_\-\.])+) SLASHIFYSTR (--(no-)?slashify-colons) NUMBER [0-9]+ +OCTALNUMBER [0-7]+ DNSERVSTR1 ([[:alpha:]][[:alnum:]\-.]*(:[0-9]+)?:) DNSERVSTR2 (\[([[:xdigit:]]:.)+\](:[0-9]+)?:)
@@ -125,6 +126,8 @@ MTYPE ((file|program|exec|sss|yp|nis|nisplus|ldap|ldaps|hesiod|userdir)(,(sun|h OPTTOUT (-t{OPTWS}|-t{OPTWS}={OPTWS}|--timeout{OPTWS}|--timeout{OPTWS}={OPTWS}) OPTNTOUT (-n{OPTWS}|-n{OPTWS}={OPTWS}|--negative-timeout{OPTWS}|--negative-timeout{OPTWS}={OPTWS}) +MODE (--mode{OPTWS}|--mode{OPTWS}={OPTWS}) + %% <INITIAL>{
@@ -392,6 +395,11 @@ OPTNTOUT (-n{OPTWS}|-n{OPTWS}={OPTWS}|--negative-timeout{OPTWS}|--negative-timeo -w|--use-weight-only { return(OPT_USE_WEIGHT); } -r|--random-multimount-selection { return(OPT_RANDOM); } + {MODE}/{OCTALNUMBER} { + BEGIN(OCTAL); + return(OPT_MODE); + } + {OPTWS}","{OPTWS} { return(COMMA); } {OPTWS} {}
@@ -423,6 +431,16 @@ OPTNTOUT (-n{OPTWS}|-n{OPTWS}={OPTWS}|--negative-timeout{OPTWS}|--negative-timeo <<EOF>> { BEGIN(INITIAL); } } +<OCTAL>{ + + {OCTALNUMBER} { + master_lval.longtype = strtol(master_text, NULL, 8); + return(OCTALNUMBER); + } + + . { BEGIN(OPTSTR); yyless(0); } +} + %% #include "automount.h"
Ian Kent
maintainerQuoted 5 lines · Cyril B.
Hello,
It looks like the mount point of the maps have fixed permissions, 755. I need to have different permissions: in my use case, I want /home (which is handled by autofs) to be set to 751.
Why is this needed?
Quoted 3 lines
The initial permissions of /home are overwritten when autofs is started, so changing those doesn't help.
They aren't overwritten.
The permissions are those of the autofs mount that is mounted over /home.
Quoted 4 lines
I can change the permissions of /home after autofs has started, but it's really not convenient: there's no easy way to do that automatically with either sysvinit or systemd.
I still don't understand why this is needed.
For indirect mounts no-one can copy things into the autofs mount and the permissions of mounts on mount points will be the same as those of the mounted file system when they are done.
Ian
--
To unsubscribe from this list: send the line "unsubscribe autofs" in
Ian Kent
maintainerQuoted 5 lines · Cyril B.
My solution was to add a --mode option to autofs, with the included patch. I'm not familiar with autofs's code or even Lex and Yacc, so my code is probably more of a proof of concept. It seems to work fine in my use case, though.
If you want to contribute patches then post then in-line as text without any additional change (eg. ensure the mailer doesn't split lines therby corrupting the patch).
I can't properly comment on the patch, even if I wanted too, because it isn't in-line.
Anyway, what about updating the man pages with your new option? Should text modes be considered, perhaps octal modes are sufficient, and should be all that's allowed, to keep the change as simple (generally a good idea) ...
Ian
--
To unsubscribe from this list: send the line "unsubscribe autofs" in
Ian Kent
maintainerQuoted 11 lines · Ian Kent
Quoted 5 lines · Cyril B.
My solution was to add a --mode option to autofs, with the included patch. I'm not familiar with autofs's code or even Lex and Yacc, so my code is probably more of a proof of concept. It seems to work fine in my use case, though.
If you want to contribute patches then post then in-line as text without any additional change (eg. ensure the mailer doesn't split lines therby corrupting the patch).
Quoted 7 lines
I can't properly comment on the patch, even if I wanted too, because it isn't in-line.
Anyway, what about updating the man pages with your new option? Should text modes be considered, perhaps octal modes are sufficient, and should be all that's allowed, to keep the change as simple (generally a good idea) ...
And btw, I've been trying to ensure that all autofs patches have a problem description for quite a long time now, so we need that too.
Generally describing what the change does isn't OK, a description of why it's needed is more important and usually negates the need to describe what the patch does.
Recently I've started adding "Signed-off-by:" annotation too.
Ian
--
To unsubscribe from this list: send the line "unsubscribe autofs" in
Quoted 6 lines · Ian Kent
Quoted 3 lines · Cyril B.
It looks like the mount point of the maps have fixed permissions, 755. I need to have different permissions: in my use case, I want /home (which is handled by autofs) to be set to 751.
Why is this needed?
Why do I want to set /home to 751? When it was set to 755, I frequently had users believing there was a serious vulnerability because they could list /home. Stupid, I know, but setting the permissions to 751 was a trivial solution for this.
Quoted 6 lines
Quoted 2 lines
The initial permissions of /home are overwritten when autofs is started, so changing those doesn't help.
They aren't overwritten.
The permissions are those of the autofs mount that is mounted over /home.
I'm not sure I'm following you. Here's my auto.master:
/home program:/etc/auto.home
Before launching autofs, permissions are set to 751:
# ls -ald /home drwxr-x--x 2 root root 4096 Aug 7 11:09 /home
Once I've launched autofs, permissions are reset to 755:
# ls -ald /home drwxr-xr-x 2 root root 0 Sep 14 10:32 /home
And when I quit autofs, my permissions are back to 751:
# ls -ald /home drwxr-x--x 2 root root 4096 Aug 7 11:09 /home
What I want is to always have /home permissions set to 751.
Note that I'm not talking about mount points below /home (e.g. /home/foobar), those do have the correct permissions.
Signature · 3 lines
Cyril B. -- To unsubscribe from this list: send the line "unsubscribe autofs" in
Quoted 26 lines · Cyril B.
Quoted 6 lines · Ian Kent
Quoted 3 lines · Cyril B.
It looks like the mount point of the maps have fixed permissions, 755. I need to have different permissions: in my use case, I want /home (which is handled by autofs) to be set to 751.
Why is this needed?
Why do I want to set /home to 751? When it was set to 755, I frequently had users believing there was a serious vulnerability because they could list /home. Stupid, I know, but setting the permissions to 751 was a trivial solution for this.
Quoted 6 lines
Quoted 2 lines
The initial permissions of /home are overwritten when autofs is started, so changing those doesn't help.
They aren't overwritten.
The permissions are those of the autofs mount that is mounted over /home.I'm not sure I'm following you. Here's my auto.master:
/home program:/etc/auto.home
Before launching autofs, permissions are set to 751:
Quoted 7 lines
# ls -ald /home drwxr-x--x 2 root root 4096 Aug 7 11:09 /homeOnce I've launched autofs, permissions are reset to 755:
# ls -ald /home drwxr-xr-x 2 root root 0 Sep 14 10:32 /home
They are not "re"set. These are the permissions of the filesystem that you are mounting over /home (e.g. myfileserver:/export/homes). Change the permissions of /export/homes on myfileserver.
frank
Quoted 11 lines
And when I quit autofs, my permissions are back to 751:
# ls -ald /home drwxr-x--x 2 root root 4096 Aug 7 11:09 /homeWhat I want is to always have /home permissions set to 751.
Note that I'm not talking about mount points below /home (e.g.
/home/foobar), those do have the correct permissions.
Signature · 4 lines
Frank Thommen - Structures IT Management and Support - EMBL Heidelberg [email protected] - +49 6221 387 8353 -- To unsubscribe from this list: send the line "unsubscribe autofs" in
Quoted 3 lines · Frank Thommen
They are not "re"set. These are the permissions of the filesystem that you are mounting over /home (e.g. myfileserver:/export/homes). Change the permissions of /export/homes on myfileserver.
In my case, I haven't mounted anything at all yet. My map is an executable, and since I haven't triggered an automatic mount (by accessing /home/foo), the executable has not even been called once. /home is empty.
Signature · 3 lines
Cyril B. -- To unsubscribe from this list: send the line "unsubscribe autofs" in
Ian Kent
maintainerQuoted 16 lines · Cyril B.
Quoted 6 lines · Ian Kent
Quoted 3 lines · Cyril B.
It looks like the mount point of the maps have fixed permissions, 755. I need to have different permissions: in my use case, I want /home (which is handled by autofs) to be set to 751.
Why is this needed?
Why do I want to set /home to 751? When it was set to 755, I frequently had users believing there was a serious vulnerability because they could list /home. Stupid, I know, but setting the permissions to 751 was a trivial solution for this.
Quoted 3 lines
Quoted 2 lines
The initial permissions of /home are overwritten when autofs is started, so changing those doesn't help.
Quoted 7 lines
Quoted 3 lines
They aren't overwritten.
The permissions are those of the autofs mount that is mounted over /home.I'm not sure I'm following you. Here's my auto.master:
/home program:/etc/auto.home
Which means there will be an autofs pseudo file system mounted on /home when automount(8) starts.
This is how the kernel intercepts accesses to these and calls back to the automount(8) daemon to request it perform mounts.
Quoted 7 lines
Before launching autofs, permissions are set to 751:
# ls -ald /home drwxr-x--x 2 root root 4096 Aug 7 11:09 /homeOnce I've launched autofs, permissions are reset to 755:
The permissions are those of the root of the autofs pseudo file system, the permissions of the underlying mount point aren't changed.
Quoted 5 lines
# ls -ald /home drwxr-xr-x 2 root root 0 Sep 14 10:32 /homeAnd when I quit autofs, my permissions are back to 751:
Because the autofs pseudo file system is then umounted and the underlying directory is again visible.
Quoted 5 lines
# ls -ald /home drwxr-x--x 2 root root 4096 Aug 7 11:09 /homeWhat I want is to always have /home permissions set to 751.
I still don't understand how that's an effective security measure.
Anyone determined enough will be able to find out the directory names and can then change to them, assuming the permissions of the mounts themselves allow it.
No-one can do anything much in the autofs pseudo file system except the daemon itself, and usually the request is that the mount points within an autofs mount be seen, aka. the browse option, not hidden, ;)
So are you saying you don't have sufficient faith in the permissions set on the file systems your mounting, that contain the information you want to protect, that you must have the permissions of an intermediate file system set to ensure that information about that vulnerability is not seen?
Can't say I can see how this has any actual benefit at all.
Ian
--
To unsubscribe from this list: send the line "unsubscribe autofs" in
Ian Kent
maintainerQuoted 9 lines · Cyril B.
Quoted 3 lines · Frank Thommen
They are not "re"set. These are the permissions of the filesystem that you are mounting over /home (e.g. myfileserver:/export/homes). Change the permissions of /export/homes on myfileserver.
In my case, I haven't mounted anything at all yet. My map is an executable, and since I haven't triggered an automatic mount (by accessing
/home/foo), the executable has not even been called once. /home is empty.
And if you create a file inside /home before starting automount(8) it will (not so) mysteriously disappear when automount is started.
Why don't you check what mounts you have after automount is started.
That may well answer your question and don't forget to check if /etc/mtab is a symlink to a mount table in the proc file system.
If it isn't then the autofs file system mounts won't be present in /etc/mtab but they will be seen in the mount table within the proc pseudo file system at /proc/mounts.
Ian
--
To unsubscribe from this list: send the line "unsubscribe autofs" in
Quoted 5 lines · Ian Kent
So are you saying you don't have sufficient faith in the permissions set on the file systems your mounting, that contain the information you want to protect, that you must have the permissions of an intermediate file system set to ensure that information about that vulnerability is not seen?
I do know that there's no vulnerability at all, and that you can trivially list users by other means.
Unfortunately, some of my less tech savvy users believe that there's a vulnerability because they can see other accounts' home directories, and thus feel that their own files are not safe. Is this stupid? absolutely. But changing my /home permissions to 751 makes those users happy and saves my time -- and my reputation as a sysadmin :)
I also do realize that the 755 permissions come from the autofs kernel filesystem itself. But the kernel doesn't support a 'mode' option for autofs (some other file systems do), and even if it did, autofs would have to be patched to support it (in a slightly different way than my current patch).
I understand that my use case may be a corner case, and I'm perfectly fine with keeping my patch in my own tree. I figured that since I had written the patch for myself anway, I may as well post it here as it could be useful for others :)
Thanks!
Signature · 3 lines
Cyril B. -- To unsubscribe from this list: send the line "unsubscribe autofs" in
Ian Kent
maintainerQuoted 22 lines · Cyril B.
Quoted 5 lines · Ian Kent
So are you saying you don't have sufficient faith in the permissions set on the file systems your mounting, that contain the information you want to protect, that you must have the permissions of an intermediate file system set to ensure that information about that vulnerability is not seen?
I do know that there's no vulnerability at all, and that you can trivially list users by other means.
Unfortunately, some of my less tech savvy users believe that there's a vulnerability because they can see other accounts' home directories, and thus feel that their own files are not safe. Is this stupid? absolutely. But changing my /home permissions to 751 makes those users happy and saves my time -- and my reputation as a sysadmin :)
I also do realize that the 755 permissions come from the autofs kernel filesystem itself. But the kernel doesn't support a 'mode' option for autofs (some other file systems do), and even if it did, autofs would have to be patched to support it (in a slightly different way than my current patch).
Quoted 4 lines
I understand that my use case may be a corner case, and I'm perfectly fine with keeping my patch in my own tree. I figured that since I had written the patch for myself anway, I may as well post it here as it could be useful for others :)
And I didn't say I wouldn't accept the change but I will need you to do the work to include all the things that the patch needs.
I'm not sure if it would be better to add mode as an autofs file system option to the kernel and yes, the daemon would still need changes. It might end up more complicated that way.
Ian
--
To unsubscribe from this list: send the line "unsubscribe autofs" in
Quoted 11 lines · Ian Kent
If you want to contribute patches then post then in-line as text without any additional change (eg. ensure the mailer doesn't split lines therby corrupting the patch).
I can't properly comment on the patch, even if I wanted too, because it isn't in-line.
Anyway, what about updating the man pages with your new option? Should text modes be considered, perhaps octal modes are sufficient, and should be all that's allowed, to keep the change as simple (generally a good idea) ...
My bad, sorry. Here's a second try, including a commit message and an updated man page:
add map option --mode
Add a --mode map option to change the mode for the base location mount point. If this option is given, autofs will chmod the mount point right after mounting it (as the kernel autofs filesystem doesn't support a 'mode' option).
Changing the mode of the base location mount point is normally not needed, but if one wants to do that, it's much better to do it inside autofs rather than outside to avoid race conditions and making sure the correct permissions are always set.
--- daemon/direct.c | 4 ++++ daemon/indirect.c | 4 ++++ include/automount.h | 1 + lib/master.c | 1 + lib/master_parse.y | 10 +++++++++- lib/master_tok.l | 20 +++++++++++++++++++- man/auto.master.5.in | 5 +++++ 7 files changed, 43 insertions(+), 2 deletions(-)
daemon/direct.c +4 -0
@@ -433,6 +433,10 @@ int do_mount_autofs_direct(struct autofs_point *ap, goto out_umount; } +if (ap->mode !=-1 ) { +chmod (me->key, ap->mode); + } + ops->open (ap->logopt, &ioctlfd, st.st_dev, me->key);if (ioctlfd <0 ) {crit (ap->logopt,"failed to create ioctl fd for %s" , me->key);
daemon/indirect.c +4 -0
@@ -163,6 +163,10 @@ static int do_mount_autofs_indirect(struct autofs_point *ap, const char *root) goto out_umount; } +if (ap->mode !=-1 ) { +chmod (root, ap->mode); + } +if (ops->open (ap->logopt, &ap->ioctlfd, st.st_dev, root)) {crit (ap->logopt,"failed to create ioctl fd for autofs path %s" , ap->path);
include/automount.h +1 -0
@@ -492,6 +492,7 @@ struct kernel_mod_version {struct autofs_point {pthread_t thid;char *path;/* Mount point name */ +mode_t mode;/* Mount point mode */ char *pref;/* amd prefix */ int pipefd;/* File descriptor for pipe */ int kpipefd;/* Kernel end descriptor for pipe */
lib/master.c +1 -0
@@ -129,6 +129,7 @@ int master_add_autofs_point(struct master_mapent *entry, unsigned logopt,free (ap);return 0 ; } + ap->mode =-1 ; entry->ap = ap;
lib/master_parse.y +9 -1
@@ -63,6 +63,7 @@ static unsigned ghost; extern unsigned global_selection_options; static unsigned random_selection; static unsigned use_weight; +static mode_t mode; static char **tmp_argv; static int tmp_argc; static char **local_argv;
@@ -101,7 +102,7 @@ static int master_fprintf(FILE *, char *, ...); %token COMMENT %token MAP %token OPT_TIMEOUT OPT_NTIMEOUT OPT_NOBIND OPT_NOGHOST OPT_GHOST OPT_VERBOSE -%token OPT_DEBUG OPT_RANDOM OPT_USE_WEIGHT OPT_SYMLINK +%token OPT_DEBUG OPT_RANDOM OPT_USE_WEIGHT OPT_SYMLINK OPT_MODE %token COLON COMMA NL DDASH %type <strtype> map %type <strtype> options
@@ -126,6 +127,7 @@ static int master_fprintf(FILE *, char *, ...); %token <strtype> MAPXFN %token <strtype> MAPNAME %token <longtype> NUMBER +%token <longtype> OCTALNUMBER %token <strtype> OPTION %start file
@@ -192,6 +194,7 @@ line: | PATH OPT_GHOST { master_notify($1); YYABORT; } | PATH OPT_NOGHOST { master_notify($1); YYABORT; } | PATH OPT_VERBOSE { master_notify($1); YYABORT; } + | PATH OPT_MODE { master_notify($1); YYABORT; } | PATH { master_notify($1); YYABORT; } | QUOTE { master_notify($1); YYABORT; } | OPTION { master_notify($1); YYABORT; }
@@ -576,6 +579,7 @@ daemon_option: OPT_TIMEOUT NUMBER { timeout = $2; } | OPT_DEBUG { debug = 1; } | OPT_RANDOM { random_selection = 1; } | OPT_USE_WEIGHT { use_weight = 1; } + | OPT_MODE OCTALNUMBER { mode = $2; } ; mount_option: OPTION
@@ -644,6 +648,7 @@ static void local_init_vars(void) ghost = defaults_get_browse_mode(); random_selection = global_selection_options & MOUNT_FLAG_RANDOM_SELECT; use_weight = 0; + mode = -1; tmp_argv = NULL; tmp_argc = 0; local_argv = NULL;
@@ -847,6 +852,9 @@ int master_parse_entry(const char *buffer, unsigned int default_timeout, unsigne entry->ap->flags |= MOUNT_FLAG_SYMLINK; if (negative_timeout) entry->ap->negative_timeout = negative_timeout; + if (mode != -1) { + entry->ap->mode = mode; + } /* source = master_find_map_source(entry, type, format,
lib/master_tok.l +19 -1
@@ -84,7 +84,7 @@ unsigned int tlen; %option nounput -%x PATHSTR MAPSTR DNSTR OPTSTR +%x PATHSTR MAPSTR DNSTR OPTSTR OCTAL WS [[:blank:]]+ OPTWS [[:blank:]]*
@@ -95,6 +95,7 @@ OPTIONSTR ([\-]?([[:alpha:]_]([[:alnum:]_\-])*(=(\"?([[:alnum:]_\-\:])+\"?))?)+) MACROSTR (-D{OPTWS}([[:alpha:]_]([[:alnum:]_\-\.])*)=([[:alnum:]_\-\.])+) SLASHIFYSTR (--(no-)?slashify-colons) NUMBER [0-9]+ +OCTALNUMBER [0-7]+ DNSERVSTR1 ([[:alpha:]][[:alnum:]\-.]*(:[0-9]+)?:) DNSERVSTR2 (\[([[:xdigit:]]:.)+\](:[0-9]+)?:)
@@ -125,6 +126,8 @@ MTYPE ((file|program|exec|sss|yp|nis|nisplus|ldap|ldaps|hesiod|userdir)(,(sun|h OPTTOUT (-t{OPTWS}|-t{OPTWS}={OPTWS}|--timeout{OPTWS}|--timeout{OPTWS}={OPTWS}) OPTNTOUT (-n{OPTWS}|-n{OPTWS}={OPTWS}|--negative-timeout{OPTWS}|--negative-timeout{OPTWS}={OPTWS}) +MODE (--mode{OPTWS}|--mode{OPTWS}={OPTWS}) + %% <INITIAL>{
@@ -392,6 +395,11 @@ OPTNTOUT (-n{OPTWS}|-n{OPTWS}={OPTWS}|--negative-timeout{OPTWS}|--negative-timeo -w|--use-weight-only { return(OPT_USE_WEIGHT); } -r|--random-multimount-selection { return(OPT_RANDOM); } + {MODE}/{OCTALNUMBER} { + BEGIN(OCTAL); + return(OPT_MODE); + } + {OPTWS}","{OPTWS} { return(COMMA); } {OPTWS} {}
@@ -423,6 +431,16 @@ OPTNTOUT (-n{OPTWS}|-n{OPTWS}={OPTWS}|--negative-timeout{OPTWS}|--negative-timeo <<EOF>> { BEGIN(INITIAL); } } +<OCTAL>{ + + {OCTALNUMBER} { + master_lval.longtype = strtol(master_text, NULL, 8); + return(OCTALNUMBER); + } + + . { BEGIN(OPTSTR); yyless(0); } +} + %% #include "automount.h"
man/auto.master.5.in +5 -0
@@ -211,6 +211,11 @@ or in the configuration. Set the timeout for caching failed key lookups. This option can be used to override the global default given either on the command line or in the configuration. +.TP +.I "\-\-mode <octal_mode>" +Set the directory mode for the base location of the \fBautofs\fP mount point. +If this option is given, \fBautofs\fP will chmod that directory with this +mode. .SH BUILTIN MAP \-hosts If "\-hosts" is given as the map then accessing a key under the mount point which corresponds to a hostname will allow access to the exports of that
--
2.1.4
Signature · 3 lines
Cyril B. -- To unsubscribe from this list: send the line "unsubscribe autofs" in