summaryrefslogtreecommitdiff
path: root/modules/pam_xauth/README
diff options
context:
space:
mode:
Diffstat (limited to 'modules/pam_xauth/README')
-rw-r--r--modules/pam_xauth/README4
1 files changed, 2 insertions, 2 deletions
diff --git a/modules/pam_xauth/README b/modules/pam_xauth/README
index 4e0e3ec4..a32822d2 100644
--- a/modules/pam_xauth/README
+++ b/modules/pam_xauth/README
@@ -8,14 +8,14 @@ The pam_xauth PAM module is designed to forward xauth keys (sometimes referred
to as "cookies") between users.
Without pam_xauth, when xauth is enabled and a user uses the su(1) command to
-assume another user's priviledges, that user is no longer able to access the
+assume another user's privileges, that user is no longer able to access the
original user's X display because the new user does not have the key needed to
access the display. pam_xauth solves the problem by forwarding the key from the
user running su (the source user) to the user whose identity the source user is
assuming (the target user) when the session is created, and destroying the key
when the session is torn down.
-This means, for example, that when you run su(1) from an xterm sesssion, you
+This means, for example, that when you run su(1) from an xterm session, you
will be able to run X programs without explicitly dealing with the xauth(1)
xauth command or ~/.Xauthority files.