ubuntu20.04桌面允许root用户登录

root@node11:~# vi /usr/share/lightdm/lightdm.conf.d/50-ubuntu.conf

Seat:\*

user-session=ubuntu
greeter-show-manual-login=true
all-guest=false

"/usr/share/lightdm/lightdm.conf.d/50-ubuntu.conf" 4L, 76C written

root@node11:~# vi /etc/pam.d/gdm-autologin

#%PAM-1.0

auth requisite pam_nologin.so
#auth required pam_succeed_if.so user != root quiet_success

auth optional pam_gdm.so

auth optional pam_gnome_keyring.so

auth required pam_permit.so

@include common-account

SELinux needs to be the first session rule. This ensures that any

lingering context has been cleared. Without this it is possible

that a module could execute code in the wrong domain.

session success=ok ignore=ignore module_unknown=ignore default=bad pam_selinux.so close

session required pam_loginuid.so

SELinux needs to intervene at login time to ensure that the process

starts in the proper default security context. Only sessions which are

intended to run in the user's context should be run after this.

session success=ok ignore=ignore module_unknown=ignore default=bad pam_selinux.so open

session optional pam_keyinit.so force revoke

session required pam_limits.so

session required pam_env.so readenv=1

session required pam_env.so readenv=1 user_readenv=1 envfile=/etc/default/locale

@include common-session

session optional pam_gnome_keyring.so auto_start

@include common-password

~

"/etc/pam.d/gdm-autologin" 23L, 1193C written

root@node11:~# vi /etc/pam.d/gdm-password

#%PAM-1.0

auth requisite pam_nologin.so
#auth required pam_succeed_if.so user != root quiet_success

@include common-auth

auth optional pam_gnome_keyring.so

@include common-account

SELinux needs to be the first session rule. This ensures that any

lingering context has been cleared. Without this it is possible

that a module could execute code in the wrong domain.

session success=ok ignore=ignore module_unknown=ignore default=bad pam_selinux.so close

session required pam_loginuid.so

SELinux needs to intervene at login time to ensure that the process

starts in the proper default security context. Only sessions which are

intended to run in the user's context should be run after this.

pam_selinux.so changes the SELinux context of the used TTY and configures

SELinux in order to transition to the user context with the next execve()

call.

session success=ok ignore=ignore module_unknown=ignore default=bad pam_selinux.so open

session optional pam_keyinit.so force revoke

session required pam_limits.so

session required pam_env.so readenv=1

session required pam_env.so readenv=1 user_readenv=1 envfile=/etc/default/locale

@include common-session

session optional pam_gnome_keyring.so auto_start

@include common-password

"/etc/pam.d/gdm-password" 25L, 1321C written

root@node11:~# vi /root/.profile

~/.profile: executed by Bourne-compatible login shells.

if "$BASH" ; then

if -f \~/.bashrc ; then

. ~/.bashrc

fi

fi

#mesg n 2> /dev/null || true
tty -s && mesg n || true

. "$HOME/.cargo/env"

~

~

~

~

~

".profile" 12L, 209C written

root@node11:~#

参考:

https://comate.baidu.com/zh/page/ug2pso36mvo

相关推荐
镜舟科技2 分钟前
Databricks 再提 LTAP,AI 时代的数据底座为何重回大一统叙事?
数据库·架构·agent
Databend1 小时前
从湖仓升级为 Agent 时代的数据控制面,Snowflake 和 Databricks 有哪些布局
大数据·数据库·agent
ClouGence4 小时前
SQL Server CDC 能放到 Always On 备库读吗?一文讲透原理与实践
数据库·sql server
你好潘先生6 小时前
别再记命令了,用 yeero do 说句人话就能跑脚本,而且不烧 token
服务器·python·命令行
先吃饱再说21 小时前
存储的进化:从 MySQL 到浏览器缓存,数据到底住在哪?
数据库
Nturmoils21 小时前
字段太多看不全,ksql 的展开模式和输出控制怎么用
数据库·后端
Databend1 天前
Agent 轨迹分析与归因的数据工程实践
大数据·数据库·agent
这个DBA有点耶1 天前
SQL改写进阶:标量子查询的“隐形代价”与消除实战
数据库·mysql·架构
程序员老赵1 天前
服务器文件不想 SFTP 上传?Docker 跑个 File Browser,浏览器就能管理
服务器·docker·开源
smallyoung1 天前
数据库乐观锁深度解析:MySQL、PostgreSQL 实战 + Spring Boot 集成指南
数据库·mysql·postgresql