Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

How to view all users and all user groups under linux

2025-02-25 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Development >

Share

Shulou(Shulou.com)06/02 Report--

This article shows you how to view all users and all user groups under linux. The content is concise and easy to understand. It will definitely brighten your eyes. I hope you can get something through the detailed introduction of this article.

Groups to view the group members of the currently logged in user

Groups gliethttp views the group in which the gliethttp user belongs and the members of the group

Whoami to view the current login user name

The / etc/group file contains all groups

All usernames that exist on / etc/shadow and / etc/passwd systems

1. / etc/group commentary

The / etc/group file is a profile of a user group, which includes users and user groups, and can show which user group or user groups a user belongs to, because a user can belong to one or more different user groups; users of the same user group have similar characteristics. For example, if we add a user to the root user group, then the user can browse the file in the root user's home directory. If the root user opens the read and write permissions of a file, all users of the root user group can modify the file. If it is an executable file (such as a script), the root user group can also execute the file.

The characteristics of user groups provide great convenience for system administrators in system management, but security is also worth paying attention to. For example, if a user has the most important content for system management, it is best to let the user have an independent user group, or set the permissions of the files under the user to be completely private; in addition, the root user group generally does not easily add ordinary users.

2. / specific analysis of the content of etc/group

The content of / etc/group includes user group (Group), user group password, GID and users (User) contained in this user group, with one record for each user group. The format is as follows:

Group_name:passwd:GID:user_list

Each record in / etc/group is divided into four fields:

First field: user group name

Second field: user group password

The third field: GID

Fourth field: user list, separated by a sign between each user; this field can be blank; if the field is blank, it indicates that the user name of the user group is GID

Overview of Linux user (user) and user Group (group) Management

Reference website: http://fedora.linuxsir.org/main/?q=node/91

1. Understand Linux's concepts of single-user multi-task, multi-user multi-task.

Linux is a multi-user and multi-task operating system; we should understand the concepts of single-user multi-task and multi-user multi-task.

1. Single user and multi-task of Linux

Single user multitasking; for example, we log in to the system as beinan, and after entering the system, I want to open gedit to write documents, but in the process of writing documents, I feel that there is less music, so I turn on xmms to have some music; of course, it is not enough to listen to some music, MSN still has to open, want to know what several brothers are doing now, so, when I log in with beinan users, I execute gedit, xmms and msn, and of course, the input method fcitx It's a little simple to say that a beinan user performs several tasks in order to get the job done; of course, the beinan user, other people can log in remotely and do other tasks.

2. Multi-user and multi-task of Linux

Sometimes it is possible that many users use the same system at the same time, but not all users have to do the same thing, so it is said that there are multiple users and multiple tasks.

For example, for a LinuxSir.Org server, there are FTP users, system administrators, web users, regular users, etc. At the same time, some brothers may be visiting the forum; some may be uploading software package management substations, such as luma or Yuking brothers, who are managing their home system and FTP; at the same time, there may also be system administrators maintaining the system. Nobody users are used to browse the home page, and everyone uses the same user, while FTP users are used to upload software packages; administrators may use ordinary accounts or super privilege root accounts to maintain or view the system; different users have different permissions, and different users need different users to accomplish different tasks, or different users may complete different tasks.

It is worth noting that multi-user multi-task is not when everyone joins the keyboard and monitor of a machine at the same time to operate the machine. Multi-user may do it through remote login, such as remote control of the server. As long as anyone has user rights, anyone can go up and operate or access it.

3. Distinguishing the roles of users

Users are divided into roles in the system, and in the Linux system, due to different roles, permissions and tasks are also different. it is worth noting that users' roles are identified through UID, especially UID; in system management, the system administrator must adhere to the unique characteristics of UID.

Root user: the system is unique, is real, can log in to the system, can operate any file and command, and has the highest permissions

Virtual users: these users are also called pseudo users or fake users, which are distinguished from real users. These users do not have the ability to log in to the system, but they are indispensable users for the operation of the system, such as bin, daemon, adm, ftp, mail, etc. These users are owned by the system itself, not added later. Of course, we can also add virtual users.

Ordinary real users: these users can log in to the system, but can only operate the contents of their own home directory; their permissions are limited; these users are added by the system administrator himself.

