You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I edited the /etc/passwd file for privilege escalation, changed the user id and group id of my default user kyrie to 0. That is, each time I open a new windows terminal, I can use sudo -i -u kyrie to launch as user kyrie with full root privileges.
Everything seems working well, except that I cannot visit WSL2 file system from Windows explorer anymore. It reminded me that the address is invalid, and the Windows user is not permitted to visit it.
Is this problem expected?
Why does user privilege escalation in WSL2 lead to restrictions on Windows user?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I worked on Win11 with WSL2.
Problem
I edited the
/etc/passwd
file for privilege escalation, changed the user id and group id of my default userkyrie
to 0. That is, each time I open a new windows terminal, I can usesudo -i -u kyrie
to launch as user kyrie with full root privileges.Everything seems working well, except that I cannot visit WSL2 file system from Windows explorer anymore. It reminded me that the address is invalid, and the Windows user is not permitted to visit it.
Beta Was this translation helpful? Give feedback.
All reactions