Global settings or directives in other virtual hosts cannot be edited. ![]() Creating a user with the right to edit directives in only a few Apache virtual servers that he owns.Some examples of the kind of access control restrictions that you can set up are : Because Webmin still runs with full root privileges even when used by a restricted user, it still has access to all the configuration files and commands that it needs. You can further restrict what the user can do within each module, so that he cannot abuse its features to perform actions that he is not supposed to. Webmin solves this kind of problem by allowing you to create additional users who can login, but only access a few modules. Unfortunately, once someone is able to login as root he has full control of the system and can do whatever he wants. On a normal Unix system, this person would have to be given root access so that he can edit the zone files and re-start the DNS server when necessary. For example, you may have a person in your organization whose job it is to create and edit DNS zones and records. However, there are many situations in which the administrator may want to give some people access to a subset of Webmin's features. Even if your system has multiple users, there may be only one who needed to perform system administration tasks. ![]() On a home or office system used by just one person, that is all you need. Introduction to Webmin users, groups and permissionsĪ standard, out-of-the-box Webmin installation has only one user (called root or admin) who can use every feature of every module. 2.8 Configuring the Webmin Users module.2.6 Viewing and disconnecting login sessions.1 Introduction to Webmin users, groups and permissions.
0 Comments
Leave a Reply. |