4. Security of multi-user operating system

In fact, multi-user system is more convenient for system management. From a security point of view, a multi-user managed system is more secure. For example, a file under the beinan user does not want other users to see, but only set the permissions of the file. Only beinan can read, write and edit. In this way, only beinan can operate on its private files. Linux performs best under multiple users, and Linux can protect the security of each user. But we also have to learn that Linux is a secure system, which is not secure without security-conscious administrators or management techniques.

From the server point of view, multi-user system security is also the most important. Our commonly used Windows operating system can only be said to be general in terms of rights management. There is no way to compare with Linux or Unix systems.

II. User (user) and user group (group) concepts

1. The concept of user

Through the previous understanding of Linux multi-user, we understand that Linux is a real multi-user operating system, so we can build several users (user) in Linux system. For example, our colleague wants to use my computer, but I don't want him to log in with my user name, because there are materials and information under my user name that I don't want others to see (that is, private content). Then I can create a new user name for him and let him use my user name to deal with it, which is in line with the operating rules from the point of view of computer security.

Of course, the concept of user is not limited to that. There are also some users in the Linux system who are used to accomplish specific tasks, such as nobody and ftp. When we visit the web program of LinuxSir.Org, we are nobody users; when we visit ftp anonymously, we use the user ftp or nobody; if you want to know some accounts of the Linux system, please check / etc/passwd

2. The concept of user group (group)

A group is a collection of users with the same characteristics (user) For example, sometimes we want multiple users to have the same permissions, such as viewing or modifying a file or executing a command, then we need a user group, and we define all users to the same user group. By modifying the permissions of the file or directory, let the user group have certain operation rights, so that the users under the user group have the same permissions on the file or directory. This is achieved by defining groups and modifying file permissions.

For example: in order to give some users the right to view a certain document, such as a schedule, and the person who wrote the schedule should have read and write permission, we want some users to know the contents of the schedule and not let them modify it. So we can put these users into a group, and then modify the permissions of the file to make the user group readable. So that every user under the user group is readable

The corresponding relationship between users and user groups is one-to-one, many-to-one, one-to-many or many-to-many.

One-to-one: a user can be the only member of a group

Many-to-one: multiple users can be members of a unique group and do not belong to other user groups; for example, beinan and linuxsir only belong to the beinan user group

One-to-many: a user can be a member of multiple user groups; for example, beinan can be a member of a root group, a linuxsir user group, or an adm user group

Many-to-many: multiple users correspond to multiple user groups, and several users can belong to the same group; in fact, the many-to-many relationship is an extension of the first three; after understanding the above three, this one can also be understood

Configuration files, commands or directories related to users (user) and user groups (group)

1. Profiles related to users (user) and user groups (group)

1) profile related to the user (user)

/ etc/passwd Note: profile of user (user)

/ etc/shadow Note: user (user) shadow password file

2) configuration files related to user groups (group)

/ etc/group Note: user Group (group) profile

/ etc/gshadow Note: shadow file of user group (group)

2. Tools or commands for managing users (user) and user groups (group)

1) tools or commands for managing users (user)

Useradd Note: add user

Adduser Note: add user

Passwd Note: set the password for the user

Usermod Note: modify user commands, you can use usermod to modify login, user's home directory, and so on.

Pwcov Note: synchronize users from / etc/passwd to / etc/shadow

Pwck Note: pwck verifies whether the contents of the user profile / etc/passwd and / etc/shadow files are legal or complete

Pwunconv Note: it is a vertical reverse operation of pwcov, which creates / etc/passwd from / etc/shadow and / etc/passwd, and then deletes the / etc/shadow file

Finger Note: view user Information tool id Note: view user's UID, GID and user groups to which they belong chfn Note: change user Information tool

Su Note: user switching tool sudo Note: sudo executes commands (execute a command as another user) through another user, and su is used to switch users, and then complete the corresponding tasks by switching to the user.

But sudo can execute commands directly later, for example, sudo can execute root assigned execution without root password, and only root can execute corresponding commands; but it has to be edited / etc/sudoers through visudo.

Visudo Note: visodo is the command for editing / etc/sudoers; you can also use vi to edit / etc/sudoers directly without this command.

