The default behaviour of #202205191908 can be changed in the file /etc/ssh/ssh_config (system-wide) or ~/.ssh/config (user specific).
To allow #202205182136 #202203221227 by default, set ForwardX11 or ForwardX11Trusted (less secure) to yes in the config file on the client side and X11Forwarding to yes on the server side. This is corresponded to the -X and -Y option.
Since XDMCP doesn’t primarily concern with encryption of its protocol, this could be a security risk. Therefore, instead of using xhost, one can utilise the 202203221227# for XDMCP by using the option -X or -Y (-X is arguably more secure except for Debian) or setting options in 202205191924#. When using this method, it is not necessary to change the setting on the 202205182153#.
The keys are encrypted using one of the supported cryptographic algorithms such as dsa, rsa, ecdsa, ecdsa-sk, ed25519 or ed25519-sk. Such keys are usually stored in the /etc/ssh as ssh_host_rsa_key and ssh_host_dsa_key alongside with its configuration# files sshd_config and ssh_config. You can 202204272031# to other computers using the command ssh-copy-id.
-X or -Y could be used to tunnel the #X Display Manager Control Protocol (XDMCP). The first is usually the more secure option than the latter except in case of Debian. You can change the default behaviour of SSH by modifying SSH Configuration where you can omit the option.