diff options
author | Alan Coopersmith <alan.coopersmith@oracle.com> | 2011-09-16 22:04:41 -0700 |
---|---|---|
committer | Alan Coopersmith <alan.coopersmith@oracle.com> | 2011-09-16 22:04:41 -0700 |
commit | 8fd15eb0149cec75d69a27b1f8ec3ce092465b80 (patch) | |
tree | d36d08983a09be32084a0e4d979a5168e1d5ddfe /README | |
parent | 063bfa679adc2c00a6b55e5c9ee97f2aa0638788 (diff) |
Strip trailing whitespace
Performed with: find * -type f | xargs perl -i -p -e 's{[ \t]+$}{}'
git diff -w & git diff -b show no diffs from this change
Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>
Diffstat (limited to 'README')
-rw-r--r-- | README | 6 |
1 files changed, 3 insertions, 3 deletions
@@ -38,7 +38,7 @@ This scheme involves changes to the following parts of the sample release: - add entries to user's auth file - remove entries from user's auth file -This mechanism assumes that the superuser and the transport layer between +This mechanism assumes that the superuser and the transport layer between the client and the server is secure. @@ -46,7 +46,7 @@ Description The sample implementation will use the xdm Display Manager to set up and control the server's authorization file. Sites that do not run xdm will -need to build their own mechanisms. +need to build their own mechanisms. Xdm uses a random key (seeded by the system time and check sum of /dev/kmem) to generate a unique sequence of characters at 16 bytes long. This sequence @@ -130,7 +130,7 @@ There are three types of input: name non-NULL, data NULL - use the named authorization; get data from that mechanism's default. name non-NULL, data non-NULL - use the given authorization and data. - + This interface is used by xdm and might also be used by any other applications that wish to explicitly set the authorization information. |