oysteikt/heimdal
0
0
Fork 0
Code Issues 5 Pull Requests Releases Activity

spelling

Browse Source 
git-svn-id: svn://svn.h5l.se/heimdal/trunk/heimdal@19196 ec53bebd-3082-4978-b11e-865c3cabbd6b
This commit is contained in:
Love Hörnquist Åstrand
2006-11-30 16:55:56 +00:00
parent 7192fa06e8
commit 7690122914
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
doc/setup.texi
View File

@@ -1101,16 +1101,16 @@ name of the TGS of the target realm.
Both of these two requirements are not required by the standard to be
checked by the client if it have external information what the
certificate the KDC is supposed to be used. So its in the interst of
minium amount of configuration on the clients they should be included.
minimum amount of configuration on the clients they should be included.
Remember that if client would accept any certificate as the KDC's
certificate, the client could be fooled into trusting something that
isn't a KDC and thus expose the user to giving away information (like
password or other private information) that it is supposed to secret.
Also, if the extension certificate have a nameConstraints extention
with a Generalname with dNSName or iPAdress it must match the hostname
or adress of the KDC.
Also, if the certificate have a nameConstraints extention with a
Generalname with dNSName or iPAdress it must match the hostname or
adress of the KDC.
@subsection Client certificate