Sudoedit Note: similar to sudo function

2) tools or commands for managing user groups (group)

Groupadd Note: add a user group

Groupdel note: delete a user group

Groupmod Note: modify user group information

Groups note: displays the user group to which the user belongs

Grpck grpconv Note: synchronize or create / etc/gshadow through the file contents of / etc/group and / etc/gshadow, or create / etc/gshadow if / etc/gshadow does not exist

Grpunconv Note: synchronize or create / etc/group with the contents of / etc/group and / etc/gshadow files, and then delete the gshadow file

3. / etc/skel directory

The / etc/skel directory is generally the directory where the user startup files are stored. This directory is controlled by root permissions. When we add users, the files in this directory are automatically copied to the newly added user's home directory; the files in the / etc/skel directory are all hidden files, that is, similar to the .file format. We can provide users with a unified, standard and default user environment by modifying, adding and deleting files in the / etc/skel directory.

[root@localhost beinan] # ls-la / etc/skel/

Total dosage 92

Drwxr-xr-x 3 root root 4096 August 11 23:32.

Drwxr-xr-x 115 root root 12288 October 14 13:44..

-rw-r-r- 1 root root 24 May 11 00:15. Bash _ logout

-rw-r-r- 1 root root 191 May 11 00:15. Bash _ profile

-rw-r-r- 1 root root 124 May 11 00:15 .bashrc

-rw-r-r- 1 root root 5619 2005-03-08 .canna

-rw-r-r- 1 root root 438 May 18 15:23. Emacs

-rw-r-r- 1 root root 120 May 23 05:18 .gtkrc

Drwxr-xr-x 3 root root 4096 August 11 23:16. KDE

-rw-r-r- 1 root root 658 2005-01-17 .zshrc

The files under the / etc/skel directory are usually copied to the home directory of the newly added user (user) automatically when we use the useradd and adduser commands to add users (user). If we add users by modifying / etc/passwd, we can create the user's home directory ourselves, then copy the files under / etc/skel to the user's home directory, and then use chown to change the owner of the new user's home directory.

4. / etc/login.defs configuration file

The / etc/login.defs file is some planning when creating a user, such as whether a home directory is required when creating a user, the scope of UID and GID, the duration of the user, and so on. This file can be defined through root.

For example, the contents of the / etc/logins.defs file of Fedora

REQUIRED # Directory where mailboxes reside, or name of file, relative to the # home directory. If you do define both, MAIL_DIR takes precedence.QMAIL_DIR is for Qmail#QMAIL_DIR Maildir MAIL_DIR / var/spool/mail Note: when creating a user, create a user mail file in the directory / var/spool/mail # MAIL_FILE .mailPassword aging controls:PASS_MAX_DAYS Maximum number of days a password may be used.PASS_MIN_DAYS Minimum number of days allowed between password changes.PASS_MIN_LEN Minimum acceptable password length.PASS_WARN_AGE Number of days warning given before a password expires.PASS_MAX_DAYS 99999 Note: the maximum number of days that a user's password does not expire

PASS_MIN_DAYS 0 Note: the minimum number of days between password changes

PASS_MIN_LEN 5 Note: minimum password length

PASS_WARN_AGE 7 Note: #

Min/max values for automatic uid selection in useraddUID_MIN 60000 Note: the minimum UID is 500. that is to say, when adding users, the UID starts at 500. note: UID_MAX 60000 Note: the maximum UID is 60000 this command is run when removing a user.It should remove any at/cron/print jobs etc Minbinarmax values for automatic gid selection in groupadd # GID_MIN 500Note: GID starts at 500. GID_MAX 60000If defined, this command is run when removing a user.It should remove any at/cron/print jobs etc. Owned bythe user to be removed (passed as the first argument).

# USERDEL_CMD / usr/sbin/userdel_local #

If useradd should create home directories for users by defaultOn RH systems, we do. This option is ORed with the-m flag onuseradd command line

. # CREATE_HOME yes Note: whether to create a user's home directory is required.

5. / etc/default/useradd file

Rules file when adding users through useradd

Useradd defaults file

GROUP=100

HOME=/home Note: build the user's home directory in / home

INACTIVE=-1 Note: whether to enable account expiration suspension.-1 means it is not enabled.

EXPIRE= Note: account termination date. If not set, it will not be enabled.

SHELL=/bin/bash Note: type of SHELL used

SKEL=/etc/skel Note: the default directory for adding users is the default location of files; that is, when we add users with adduser, all the files in the user's home directory are copied from this directory.

Postscript:

There is about so much about the management of users (user) and user groups (group). As long as you understand and master what is mentioned above, users (user) and user groups (group) will manage almost. Since users (user) and user groups (group) are associated with file and directory permissions, the operation of file and directory permissions will be introduced to you separately.

This article only makes novice brothers understand some principles of user and group, so when I write this article, I mostly explain the content. I mean, by explaining and indexing some commands, it is important to let novice brothers understand a little bit of theory, and technical operation is nothing more than the use of commands.

=

Learning notes on Linux users, user groups, and file permissions

Reference website: http://www.sourcejoy.com/other_dev_tech/linux-user-and-file-manage.html

Recently, I plan to study the linux operating system more carefully. First, I made up for the three more important knowledge of users, user groups and file permissions.

To learn these things, you must first master the relevant knowledge of the authority system of linux.

The authority system of linux is mainly composed of users, user groups and permissions.

Users are users who log in and use linux one by one. The interior of the linux is represented by UID.

A user group is a grouping of users. The interior of the linux is represented by GID.

Permissions are divided into three permissions: read, write and execute.

The user information of linux is saved in the / etc/passwd file. In addition, the / etc/shadow file stores the information about the user's password.

/ etc/passwd file format:

User name: password: UID:GID: user Information: HOME directory path: user shell

If UID is 0, root,1~499 is the system user, and more than 500 are ordinary users.

/ etc/shadow saves user password information, including encrypted password, password expiration time, password expiration prompt days, etc.

User group information is saved in the / etc/group file.

The format is as follows:

User group name: group password: GID: accounts in the group (multiple accounts are separated by commas)

After the user logs in, the GID in the / etc/passwd file is the user's initial user group.

The fact that the user's initial user group is no longer reflected in / etc/group.

View the user group commands for the current user:

[root@local opt] # groups

Root bin daemon sys adm disk wheel

In the output information, the first user group is the current user's valid user group (current user group)

Toggle valid user groups command:

[root@local opt] # newgrp user group name

To leave the new valid user group, enter exit enter.

New user command:

[root@local opt] # useradd user name-g initial user group-G other user group (modify / etc/group)-c user description-u specifies UID

After the user is built, you need to set the password for the user:

[root@local opt] # passwd user name

Users want to change their own password command:

[root@local opt] # passwd

Modify user information command:

[root@local opt] # usermod parameter user name

Parameters:

-c description

-g group name initial user group

-e expiration date format: YYYY-MM-DD

-G group name other user group

-l modify the user name

-L lock the account (add two exclamation marks (!!) in front of the user's corresponding password string in the / etc/shadow file)

-U unlock

Delete user command:

[root@local opt] # userdel [- r] username

Where parameter-r is the home directory of the deleted user.

In fact, there may be this user file in other parts of the system. To delete a user and his file completely, you must first find the file that belongs to him:

[root@local opt] # find /-user user name

Then delete, and then run userdel to delete the user.

View the available shell commands:

[root@local opt] # chsh-l

Modify your own shell command:

[root@local opt] # chsh-s

View your own or someone's UID/GID information:

[root@local opt] # id [user name] groups is a valid user group in the returned information

Add user group commands:

[root@local opt] # groupadd user group name

Modify user group name command:

[root@local opt] # groupmod-n name

Delete user group command:

[root@local opt] # groupdel user group name

Set user group password command:

[root@local opt] # gpasswd user group name

If gpasswd is added with parameters, it has other functions

Set up user group administrator commands:

[root@local opt] # gpasswd-A user name user group name

Add an account to the group command:

[root@local opt] # gpasswd-M user name user group name

Remove an account from the group command:

[root@local opt] # gpasswd-d user name user group name

Operation of passwd related parameters:

-l lock user

-u unlock the user

-n days password cannot be changed

-x days password expiration days

-w days warning days

File permission knowledge

Let's take a look at an example:

[root@local opt] # ls-al

The ls-al command lists all files in the directory, including hidden files. The first character of the name of the hidden file is'.'

-rw-r-r- 1 root root 81 08-02 14:54 gtkrc-1.2-gnome2

-rw--- 1 root root 18908-02 14:54 ICEauthority

-rw--- 1 root root 35 08-05 10:02. Lesshst

Drwx-- 3 root root 4096 08-02 14:54. Metacity

Drwxr-xr-x 3 root root 4096 08-02 14:54 nautilus

The columns of the list are defined as follows:

[permission attribute information] [number of connections] [owner] [user group to which the owner belongs] [size] [last modified time] [file name]

The list of permission attributes is 10 characters:

The first character represents the file type, d is the directory-the ordinary file l is the connection b is the storable interface device c is the input device such as keyboard and mouse

2, 3, 4 characters represent owner permissions, 5, 6, 7 characters indicate owner user rights in the same group, and 8, 9, 10 are other user permissions.

The second character indicates the owner read permission, r if you have permission, and-

The third character represents the owner's write permission, w if you have permission, and-

The fourth character represents the owner's permission to execute, x if you have permission, and-

The fifth character indicates that the owner has read permission for the same group of users, r if he has permission, and-

The sixth character indicates that the owner has write permission for the same group of users, w if he has permission, and-

The seventh character indicates that the owner has the same group of users to execute permissions, x if he has permission, and-

The eighth character indicates other different group read permissions, r if you have permission, and-

The ninth character represents other write permissions of different groups, w if you have permission, and-

The tenth character represents other non-group execution permissions, x if you have permission, and-

Modify the group command to which the file belongs:

[root@local opt] # chgrp [- R] group name file name

Where-R is set recursively

Modify the owner and group commands of the file:

[root@local opt] # chown [- R] user [: user group] file name

Modify file access command:

[root@local opt] # chmod [- R] 0777 filename

Linux's method of viewing users and user groups

Whois

Function description: find and display user information.

Syntax: whois [account name] Supplementary Note: the whois command will find and display the relevant information about the user of the specified account. Because it is searched in Network Solutions's WHOIS database, the account name must be registered above to be found, and there is no case difference in the name. Whoami

Function description: first it seems that the user name.

Syntax: whoami [- help] [- version] add: display your own user name, this instruction is equivalent to the execution of the "id-un" instruction.

Parameters:

-help online help.

-version displays version information. Who

Function description: displays the user information currently logged in to the system.

Syntax: who [- Himqsw] [- help] [- version] [am I] [log file] add: execute this instruction to know which users are currently logged into the system, and executing the who command alone will list the login account, the terminal used, the login time and where you logged in or which X monitor you are using.

Parameters:

-H or-heading displays the header information column of each field.

-I or-u or-idle shows idle time, and if the user takes any action within the previous minute, it will be marked "." If the user has not taken any action for more than 24 hours, the string "old" is marked.

-m this parameter has the same effect as the specified "am I" string.

-Q or-count displays only the account name and total number of people logged in to the system.

-s this parameter will be ignored and will not be processed, and will only be responsible for solving the compatibility problem of other versions of the who directive.

-w or-T or-mesg or-message or-writable displays the user's information status bar.

-help online help.

-version displays version information. W

Function description: displays the user information currently logged in to the system.

Grammar: W [- fhlsuV] [user name] add: execute this instruction to know who are currently logged in to the system and the programs they are executing. Execute w separately

The directive displays all users, or you can specify a user name to display only information about a user.

Parameters:

-f turns on or off showing where the user logs in to the system.

-h does not display the title information column of each field.

-l uses a detailed format list, which is the default value.

-s uses a concise format list and does not show the login time of the user, the CPU time spent by the terminal phase jobs and programs.

-u ignores the name of the executing program and the information that the program takes CPU time.

-V displays version information. Finger command

The function of the finger command is to query the user's information, which usually displays the user name, home directory, stagnation time, login time, login shell and other information of a user in the system. If you want to query user information on a remote machine, you need to follow the user name with "@ hostname" in the format of [username @ hostname], but the network host you want to query needs to run the finger daemon.

The general format of the command is:

The meanings of the options in the finger [options] [user] [user @ host] command are as follows:

-s displays the user's registration name, actual name, terminal name, write status, stagnation time, login time and other information.

In addition to the information displayed with the-s option, it also displays information such as the user's home directory, login shell, mail status, and the contents of .plan, .project, and .forward files under the user's home directory.

-p is the same as the-l option except that the .plan file and .project file are not displayed.

Use the finger command on the local machine.

$finger xxq

Login: xxq Name:

Directory: / home/xxq Shell: / bin/bash

Last login Thu Jan 1 21:43 (CST) on tty1

No mail.

No Plan.

$finger

Login Name Tty Idle Login Time Office Office Phone

Root root * 1 28 Nov 25 09:17

……

The / etc/group file contains all groups

All usernames that exist on / etc/shadow and / etc/passwd systems

The method of modifying the group to which the current user belongs

Usermod or you can modify the / etc/paaawd file directly to vlock (virtual console lock)

Function description: lock the virtual terminal.

Syntax: vlock [- achv] added that executing the vlock instruction can lock the virtual terminal and prevent others from using it.

Parameters:

-an or-all locks all terminal phase jobs, and if you use this parameter in a full-screen terminal, you will use the keyboard

The function of switching terminals is also turned off.

-c or-current locks the current terminal phase job, which is the default value.

-h or-help online help.

-v or-version displays version information.

Usermod

Function description: modify user account.

Grammar: usermod [- LU] [- c] [- d] [- e] [- f] [- g] [- G] [- l] [- s] [- u] [user account]

Note: usermod can be used to modify the settings of a user's account.

Parameters:

-c modify the remarks of the user account.

-d login directory > modify the directory when the user logs in.

-e modify the validity period of the account.

-f modify how many days after the password expires to close the account.

-g modify the group to which the user belongs.

-G modifies the additional group to which the user belongs.

-l modify the user account name.

-L locks the user's password, invalidating it.

-s modifies the shell used by the user after login.

-u modify user ID.

-U unlocks the password.

Userdel

Function description: delete user account.

Syntax: userdel [- r] [user account] Note: userdel can delete user account and related files. If no parameters are added, only the user account will be deleted, not the related files.

Parameters:

-f Delete the user login directory and all files in the directory.

Userconf

Function description: user account setting program.

Grammar: userconf [--addgroup] [--adduser] [--delgroup] [--deluser] [--help] adds that userconf is actually the symbolic connection of linuxconf, providing a graphical interface for administrators to establish and manage all kinds of accounts. If you do not add any parameters, you will enter the graphical interface.

Parameters:

-- A new group is added to addgroup.

-- add a user account to adduser.

-- delgroup deletes the group.

-- deluser deletes user accounts.

-- help displays help.

Useradd

Function description: set up user account.

Grammar: useradd [- mMnr] [- c] [- d] [- e] [- f] [- g] [- G] [- s] [- u] [user account] or useradd-D [- b] [- e] [- f] [- g] [- G] [- s]

Note: useradd can be used to set up user accounts. After the account is set up, use passwd to set the password of the account. You can use userdel to delete the account. The account created using the useradd directive is actually saved in the / etc/passwd text file.

Parameters:

-c plus remarks. The remarks text is saved in the comments field of passwd.

-d specifies the starting directory when the user logs in.

-D change the default value.

-e specifies the validity period of the account.

-f specifies how many days after the password expires, the account will be closed.

-g specifies the group to which the user belongs.

-G specifies the additional group to which the user belongs.

-m automatically sets up the login directory of the user.

-M do not automatically create a user's login directory.

-n cancels the creation of a group with the user name.

-r set up a system account.

-s specifies the shell that the user will use after logging in.

-u specifies the user ID. What is Linux system Linux is a free-to-use and free-spread UNIX-like operating system, is a POSIX-based multi-user, multi-task, multi-threaded and multi-CPU operating system, using Linux can run major Unix tools, applications and network protocols.

The above is how to view all users and all user groups under linux. Have you learned any knowledge or skills? If you want to learn more skills or enrich your knowledge reserve, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 222

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Development

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report