The _x_a_u_t_h program is used to edit and display the authorization information used in connecting to the X server. This program is usually used to extract authorization records from one machine and merge them in on another (as is the case when using remote logins or granting access to other users). Commands (described below) may be entered interactively, on the _x_a_u_t_h command line, or in scripts. Note that this program does nnoott contact the X server except when the generate command is used. Normally _x_a_u_t_h is not used to create the authority file entry in the first place; _x_d_m does that.
This command is similar to add. The main difference is that instead of requiring the user to supply the key data, it connects to the server specified in _d_i_s_p_l_a_y_n_a_m_e and uses the SECURITY extension in order to get the key data to store in the authorization file. If the server cannot be contacted or if it does not support the SECURITY extension, the command fails. Otherwise, an authorization entry for the indicated display using the given protocol is added to the authorization file. A protocol name consisting of just a single period is treated as an abbreviation for _M_I_T_-_M_A_G_I_C_-_C_O_O_K_I_E_-_1.
If the ttrruusstteedd option is used, clients that connect using this authorization will have full run of the display, as usual. If uunnttrruusstteedd is used, clients that connect using this authorization will be considered untrusted and prevented from stealing or tampering with data belonging to trusted clients. See the SECURITY extension specification for full details on the restrictions imposed on untrusted clients. The default is uunnttrruusstteedd.
The ttiimmeeoouutt option specifies how long in seconds this authorization will be valid. If the authorization remains unused (no clients are connected with it) for longer than this time period, the server purges the authorization, and future attempts to connect using it will fail. Note that the purging done by the server does nnoott delete the authorization entry from the authorization file. The default timeout is 60 seconds.
The ggrroouupp option specifies the application group that clients connecting with this authorization should belong to. See the application group extension specification for more details. The default is to not belong to an application group.
The ddaattaa option specifies data that the server should use to generate the authorization. Note that this is nnoott the same data that gets written to the authorization file. The interpretation of this data depends on the authorization protocol. The _h_e_x_d_a_t_a is in the same format as the _h_e_x_k_e_y described in the add command. The default is to send no data.