How to fix postfix set-permissions without user named root?

Clash Royale CLAN TAG#URR8PPP
up vote
3
down vote
favorite
I'm trying to setup Postfix from Entware (a repo for embedded devices).
There is no SElinux involved and chroot is disabled in master.cf.
# postconf -n
command_directory = /opt/sbin
compatibility_level = 2
config_directory = /opt/etc/postfix
daemon_directory = /opt/libexec/postfix
data_directory = /opt/var/lib/postfix
debug_peer_level = 2
debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin ddd $daemon_directory/$process_name $process_id & sleep 5
default_database_type = cdb
inet_protocols = ipv4
mail_spool_directory = /opt/var/mail
manpage_directory = no
myhostname = domain.nl
mynetworks = 1.1.2.1,8.9.1.1
queue_directory = /opt/var/spool/postfix
shlib_directory = /opt/lib/postfix
smtputf8_enable = no
unknown_local_recipient_reject_code = 550
The issue is that postfix set-permissions isn't able to figure out the root user name. This distribution comes by default with a "root" user named "admin". At least I think that the user name is the issue, because of:
# postfix set-permissions
find: unknown user root
# ls -lah /opt/sbin/postdrop
-rwxr-xr-x 1 NewRootUser root 246.8K Sep 8 22:33 /opt/sbin/postdrop
Regression
With the help of https://wiki.zimbra.com/wiki/Steps_to_fix_permission_and_ownership_of_Postfix_binaries_manually_due_to_bug_on_zmfixperm is tried to fix the differences (755 was already set):
# chown AdminUserName:postdrop /opt/sbin/postdrop
# chown AdminUserName:postdrop /opt/sbin/postqueue
# chmod g+s /opt/sbin/postdrop
# chmod g+s /opt/sbin/postqueue
Result:
# postfix check
postsuper: fatal: scan_dir_push: open directory defer: Permission denied
Question
How to make postfix set-permissions learn the new root user name?
Or how to manually do the steps that postfix set-permissions should do?
Or where in the postfix source code can one find the actions that are executed for flag set-permissions?
permissions postfix
add a comment |Â
up vote
3
down vote
favorite
I'm trying to setup Postfix from Entware (a repo for embedded devices).
There is no SElinux involved and chroot is disabled in master.cf.
# postconf -n
command_directory = /opt/sbin
compatibility_level = 2
config_directory = /opt/etc/postfix
daemon_directory = /opt/libexec/postfix
data_directory = /opt/var/lib/postfix
debug_peer_level = 2
debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin ddd $daemon_directory/$process_name $process_id & sleep 5
default_database_type = cdb
inet_protocols = ipv4
mail_spool_directory = /opt/var/mail
manpage_directory = no
myhostname = domain.nl
mynetworks = 1.1.2.1,8.9.1.1
queue_directory = /opt/var/spool/postfix
shlib_directory = /opt/lib/postfix
smtputf8_enable = no
unknown_local_recipient_reject_code = 550
The issue is that postfix set-permissions isn't able to figure out the root user name. This distribution comes by default with a "root" user named "admin". At least I think that the user name is the issue, because of:
# postfix set-permissions
find: unknown user root
# ls -lah /opt/sbin/postdrop
-rwxr-xr-x 1 NewRootUser root 246.8K Sep 8 22:33 /opt/sbin/postdrop
Regression
With the help of https://wiki.zimbra.com/wiki/Steps_to_fix_permission_and_ownership_of_Postfix_binaries_manually_due_to_bug_on_zmfixperm is tried to fix the differences (755 was already set):
# chown AdminUserName:postdrop /opt/sbin/postdrop
# chown AdminUserName:postdrop /opt/sbin/postqueue
# chmod g+s /opt/sbin/postdrop
# chmod g+s /opt/sbin/postqueue
Result:
# postfix check
postsuper: fatal: scan_dir_push: open directory defer: Permission denied
Question
How to make postfix set-permissions learn the new root user name?
Or how to manually do the steps that postfix set-permissions should do?
Or where in the postfix source code can one find the actions that are executed for flag set-permissions?
permissions postfix
4
"renamed away from default "root".". This was a Known Bad Idea long ago. Most checks forroot, ortoor, or whatever, are actually checks forUID = 0, except for many hiddenUSERID = "root ". You'll never find them all. Renamingrootis all problems, no benefit.
â waltinator
Sep 27 at 16:37
github.com/vdukhovni/postfix/blob/⦠has onechownthat brings$userin; apparently from the command-line, environment, or main.cf
â Jeff Schaller
Sep 29 at 20:49
the permissions are stored in the inode, if somehow you can modify it to gain access to /etc/postfix/main.cf and /etc/postfix/master.cf to modify it manually via accessing the place it's stored in from other OS
â Yousef Al-Hadhrami
Sep 29 at 22:06
unix.stackexchange.com/questions/69191/â¦
â Yousef Al-Hadhrami
Sep 29 at 22:07
or try using chmod from other operating system to give access to new renamed user
â Yousef Al-Hadhrami
Sep 29 at 22:16
add a comment |Â
up vote
3
down vote
favorite
up vote
3
down vote
favorite
I'm trying to setup Postfix from Entware (a repo for embedded devices).
There is no SElinux involved and chroot is disabled in master.cf.
# postconf -n
command_directory = /opt/sbin
compatibility_level = 2
config_directory = /opt/etc/postfix
daemon_directory = /opt/libexec/postfix
data_directory = /opt/var/lib/postfix
debug_peer_level = 2
debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin ddd $daemon_directory/$process_name $process_id & sleep 5
default_database_type = cdb
inet_protocols = ipv4
mail_spool_directory = /opt/var/mail
manpage_directory = no
myhostname = domain.nl
mynetworks = 1.1.2.1,8.9.1.1
queue_directory = /opt/var/spool/postfix
shlib_directory = /opt/lib/postfix
smtputf8_enable = no
unknown_local_recipient_reject_code = 550
The issue is that postfix set-permissions isn't able to figure out the root user name. This distribution comes by default with a "root" user named "admin". At least I think that the user name is the issue, because of:
# postfix set-permissions
find: unknown user root
# ls -lah /opt/sbin/postdrop
-rwxr-xr-x 1 NewRootUser root 246.8K Sep 8 22:33 /opt/sbin/postdrop
Regression
With the help of https://wiki.zimbra.com/wiki/Steps_to_fix_permission_and_ownership_of_Postfix_binaries_manually_due_to_bug_on_zmfixperm is tried to fix the differences (755 was already set):
# chown AdminUserName:postdrop /opt/sbin/postdrop
# chown AdminUserName:postdrop /opt/sbin/postqueue
# chmod g+s /opt/sbin/postdrop
# chmod g+s /opt/sbin/postqueue
Result:
# postfix check
postsuper: fatal: scan_dir_push: open directory defer: Permission denied
Question
How to make postfix set-permissions learn the new root user name?
Or how to manually do the steps that postfix set-permissions should do?
Or where in the postfix source code can one find the actions that are executed for flag set-permissions?
permissions postfix
I'm trying to setup Postfix from Entware (a repo for embedded devices).
There is no SElinux involved and chroot is disabled in master.cf.
# postconf -n
command_directory = /opt/sbin
compatibility_level = 2
config_directory = /opt/etc/postfix
daemon_directory = /opt/libexec/postfix
data_directory = /opt/var/lib/postfix
debug_peer_level = 2
debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin ddd $daemon_directory/$process_name $process_id & sleep 5
default_database_type = cdb
inet_protocols = ipv4
mail_spool_directory = /opt/var/mail
manpage_directory = no
myhostname = domain.nl
mynetworks = 1.1.2.1,8.9.1.1
queue_directory = /opt/var/spool/postfix
shlib_directory = /opt/lib/postfix
smtputf8_enable = no
unknown_local_recipient_reject_code = 550
The issue is that postfix set-permissions isn't able to figure out the root user name. This distribution comes by default with a "root" user named "admin". At least I think that the user name is the issue, because of:
# postfix set-permissions
find: unknown user root
# ls -lah /opt/sbin/postdrop
-rwxr-xr-x 1 NewRootUser root 246.8K Sep 8 22:33 /opt/sbin/postdrop
Regression
With the help of https://wiki.zimbra.com/wiki/Steps_to_fix_permission_and_ownership_of_Postfix_binaries_manually_due_to_bug_on_zmfixperm is tried to fix the differences (755 was already set):
# chown AdminUserName:postdrop /opt/sbin/postdrop
# chown AdminUserName:postdrop /opt/sbin/postqueue
# chmod g+s /opt/sbin/postdrop
# chmod g+s /opt/sbin/postqueue
Result:
# postfix check
postsuper: fatal: scan_dir_push: open directory defer: Permission denied
Question
How to make postfix set-permissions learn the new root user name?
Or how to manually do the steps that postfix set-permissions should do?
Or where in the postfix source code can one find the actions that are executed for flag set-permissions?
permissions postfix
permissions postfix
edited Oct 2 at 20:37
asked Sep 27 at 13:01
Pro Backup
1,92352856
1,92352856
4
"renamed away from default "root".". This was a Known Bad Idea long ago. Most checks forroot, ortoor, or whatever, are actually checks forUID = 0, except for many hiddenUSERID = "root ". You'll never find them all. Renamingrootis all problems, no benefit.
â waltinator
Sep 27 at 16:37
github.com/vdukhovni/postfix/blob/⦠has onechownthat brings$userin; apparently from the command-line, environment, or main.cf
â Jeff Schaller
Sep 29 at 20:49
the permissions are stored in the inode, if somehow you can modify it to gain access to /etc/postfix/main.cf and /etc/postfix/master.cf to modify it manually via accessing the place it's stored in from other OS
â Yousef Al-Hadhrami
Sep 29 at 22:06
unix.stackexchange.com/questions/69191/â¦
â Yousef Al-Hadhrami
Sep 29 at 22:07
or try using chmod from other operating system to give access to new renamed user
â Yousef Al-Hadhrami
Sep 29 at 22:16
add a comment |Â
4
"renamed away from default "root".". This was a Known Bad Idea long ago. Most checks forroot, ortoor, or whatever, are actually checks forUID = 0, except for many hiddenUSERID = "root ". You'll never find them all. Renamingrootis all problems, no benefit.
â waltinator
Sep 27 at 16:37
github.com/vdukhovni/postfix/blob/⦠has onechownthat brings$userin; apparently from the command-line, environment, or main.cf
â Jeff Schaller
Sep 29 at 20:49
the permissions are stored in the inode, if somehow you can modify it to gain access to /etc/postfix/main.cf and /etc/postfix/master.cf to modify it manually via accessing the place it's stored in from other OS
â Yousef Al-Hadhrami
Sep 29 at 22:06
unix.stackexchange.com/questions/69191/â¦
â Yousef Al-Hadhrami
Sep 29 at 22:07
or try using chmod from other operating system to give access to new renamed user
â Yousef Al-Hadhrami
Sep 29 at 22:16
4
4
"renamed away from default "root".". This was a Known Bad Idea long ago. Most checks for
root, or toor, or whatever, are actually checks for UID = 0, except for many hidden USERID = "root ". You'll never find them all. Renaming root is all problems, no benefit.â waltinator
Sep 27 at 16:37
"renamed away from default "root".". This was a Known Bad Idea long ago. Most checks for
root, or toor, or whatever, are actually checks for UID = 0, except for many hidden USERID = "root ". You'll never find them all. Renaming root is all problems, no benefit.â waltinator
Sep 27 at 16:37
github.com/vdukhovni/postfix/blob/⦠has one
chown that brings $user in; apparently from the command-line, environment, or main.cfâ Jeff Schaller
Sep 29 at 20:49
github.com/vdukhovni/postfix/blob/⦠has one
chown that brings $user in; apparently from the command-line, environment, or main.cfâ Jeff Schaller
Sep 29 at 20:49
the permissions are stored in the inode, if somehow you can modify it to gain access to /etc/postfix/main.cf and /etc/postfix/master.cf to modify it manually via accessing the place it's stored in from other OS
â Yousef Al-Hadhrami
Sep 29 at 22:06
the permissions are stored in the inode, if somehow you can modify it to gain access to /etc/postfix/main.cf and /etc/postfix/master.cf to modify it manually via accessing the place it's stored in from other OS
â Yousef Al-Hadhrami
Sep 29 at 22:06
unix.stackexchange.com/questions/69191/â¦
â Yousef Al-Hadhrami
Sep 29 at 22:07
unix.stackexchange.com/questions/69191/â¦
â Yousef Al-Hadhrami
Sep 29 at 22:07
or try using chmod from other operating system to give access to new renamed user
â Yousef Al-Hadhrami
Sep 29 at 22:16
or try using chmod from other operating system to give access to new renamed user
â Yousef Al-Hadhrami
Sep 29 at 22:16
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
3
down vote
accepted
Applications which expect and use user name root will understandably fail when there is no such user on the system. However, you can have more than one user with same UID. Usually, you should probably not configure the system with multiple user names with same UID, similarly as you should not rename root user.
You can add another UID 0 account, which has the username root. This possibly solves issues with applications which use user names instead of numeric UIDs. To add another root user with disabled password and login, append following to /etc/passwd:
root:x:0:0:root:/root:/bin/false
Full syntax is explained in man 5 passwd.
With this/etc/passwdline, and aln -s /opt/sbin/sendmail.postfix /opt/sbin/sendmail, I was able topostfix set-permissionsand start postfix.
â Pro Backup
Oct 1 at 20:27
add a comment |Â
up vote
2
down vote
First, let me echo other's point that renaming the root user is a bad idea. That said, if you're set on doing it...
Where in the postfix source code can one find the actions that are executed for flag set-permissions?
The command postfix set-permissions seems to be handled by postfix/conf/postfix-script, which in turn calls post-install create-missing:
set-permissions|upgrade-configuration)
$daemon_directory/post-install create-missing "$@"
;;
https://github.com/vdukhovni/postfix/blob/bfff4380a3b6fac2513c73531ee3a79212c08660/postfix/conf/postfix-script#L376
https://github.com/vdukhovni/postfix/blob/bfff4380a3b6fac2513c73531ee3a79212c08660/postfix/conf/post-install#L245
You might have to search the repo for "root" and adjust anything that's expecting the administrator's username to be "root":
https://github.com/vdukhovni/postfix/search?p=3&q=root&unscoped_q=root
You answer says we are looking forz, andaleads tobleads toc, I am board, here are some links.
â ctrl-alt-delor
Oct 1 at 18:37
The question was where in the source is set-permissions handled. Providing a link to that point seemed like a legitimate answer. Did I then trace that all the way down to some point where "root" is used? Clearly not. Might the original author be able to do that with a concrete starting point? Hopefully.
â Andy Dalton
Oct 1 at 20:24
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
accepted
Applications which expect and use user name root will understandably fail when there is no such user on the system. However, you can have more than one user with same UID. Usually, you should probably not configure the system with multiple user names with same UID, similarly as you should not rename root user.
You can add another UID 0 account, which has the username root. This possibly solves issues with applications which use user names instead of numeric UIDs. To add another root user with disabled password and login, append following to /etc/passwd:
root:x:0:0:root:/root:/bin/false
Full syntax is explained in man 5 passwd.
With this/etc/passwdline, and aln -s /opt/sbin/sendmail.postfix /opt/sbin/sendmail, I was able topostfix set-permissionsand start postfix.
â Pro Backup
Oct 1 at 20:27
add a comment |Â
up vote
3
down vote
accepted
Applications which expect and use user name root will understandably fail when there is no such user on the system. However, you can have more than one user with same UID. Usually, you should probably not configure the system with multiple user names with same UID, similarly as you should not rename root user.
You can add another UID 0 account, which has the username root. This possibly solves issues with applications which use user names instead of numeric UIDs. To add another root user with disabled password and login, append following to /etc/passwd:
root:x:0:0:root:/root:/bin/false
Full syntax is explained in man 5 passwd.
With this/etc/passwdline, and aln -s /opt/sbin/sendmail.postfix /opt/sbin/sendmail, I was able topostfix set-permissionsand start postfix.
â Pro Backup
Oct 1 at 20:27
add a comment |Â
up vote
3
down vote
accepted
up vote
3
down vote
accepted
Applications which expect and use user name root will understandably fail when there is no such user on the system. However, you can have more than one user with same UID. Usually, you should probably not configure the system with multiple user names with same UID, similarly as you should not rename root user.
You can add another UID 0 account, which has the username root. This possibly solves issues with applications which use user names instead of numeric UIDs. To add another root user with disabled password and login, append following to /etc/passwd:
root:x:0:0:root:/root:/bin/false
Full syntax is explained in man 5 passwd.
Applications which expect and use user name root will understandably fail when there is no such user on the system. However, you can have more than one user with same UID. Usually, you should probably not configure the system with multiple user names with same UID, similarly as you should not rename root user.
You can add another UID 0 account, which has the username root. This possibly solves issues with applications which use user names instead of numeric UIDs. To add another root user with disabled password and login, append following to /etc/passwd:
root:x:0:0:root:/root:/bin/false
Full syntax is explained in man 5 passwd.
edited Oct 1 at 20:27
answered Sep 30 at 20:10
sebasth
7,24131745
7,24131745
With this/etc/passwdline, and aln -s /opt/sbin/sendmail.postfix /opt/sbin/sendmail, I was able topostfix set-permissionsand start postfix.
â Pro Backup
Oct 1 at 20:27
add a comment |Â
With this/etc/passwdline, and aln -s /opt/sbin/sendmail.postfix /opt/sbin/sendmail, I was able topostfix set-permissionsand start postfix.
â Pro Backup
Oct 1 at 20:27
With this
/etc/passwd line, and a ln -s /opt/sbin/sendmail.postfix /opt/sbin/sendmail, I was able to postfix set-permissions and start postfix.â Pro Backup
Oct 1 at 20:27
With this
/etc/passwd line, and a ln -s /opt/sbin/sendmail.postfix /opt/sbin/sendmail, I was able to postfix set-permissions and start postfix.â Pro Backup
Oct 1 at 20:27
add a comment |Â
up vote
2
down vote
First, let me echo other's point that renaming the root user is a bad idea. That said, if you're set on doing it...
Where in the postfix source code can one find the actions that are executed for flag set-permissions?
The command postfix set-permissions seems to be handled by postfix/conf/postfix-script, which in turn calls post-install create-missing:
set-permissions|upgrade-configuration)
$daemon_directory/post-install create-missing "$@"
;;
https://github.com/vdukhovni/postfix/blob/bfff4380a3b6fac2513c73531ee3a79212c08660/postfix/conf/postfix-script#L376
https://github.com/vdukhovni/postfix/blob/bfff4380a3b6fac2513c73531ee3a79212c08660/postfix/conf/post-install#L245
You might have to search the repo for "root" and adjust anything that's expecting the administrator's username to be "root":
https://github.com/vdukhovni/postfix/search?p=3&q=root&unscoped_q=root
You answer says we are looking forz, andaleads tobleads toc, I am board, here are some links.
â ctrl-alt-delor
Oct 1 at 18:37
The question was where in the source is set-permissions handled. Providing a link to that point seemed like a legitimate answer. Did I then trace that all the way down to some point where "root" is used? Clearly not. Might the original author be able to do that with a concrete starting point? Hopefully.
â Andy Dalton
Oct 1 at 20:24
add a comment |Â
up vote
2
down vote
First, let me echo other's point that renaming the root user is a bad idea. That said, if you're set on doing it...
Where in the postfix source code can one find the actions that are executed for flag set-permissions?
The command postfix set-permissions seems to be handled by postfix/conf/postfix-script, which in turn calls post-install create-missing:
set-permissions|upgrade-configuration)
$daemon_directory/post-install create-missing "$@"
;;
https://github.com/vdukhovni/postfix/blob/bfff4380a3b6fac2513c73531ee3a79212c08660/postfix/conf/postfix-script#L376
https://github.com/vdukhovni/postfix/blob/bfff4380a3b6fac2513c73531ee3a79212c08660/postfix/conf/post-install#L245
You might have to search the repo for "root" and adjust anything that's expecting the administrator's username to be "root":
https://github.com/vdukhovni/postfix/search?p=3&q=root&unscoped_q=root
You answer says we are looking forz, andaleads tobleads toc, I am board, here are some links.
â ctrl-alt-delor
Oct 1 at 18:37
The question was where in the source is set-permissions handled. Providing a link to that point seemed like a legitimate answer. Did I then trace that all the way down to some point where "root" is used? Clearly not. Might the original author be able to do that with a concrete starting point? Hopefully.
â Andy Dalton
Oct 1 at 20:24
add a comment |Â
up vote
2
down vote
up vote
2
down vote
First, let me echo other's point that renaming the root user is a bad idea. That said, if you're set on doing it...
Where in the postfix source code can one find the actions that are executed for flag set-permissions?
The command postfix set-permissions seems to be handled by postfix/conf/postfix-script, which in turn calls post-install create-missing:
set-permissions|upgrade-configuration)
$daemon_directory/post-install create-missing "$@"
;;
https://github.com/vdukhovni/postfix/blob/bfff4380a3b6fac2513c73531ee3a79212c08660/postfix/conf/postfix-script#L376
https://github.com/vdukhovni/postfix/blob/bfff4380a3b6fac2513c73531ee3a79212c08660/postfix/conf/post-install#L245
You might have to search the repo for "root" and adjust anything that's expecting the administrator's username to be "root":
https://github.com/vdukhovni/postfix/search?p=3&q=root&unscoped_q=root
First, let me echo other's point that renaming the root user is a bad idea. That said, if you're set on doing it...
Where in the postfix source code can one find the actions that are executed for flag set-permissions?
The command postfix set-permissions seems to be handled by postfix/conf/postfix-script, which in turn calls post-install create-missing:
set-permissions|upgrade-configuration)
$daemon_directory/post-install create-missing "$@"
;;
https://github.com/vdukhovni/postfix/blob/bfff4380a3b6fac2513c73531ee3a79212c08660/postfix/conf/postfix-script#L376
https://github.com/vdukhovni/postfix/blob/bfff4380a3b6fac2513c73531ee3a79212c08660/postfix/conf/post-install#L245
You might have to search the repo for "root" and adjust anything that's expecting the administrator's username to be "root":
https://github.com/vdukhovni/postfix/search?p=3&q=root&unscoped_q=root
answered Oct 1 at 18:17
Andy Dalton
4,9791520
4,9791520
You answer says we are looking forz, andaleads tobleads toc, I am board, here are some links.
â ctrl-alt-delor
Oct 1 at 18:37
The question was where in the source is set-permissions handled. Providing a link to that point seemed like a legitimate answer. Did I then trace that all the way down to some point where "root" is used? Clearly not. Might the original author be able to do that with a concrete starting point? Hopefully.
â Andy Dalton
Oct 1 at 20:24
add a comment |Â
You answer says we are looking forz, andaleads tobleads toc, I am board, here are some links.
â ctrl-alt-delor
Oct 1 at 18:37
The question was where in the source is set-permissions handled. Providing a link to that point seemed like a legitimate answer. Did I then trace that all the way down to some point where "root" is used? Clearly not. Might the original author be able to do that with a concrete starting point? Hopefully.
â Andy Dalton
Oct 1 at 20:24
You answer says we are looking for
z, and a leads to b leads to c, I am board, here are some links.â ctrl-alt-delor
Oct 1 at 18:37
You answer says we are looking for
z, and a leads to b leads to c, I am board, here are some links.â ctrl-alt-delor
Oct 1 at 18:37
The question was where in the source is set-permissions handled. Providing a link to that point seemed like a legitimate answer. Did I then trace that all the way down to some point where "root" is used? Clearly not. Might the original author be able to do that with a concrete starting point? Hopefully.
â Andy Dalton
Oct 1 at 20:24
The question was where in the source is set-permissions handled. Providing a link to that point seemed like a legitimate answer. Did I then trace that all the way down to some point where "root" is used? Clearly not. Might the original author be able to do that with a concrete starting point? Hopefully.
â Andy Dalton
Oct 1 at 20:24
add a comment |Â
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
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f471821%2fhow-to-fix-postfix-set-permissions-without-user-named-root%23new-answer', 'question_page');
);
Post as a guest
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
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
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
4
"renamed away from default "root".". This was a Known Bad Idea long ago. Most checks for
root, ortoor, or whatever, are actually checks forUID = 0, except for many hiddenUSERID = "root ". You'll never find them all. Renamingrootis all problems, no benefit.â waltinator
Sep 27 at 16:37
github.com/vdukhovni/postfix/blob/⦠has one
chownthat brings$userin; apparently from the command-line, environment, or main.cfâ Jeff Schaller
Sep 29 at 20:49
the permissions are stored in the inode, if somehow you can modify it to gain access to /etc/postfix/main.cf and /etc/postfix/master.cf to modify it manually via accessing the place it's stored in from other OS
â Yousef Al-Hadhrami
Sep 29 at 22:06
unix.stackexchange.com/questions/69191/â¦
â Yousef Al-Hadhrami
Sep 29 at 22:07
or try using chmod from other operating system to give access to new renamed user
â Yousef Al-Hadhrami
Sep 29 at 22:16