How to specify regular expression for command arguments in sudoers
sudoers(5)
manpage says that shell-style wildcards (aka meta or glob characters)
could be used in command line arguments in the sudoers file. They are *
, ?
, [...]
and [!...]
.
My idea is to use some stuff in regular expression style, like /path/to/command -a[v]*
, to mean either command -a
, command -av
and command -avvv...v
in one line (for such commands which changes their's verbosity depending on number of -v
arguments, e.g. tcpdump
). But it doesn't works.
Is there some way to do that, not adding /path/to/command -a -v
several times into sudoers
with different number of -v
in each one?
sudo
bumped to the homepage by Community♦ 51 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
sudoers(5)
manpage says that shell-style wildcards (aka meta or glob characters)
could be used in command line arguments in the sudoers file. They are *
, ?
, [...]
and [!...]
.
My idea is to use some stuff in regular expression style, like /path/to/command -a[v]*
, to mean either command -a
, command -av
and command -avvv...v
in one line (for such commands which changes their's verbosity depending on number of -v
arguments, e.g. tcpdump
). But it doesn't works.
Is there some way to do that, not adding /path/to/command -a -v
several times into sudoers
with different number of -v
in each one?
sudo
bumped to the homepage by Community♦ 51 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
sudoers(5)
manpage says that shell-style wildcards (aka meta or glob characters)
could be used in command line arguments in the sudoers file. They are *
, ?
, [...]
and [!...]
.
My idea is to use some stuff in regular expression style, like /path/to/command -a[v]*
, to mean either command -a
, command -av
and command -avvv...v
in one line (for such commands which changes their's verbosity depending on number of -v
arguments, e.g. tcpdump
). But it doesn't works.
Is there some way to do that, not adding /path/to/command -a -v
several times into sudoers
with different number of -v
in each one?
sudo
sudoers(5)
manpage says that shell-style wildcards (aka meta or glob characters)
could be used in command line arguments in the sudoers file. They are *
, ?
, [...]
and [!...]
.
My idea is to use some stuff in regular expression style, like /path/to/command -a[v]*
, to mean either command -a
, command -av
and command -avvv...v
in one line (for such commands which changes their's verbosity depending on number of -v
arguments, e.g. tcpdump
). But it doesn't works.
Is there some way to do that, not adding /path/to/command -a -v
several times into sudoers
with different number of -v
in each one?
sudo
sudo
asked Mar 18 '15 at 13:59
AntonioKAntonioK
5922727
5922727
bumped to the homepage by Community♦ 51 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 51 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The sudoers
man page is fairly clear about not supporting this. Comments in the man page suggest that it uses the system fnmatch function to do the matching. On linux/glibc based systems fnmatch can use an extended globbing format with similar expressiveness to regular expressions but a different syntax.
Therefore if you should be able to rebuild sudo to support the extended syntax by finding the place where sudo calls fnmatch adding FNM_EXTMATCH to the flags argument.
and #define _GNU_SOURCE to the top of the file that calls it.
Of course if you do this you will be running your own hand patched version of an suid binary so be careful.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f190981%2fhow-to-specify-regular-expression-for-command-arguments-in-sudoers%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The sudoers
man page is fairly clear about not supporting this. Comments in the man page suggest that it uses the system fnmatch function to do the matching. On linux/glibc based systems fnmatch can use an extended globbing format with similar expressiveness to regular expressions but a different syntax.
Therefore if you should be able to rebuild sudo to support the extended syntax by finding the place where sudo calls fnmatch adding FNM_EXTMATCH to the flags argument.
and #define _GNU_SOURCE to the top of the file that calls it.
Of course if you do this you will be running your own hand patched version of an suid binary so be careful.
add a comment |
The sudoers
man page is fairly clear about not supporting this. Comments in the man page suggest that it uses the system fnmatch function to do the matching. On linux/glibc based systems fnmatch can use an extended globbing format with similar expressiveness to regular expressions but a different syntax.
Therefore if you should be able to rebuild sudo to support the extended syntax by finding the place where sudo calls fnmatch adding FNM_EXTMATCH to the flags argument.
and #define _GNU_SOURCE to the top of the file that calls it.
Of course if you do this you will be running your own hand patched version of an suid binary so be careful.
add a comment |
The sudoers
man page is fairly clear about not supporting this. Comments in the man page suggest that it uses the system fnmatch function to do the matching. On linux/glibc based systems fnmatch can use an extended globbing format with similar expressiveness to regular expressions but a different syntax.
Therefore if you should be able to rebuild sudo to support the extended syntax by finding the place where sudo calls fnmatch adding FNM_EXTMATCH to the flags argument.
and #define _GNU_SOURCE to the top of the file that calls it.
Of course if you do this you will be running your own hand patched version of an suid binary so be careful.
The sudoers
man page is fairly clear about not supporting this. Comments in the man page suggest that it uses the system fnmatch function to do the matching. On linux/glibc based systems fnmatch can use an extended globbing format with similar expressiveness to regular expressions but a different syntax.
Therefore if you should be able to rebuild sudo to support the extended syntax by finding the place where sudo calls fnmatch adding FNM_EXTMATCH to the flags argument.
and #define _GNU_SOURCE to the top of the file that calls it.
Of course if you do this you will be running your own hand patched version of an suid binary so be careful.
answered Sep 7 '18 at 19:05
William HayWilliam Hay
21317
21317
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f190981%2fhow-to-specify-regular-expression-for-command-arguments-in-sudoers%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown