[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
password changing from Windows
[Sorry, I just managed to send the previous copy when I was trying to
attach the diff. Maybe the Gnus keybindings aren't ideal :-/.]
The current release says it supports the Windows password-change
protocol. Are you expected to be able to use this with the normal
Windows ctl-alt-del change password business when authenticating
against Heimdal via Active Directory with a trust relationship?
When I try it from Windows XP with a Windows 2003 AD controller
trusting Heimdal 0.6.3, Windows says the password can't be changed.
The KDC log does show a changepw ticket being issued.
If it should work, any suggestions for configuration fixes or
debugging? Thanks.
--- Makefile.am 2004/12/17 10:53:09 1.1
+++ Makefile.am 2004/12/17 10:55:01
@@ -5,4 +5,7 @@
AUTOMAKE_OPTIONS = no-texinfo.tex
info_TEXINFOS = heimdal.texi
-heimdal_TEXINFOS = intro.texi install.texi setup.texi kerberos4.texi apps.texi
+heimdal_TEXINFOS = ack.texi apps.texi heimdal.texi install.texi \
+ intro.texi kerberos4.texi migration.texi misc.texi \
+ programming.texi setup.texi whatis.texi win2k.texi
+
--- setup.texi 2004/12/17 13:53:07 1.1
+++ setup.texi 2004/12/17 14:48:12
@@ -41,9 +41,9 @@
The configuration file is a hierarchical structure consisting of
sections, each containing a list of bindings (either variable
assignments or subsections). A section starts with
-@samp{[section-name]}. A binding consists of a left hand side, an equal
+@samp{[@var{section-name}]}. A binding consists of a left hand side, an equal
(@samp{=}) and a right hand side (the left hand side tag must be
-separated from the equal with some whitespace.) Subsections has a
+separated from the equal with some whitespace). Subsections have a
@samp{@{} as the first non-whitespace character after the equal. All
other bindings are treated as variable assignments. The value of a
variable extends to the end of the line.
@@ -73,7 +73,7 @@
The @samp{libdefaults} section contains a list of library configuration
parameters, such as the default realm and the timeout for KDC
responses. The @samp{realms} section contains information about specific
-realms, such as where they hide their KDC. This section serves the same
+realms, such as where they hide their KDC@. This section serves the same
purpose as the Kerberos 4 @file{krb.conf} file, but can contain more
information. Finally the @samp{domain_realm} section contains a list of
mappings from domains to realms, equivalent to the Kerberos 4
@@ -96,8 +96,8 @@
@end example
If you use a realm name equal to your domain name, you can omit the
-@samp{libdefaults}, and @samp{domain_realm}, sections. If you have a
-SRV-record for your realm, or your Kerberos server has CNAME called
+@samp{libdefaults}, and @samp{domain_realm}, sections. If you have a DNS
+SRV record for your realm, or your Kerberos server has a CNAME
@samp{kerberos.my.realm}, you can omit the @samp{realms} section too.
@node Creating the database, keytabs, Configuration file, Setting up a realm
@@ -105,7 +105,7 @@
The database library will look for the database in the directory
@file{/var/heimdal}, so you should probably create that directory.
-Make sure the directory have restrictive permissions.
+Make sure the directory has restrictive permissions.
@example
# mkdir /var/heimdal
@@ -125,24 +125,24 @@
If you want to generate a random master key you can use the
--random-key to kstash. This will make sure you have a good key
-attackers can't do a dictionary attack on the master key.
+on which attackers can't do a dictionary attack.
If you have a master key, make sure you make a backup of your master
-key file, without it, backups of the database is of no use.
+key file; without it backups of the database are of no use.
-To initialise the database use the @code{kadmin} program, with the
+To initialise the database use the @command{kadmin} program, with the
@samp{-l} option (to enable local database mode). First issue a
@kbd{init MY.REALM} command. This will create the database and insert
default principals for that realm. You can have more than one realm in
one database, so @samp{init} does not destroy any old database.
Before creating the database, @samp{init} will ask you some questions
-about max ticket lifetimes.
+about maximum ticket lifetimes.
After creating the database you should probably add yourself to it. You
do this with the @samp{add} command. It takes as argument the name of a
-principal. The principal should contain a realm, so if you haven't setup
-a default realm, you will need to explicitly include the realm.
+principal. The principal should contain a realm, so if you haven't set
+up a default realm, you will need to explicitly include the realm.
@example
# kadmin -l
@@ -187,7 +187,7 @@
@node keytabs, Serving Kerberos 4/524/kaserver, Creating the database, Setting up a realm
@section keytabs
-To extract a service ticket from the database and put it in a keytab you
+To extract a service ticket from the database and put it in a keytab, you
need to first create the principal in the database with @samp{ank}
(using the @kbd{--random-key} flag to get a random key) and then
extract it with @samp{ext_keytab}.
@@ -210,8 +210,8 @@
@section Serving Kerberos 4/524/kaserver
Heimdal can be configured to support 524, Kerberos 4 or kaserver. All
-theses services are default turned off. Kerberos 4 support also
-depends on if Kerberos 4 support is compiled in with Heimdal.
+these services are turned off by default. Kerberos 4 support also
+depends on Kerberos 4 support being compiled in with Heimdal.
@subsection 524
@@ -228,7 +228,7 @@
@subsection Kerberos 4
-Kerberos 4 is the predecessor to to Kerberos 5. It only support single
+Kerberos 4 is the predecessor to to Kerberos 5. It only supports single
DES. You should only enable Kerberos 4 support if you have a need for
for compatibility with an installed base of Kerberos 4 clients/servers.
@@ -241,11 +241,11 @@
@subsection kaserver
-Kaserver is a Kerberos 4 that is used in AFS, the protocol have some
-features over plain Kerberos 4, but like Kerberos 4 only use single
-DES too.
+Kaserver is a Kerberos 4 that is used in AFS. The protocol has some extra
+features over plain Kerberos 4 but, like Kerberos 4, only uses single
+DES@.
-You should only enable Kerberos 4 support if you have a need for for
+You should only enable Kaserver support if you have a need for for
compatibility with an installed base of AFS machines.
Kaserver can be turned on by adding this to the configuration file
@@ -258,9 +258,9 @@
@node Remote administration, Password changing, Serving Kerberos 4/524/kaserver, Setting up a realm
@section Remote administration
-The administration server, @samp{kadmind}, can be started by
-@samp{inetd} (which isn't recommended) or run as a normal daemon. If you
-want to start it from @samp{inetd} you should add a line similar to the
+The administration server, @command{kadmind}, can be started by
+@command{inetd} (which isn't recommended) or run as a normal daemon. If you
+want to start it from @command{inetd} you should add a line similar to the
one below to your @file{/etc/inetd.conf}.
@example
@@ -268,28 +268,29 @@
@end example
You might need to add @samp{kerberos-adm} to your @file{/etc/services}
-as 749/tcp.
+as @samp{749/tcp}.
-Access to the administration server is controlled by an acl-file, (default
-@file{/var/heimdal/kadmind.acl}.) The lines in the access file, has the
+Access to the administration server is controlled by an ACL file, (default
+@file{/var/heimdal/kadmind.acl}.) The lines in the access file, have the
following syntax:
@smallexample
principal [priv1,priv2,...] [glob-pattern]
@end smallexample
-The matching is from top to bottom for matching principal (and if given,
-glob-pattern). When there is a match, the rights of that lines are
+The matching is from top to bottom for matching principals (and if given,
+glob-pattern). When there is a match, the right-hand parts of that line are
used.
The privileges you can assign to a principal are: @samp{add},
@samp{change-password} (or @samp{cpw} for short), @samp{delete},
@samp{get}, @samp{list}, and @samp{modify}, or the special privilege
@samp{all}. All of these roughly corresponds to the different commands
-in @samp{kadmin}.
+in @command{kadmin}.
-If a @var{glob-pattern} is given on a line, it restricts the right for
+If a @var{glob-pattern} is given on a line, it restricts the
+right-hand part for
the principal to only apply for the subjects that match the pattern.
-The patters are of the same type as those used in shell globbing, see
+The patterns are of the same type as those used in shell globbing, see
@url{none,,fnmatch(3)}.
In the example below @samp{lha/admin} can change every principal in the
@@ -309,20 +310,21 @@
@node Password changing, Testing clients and servers, Remote administration, Setting up a realm
@section Password changing
-To allow users to change their passwords, you should run @samp{kpasswdd}.
-It is not run from @samp{inetd}.
+To allow users to change their passwords, you should run @command{kpasswdd}.
+It is not run from @command{inetd}.
-You might need to add @samp{kpasswd} to your @file{/etc/services} as
+You might need to add @command{kpasswd} to your @file{/etc/services} as
464/udp.
@subsection Password quality assurance
It is important that users have good passwords, both to make it harder
-to guess them and to avoid off-line attacks (pre-authentication provides
+to guess them and to avoid off-line attacks (although
+pre-authentication provides
some defense against off-line attacks). To ensure that the users choose
good passwords, you can enable password quality controls in
-@samp{kpasswdd}. The controls themselves are done in a shared library
-that is used by @samp{kpasswdd}. To configure in these controls, add
+@command{kpasswdd}. The controls themselves are done in a shared library
+that is used by @command{kpasswdd}. To configure in these controls, add
lines similar to the following to your @file{/etc/krb5.conf}:
@example
@@ -340,7 +342,7 @@
@end example
The function should verify that @var{pwd} is a good password for
-@var{principal} and if so return @code{NULL}. If it is deemed to be of
+@var{principal}, and if so, return @code{NULL}. If it is deemed to be of
low quality, it should return a string explaining why that password
should not be used.
@@ -351,7 +353,7 @@
@url{ftp://ftp.pdc.kth.se/pub/krb/src/cracklib.patch}.
If no password quality checking function is configured, it is only
-verified that it is at least six characters of length.
+verified that it is at least six characters long.
@node Testing clients and servers, Slave Servers, Password changing, Setting up a realm
@section Testing clients and servers
@@ -366,21 +368,21 @@
master server fails. It is possible to have any number of such slave
servers but more than three usually doesn't buy much more redundancy.
-All Kerberos servers for a realm shall have the same database so that
+All Kerberos servers for a realm must have the same database so that
they present the same service to all the users. The
@pindex hprop
-@code{hprop} program, running on the master, will propagate the database
+@command{hprop} program, running on the master, will propagate the database
to the slaves, running
@pindex hpropd
-@code{hpropd} processes.
+@command{hpropd} processes.
Every slave needs a database directory, the master key (if it was used
for the database) and a keytab with the principal
@samp{hprop/@var{hostname}}. Add the principal with the
@pindex ktutil
-@code{ktutil} command and start
+@command{ktutil} command and start
@pindex hpropd
-@code{propd}, as follows:
+@command{propd}, as follows:
@example
slave# ktutil get -p foo/admin hprop/`hostname`
@@ -395,36 +397,36 @@
Then run
@pindex hprop
-@code{hprop} on the master:
+@command{hprop} on the master:
@example
master# hprop slave
@end example
-This was just an on-hands example to make sure that everything was
-working properly. Doing it manually is of course the wrong way and to
+This was just a hands-on example to make sure that everything was
+working properly. Doing it manually is of course the wrong way, and to
automate this you will want to start
@pindex hpropd
-@code{hpropd} from @code{inetd} on the slave(s) and regularly run
+@command{hpropd} from @command{inetd} on the slave(s) and regularly run
@pindex hprop
-@code{hprop} on the master to regularly propagate the database.
-Starting the propagation once an hour from @code{cron} is probably a
+@command{hprop} on the master to propagate the database.
+Starting the propagation once an hour from @command{cron} is probably a
good idea.
@node Incremental propagation, Salting , Slave Servers, Setting up a realm
@section Incremental propagation
-There is also a newer and still somewhat experimental mechanism for
+There is also a newer, and still somewhat experimental, mechanism for
doing incremental propagation in Heimdal. Instead of sending the whole
database regularly, it sends the changes as they happen on the master to
-the slaves. The master keeps track of all the changes by assigned a
+the slaves. The master keeps track of all the changes by assigning a
version number to every change to the database. The slaves know which
was the latest version they saw and in this way it can be determined if
-they are in sync or not. A log of all the changes is kept on the master
-and when a slave is at an older versioner than the oldest one in the
+they are in sync or not. A log of all the changes is kept on the master,
+and when a slave is at an older version than the oldest one in the
log, the whole database has to be sent.
-Protocol-wise, all the slaves connects to the master and as a greeting
+Protocol-wise, all the slaves connect to the master and as a greeting
tell it the latest version that they have (@samp{IHAVE} message). The
master then responds by sending all the changes between that version and
the current version at the master (a series of @samp{FORYOU} messages)
@@ -432,8 +434,8 @@
@subsection Configuring incremental propagation
-The program that runs on the master is @code{ipropd-master} and all
-clients run @code{ipropd-slave}.
+The program that runs on the master is @command{ipropd-master} and all
+clients run @command{ipropd-slave}.
Create the file @file{/var/heimdal/slaves} on the master containing all
the slaves that the database should be propagated to. Each line contains
@@ -445,7 +447,7 @@
for some peculiar reason, you can use the @kbd{--port} option. This is
useful when you have multiple realms to distribute from one server.
-Then you need to create these principals that you added in the
+Then you need to create those principals that you added in the
configuration file. Create one @samp{iprop/hostname} for the master and
for every slave.
@@ -454,13 +456,13 @@
master# /usr/heimdal/sbin/ktutil get iprop/`hostname`
@end example
-The next step is to start the @code{ipropd-master} process on the master
-server. The @code{ipropd-master} listens on the UNIX-socket
+The next step is to start the @command{ipropd-master} process on the master
+server. The @command{ipropd-master} listens on the UNIX domain socket
@file{/var/heimdal/signal} to know when changes have been made to the
database so they can be propagated to the slaves. There is also a
safety feature of testing the version number regularly (every 30
seconds) to see if it has been modified by some means that do not raise
-this signal. Then, start @code{ipropd-slave} on all the slaves:
+this signal. Then, start @command{ipropd-slave} on all the slaves:
@example
master# /usr/heimdal/libexec/ipropd-master &
@@ -475,7 +477,7 @@
keys. Using a salt increases the search space to make it almost
impossible to precalculate all keys. Salting is the process of mixing a
public string (the salt) with the password, then sending it through an
-encryption-type specific string-to-key function that will output the
+encryption type-specific string-to-key function that will output the
fixed size encryption key.
In Kerberos 5 the salt is determined by the encryption-type, except
@@ -483,7 +485,7 @@
In @code{des} there is the Kerberos 4 salt
(none at all) or the afs-salt (using the cell (realm in
-afs-lingo)).
+AFS lingo)).
In @code{arcfour} (the encryption type that Microsoft Windows 2000 uses)
there is no salt. This is to be compatible with NTLM keys in Windows
@@ -499,23 +501,23 @@
salt (remember that if the salt is appended/prepended, the empty salt ""
is the same thing as no salt at all).
-Common types of salting includes
+Common types of salting include
@itemize @bullet
@item @code{v4} (or @code{des:pw-salt:})
-The Kerberos 4 salting is using no salt att all. Reason there is colon
-that the end or the salt string is that it makes the salt the empty
+The Kerberos 4 salting is using no salt at all. The reason there is colon
+at the end or the salt string is that it makes the salt the empty
string (same as no salt).
@item @code{v5} (or @code{pw-salt})
-@code{pw-salt} means all regular encryption-types that is regular
+@code{pw-salt} means all regular encryption-types that is regular @c fixme: ??
@item @code{afs3-salt}
-@code{afs3-salt} is the salting that is used with Transarc kaserver. Its
-the cell appended to the password.
+@code{afs3-salt} is the salt that is used with Transarc kaservers. It
+is the cell appended to the password.
@end itemize
@@ -523,14 +525,14 @@
@section Cross realm
@cindex Cross realm
-Suppose you are residing in the realm @samp{MY.REALM}, how do you
+Suppose you reside in the realm @samp{MY.REALM}: how do you
authenticate to a server in @samp{OTHER.REALM}? Having valid tickets in
-@samp{MY.REALM} allows you to communicate with kerberised services in that
+@samp{MY.REALM} allows you to communicate with Kerberised services in that
realm. However, the computer in the other realm does not have a secret
key shared with the Kerberos server in your realm.
-It is possible to add a share keys between two realms that trust each
-other. When a client program, such as @code{telnet} or @code{ssh},
+It is possible to share keys between two realms that trust each
+other. When a client program, such as @computer{telnet} or @computer{ssh},
finds that the other computer is in a different realm, it will try to
get a ticket granting ticket for that other realm, but from the local
Kerberos server. With that ticket granting ticket, it will then obtain
@@ -543,7 +545,7 @@
@samp{krbtgt/MY.REALM@@OTHER.REALM} and
@samp{krbtgt/OTHER.REALM@@MY.REALM}in @samp{OTHER.REALM}.
-In Kerberos 5 the trust can be one configured to be one way. So that
+In Kerberos 5 the trust can be configured to be one way, so that
users from @samp{MY.REALM} can authenticate to services in
@samp{OTHER.REALM}, but not the opposite. In the example above, the
@samp{krbtgt/MY.REALM@@OTHER.REALM} then should be removed.
@@ -589,14 +591,14 @@
@cindex Transit policy
If you want to use cross realm authentication through an intermediate
-realm it must be explicitly allowed by either the KDCs or the server
+realm, it must be explicitly allowed by either the KDCs or the server
receiving the request. This is done in @file{krb5.conf} in the
@code{[capaths]} section.
When the ticket transits through a realm to another realm, the
destination realm adds its peer to the "transited-realms" field in the
-ticket. The field is unordered, this is since there is no way to know if
-know if one of the transited-realms changed the order of the list.
+ticket. The field is unordered, since there is no way to know if
+one of the transited realms changed the order of the list.
The syntax for @code{[capaths]} section:
@@ -610,7 +612,7 @@
@end example
The realm @code{STACKEN.KTH.SE} allows clients from @code{SU.SE} and
-@code{DSV.SU.SE} to cross in. Since @code{STACKEN.KTH.SE} only have
+@code{DSV.SU.SE} to cross it. Since @code{STACKEN.KTH.SE} only have
direct cross realm with @code{KTH.SE}, and @code{DSV.SU.SE} only have direct cross
realm with @code{SU.SE} they need to use both @code{SU.SE} and
@code{KTH.SE} as transit realms.
@@ -631,8 +633,8 @@
The order of the @code{PERMITTED-CROSS-REALMS} is not important when
doing transit cross realm verification.
-But the order is important when the @code{[capaths]} section is used
-to figure out the intermediate realm to go to when doing multi realm
+However the order is important when the @code{[capaths]} section is used
+to figure out the intermediate realm to go to when doing multi-realm
transit. When figuring out the next realm, the first realm of the list
of @code{PERMITTED-CROSS-REALMS} is chosen. This is done in both the
client kerberos library and the KDC.
@@ -648,11 +650,11 @@
If there is information about where to find the KDC or kadmind for a
realm in the @file{krb5.conf} for a realm, that information will be
-preferred and DNS will not be queried.
+preferred, and DNS will not be queried.
Heimdal will try to use DNS to find the KDCs for a realm. First it
-will try to find @code{SRV} resource record (RR) for the realm. If no
-SRV RRs are found, it will fall back to looking for a @code{A} RR for
+will try to find a @code{SRV} resource record (RR) for the realm. If no
+SRV RRs are found, it will fall back to looking for an @code{A} RR for
a machine named kerberos.REALM, and then kerberos-1.REALM, etc
Adding this information to DNS makes the client have less
@@ -660,12 +662,12 @@
system administrator to change the number of KDCs and on what machines
they are running without caring about clients.
-The backside of using DNS that the client might be fooled to use the
+The down side of using DNS is that the client might be fooled to use the
wrong server if someone fakes DNS replies/data, but storing the IP
addresses of the KDC on all the clients makes it very hard to change
the infrastructure.
-Example of the configuration for the realm @code{EXAMPLE.COM},
+An example of the configuration for the realm @code{EXAMPLE.COM}:
@example
@@ -684,15 +686,15 @@
@subsection Using DNS to map hostname to Kerberos realm
-Heimdal also support a way to lookup realm from a hostname. This to
-minimize configuration needed on clients. Using this have the backdraw
-that clients can be redirect by an attacker to realms within the same
-cross realm trust and made belive they talk to the right server (since
-kerberos authentication will succeed).
+Heimdal also supports a way to lookup a realm from a hostname. This to
+minimize configuration needed on clients. Using this has the drawback
+that clients can be redirected by an attacker to realms within the
+same cross realm trust and made to believe they are talking to the
+right server (since Kerberos authentication will succeed).
-Example configuration that informs clients that for the realms
+An example configuration that informs clients that for the realms
it.example.com and srv.example.com, they should use the realm
-EXAMPLE.COM.
+EXAMPLE.COM:
@example
@@ -707,7 +709,7 @@
@cindex Using the LDAP backend
This document describes how to install the LDAP backend for
-Heimdal. Note that, before attempting to configure such an
+Heimdal. Note that before attempting to configure such an
installation, you should be aware of the implications of storing
private information (such as users' keys) in a directory service
primarily designed for public information. Nonetheless, with a
@@ -715,7 +717,7 @@
secure fashion. A knowledge of LDAP, Kerberos, and C is necessary to
install this backend. The HDB schema was devised by Leif Johansson.
-Requirements
+Requirements:
@itemize @bullet
@@ -724,14 +726,15 @@
@code{--with-openldap=/usr/local} (adjust according to where you have
installed OpenLDAP).
-You can verify that you manage to configure ldap support by running
-@file{kdc --builtin-hdb}, ``ldap:'' as one entry in the list.
+You can verify that you managed to configure LDAP support by running
+@file{kdc --builtin-hdb}, and checking that @samp{ldap:} is one entry
+in the list.
-Its also possible to configure the ldap backend as a shared module,
-see option --hdb-openldap-module to configure.
+Its also possible to configure the LDAP backend as a shared module
+see option @kbd{--hdb-openldap-module} to @command{configure}.
@item
-OpenLDAP 2.0.x. Configure OpenLDAP with --enable-local to enable the
+OpenLDAP 2.0.x. Configure OpenLDAP with @kbd{--enable-local} to enable the
local transport. (A patch to support SASL EXTERNAL authentication is
necessary in order to use OpenLDAP 2.1.x.)
@@ -754,14 +757,14 @@
The sasl-regexp is for mapping between the SASL/EXTERNAL and a user in
a tree. The user that the key is mapped to should be have a
krb5Principal aux object with krb5PrincipalName set so that the
-``creator'' and ``modifier'' gets right in @file{kadmin}.
+``creator'' and ``modifier'' is right in @command{kadmin}.
Another option is to create an admins group and add the dn to that
group.
-You also needs to make sure its possible for the KDC to connect
-without encryption, the connection is already secure, its done over a
-local unix socket. Comment out ``sasl-secprops minssf'' in the
+You also needs to make sure it is possible for the KDC to connect
+without encryption. The connection is already secure---it is done over a
+local Unix socket. Comment out @samp{sasl-secprops minssf} in the
configuration file.
@example
@@ -776,19 +779,19 @@
include /usr/local/etc/openldap/schema/krb5-kdc.schema
@end example
-Start the slapd with the local listener (as well as the default TCP/IP
+Start @samp{slapd} with the local listener (as well as the default TCP/IP
listener on port 389) as follows:
@example
slapd -h "ldapi:/// ldap:///"
@end example
-Note: These is a bug in slapd where it appears to corrupt the krb5Key
+Note: These is a bug in @samp{slapd} where it appears to corrupt the krb5Key
binary attribute on shutdown. This may be related to our use of the V3
schema definition syntax instead of the old UMich-style, V2 syntax.
@item
-You should specify a the distinguished name under which your
+You should specify the distinguished name under which your
principals will be stored in @file{krb5.conf}:
@example
@@ -799,12 +802,12 @@
@}
@end example
-mkey_file can be excluded if you feel that you trust your ldap
+@samp{mkey_file} can be excluded if you feel that you trust your LDAP
directory to have the raw keys inside it.
@item
-Once you have built Heimdal and started the LDAP server, run kadmin
+Once you have built Heimdal and started the LDAP server, run @command{kadmin}
(as usual) to initialize the database. Note that the instructions for
stashing a master key are as per any Heimdal installation.
@@ -824,7 +827,7 @@
kadmin> exit
@end example
-Verify that the principal database has indeed been stored at the
+Verify that the principal database has indeed been stored in the
directory with the following command:
@example
@@ -849,6 +852,6 @@
Write text here.
-Note that the samba domain and the realm realm can have diffrent names
-since arcfour's string to key function principal/realm independent.
+Note that the Samba domain and the realm can have diffrent names
+since arcfour's string to key function is principal/realm independent.
--- win2k.texi 2004/12/10 17:21:04 1.1
+++ win2k.texi 2004/12/21 14:15:46
@@ -10,12 +10,13 @@
that we have found out while trying to test Heimdal against Windows
2000. Another big problem with the Kerberos implementation in Windows
2000 is that the available documentation is more focused on getting
-things to work rather than how they work and not that useful in figuring
+things to work rather than how they work, and not that useful in figuring
out how things really work.
This information should apply to Heimdal @value{VERSION} and Windows
-2000 Professional. It's of course subject all the time and mostly consists of
-our not so inspired guesses. Hopefully it's still somewhat useful.
+2000 Professional. It's of course subject to change all the time and
+mostly consists of our not so inspired guesses. Hopefully it's still
+somewhat useful.
@menu
* Configuring Windows 2000 to use a Heimdal KDC::
@@ -31,15 +32,15 @@
@comment node-name, next, precious, up
@section Configuring Windows 2000 to use a Heimdal KDC
-You need the command line program called @code{ksetup.exe} which is available
-in the file @code{SUPPORT/TOOLS/SUPPORT.CAB} on the Windows 2000 Professional
+You need the command line program called @command{ksetup.exe} which is available
+in the file @file{SUPPORT/TOOLS/SUPPORT.CAB} on the Windows 2000 Professional
CD-ROM. This program is used to configure the Kerberos settings on a
Workstation.
-@code{Ksetup} store the domain information under the registry key:
+@command{ksetup} stores the domain information under the registry key:
@code{HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\LSA\Kerberos\Domains}.
-Use the kadmin program in Heimdal to create a host principal in the
+Use the @command{kadmin} program in Heimdal to create a host principal in the
Kerberos realm.
@example
@@ -47,7 +48,7 @@
kadmin> ank --password=password host/datan.example.com
@end example
-The name @code{datan.example.com} should be replaced with DNS name of
+The name @samp{datan.example.com} should be replaced with DNS name of
the workstation.
You must configure the workstation as a member of a workgroup, as opposed
@@ -58,26 +59,26 @@
C:> ksetup /addkdc EXAMPLE.COM kdc.example.com
@end example
-Set the machine password, i.e. create the local keytab:
+Set the machine password, i.e.@: create the local keytab:
@example
C:> ksetup /setmachpassword password
@end example
-The password used in @code{ksetup /setmachpassword} must be the same
-as the password used in the @code{kadmin ank} command.
+The password used in @kbd{ksetup /setmachpassword} must be the same
+as the password used in the @kbd{kadmin ank} command.
The workstation must now be rebooted.
-A mapping between local NT users and Kerberos principals must be specified,
-you have two choices:
+A mapping between local NT users and Kerberos principals must be specified.
+You have two choices. First:
@example
C:> ksetup /mapuser user@@MY.REALM nt_user
@end example
-This will map a user to a specific principal, this allows you to have
+This will map a user to a specific principal; this allows you to have
other usernames in the realm than in your NT user database. (Don't ask
-me why on earth you would want that...)
+me why on earth you would want that@enddots{})
You can also say:
@example
@@ -98,18 +99,18 @@
By default the trust will be non-transitive. This means that only users
directly from the trusted domain may authenticate. This can be changed
-to transitive by using the @code{netdom.exe} tool. @code{netdom.exe}
+to transitive by using the @command{netdom.exe} tool. @command{netdom.exe}
can also be used to add the trust between two realms.
You need to tell Windows 2000 on what hosts to find the KDCs for the
-non-Windows realm with @code{ksetup}, see @xref{Configuring Windows 2000
+non-Windows realm with @command{ksetup}, see @xref{Configuring Windows 2000
to use a Heimdal KDC}.
-This need to be done on all computers that want enable cross-realm
-login with @code{Mapped Names}.
+This needs to be done on all computers that want to enable cross-realm
+login with @code{Mapped Names}. @c fixme: probably shouldn't be @code
-Then you need to add the inter-realm keys on the Windows kdc. Start the
-Domain Tree Management tool. (Found in Programs, Administrative tools,
+Then you need to add the inter-realm keys on the Windows KDC@. Start the
+Domain Tree Management tool (found in Programs, Administrative tools,
Active Directory Domains and Trusts).
Right click on Properties of your domain, select the Trust tab. Press
@@ -117,26 +118,29 @@
password. When prompted if this is a non-Windows Kerberos realm, press
OK.
-Do not forget to add trusts in both directions.
+Do not forget to add trusts in both directions (if that's what you want).
-If you want to use @code{netdom.exe} instead of the Domain Tree
-Management tool, you do it like this,
+If you want to use @command{netdom.exe} instead of the Domain Tree
+Management tool, you do it like this:
@example
netdom trust NT.REALM.EXAMPLE.COM /Domain:EXAMPLE.COM /add /realm /passwordt:TrustPassword
@end example
-You also need to add the inter-realm keys to the Heimdal KDC. There are
-some tweaks that you need to do to @file{krb5.conf} beforehand.
+You also need to add the inter-realm keys to the Heimdal KDC@.
+@c fixme: this doesn't seem to work, and it's apparently not necessary
+@c with Windows 2003.
+There are
+some tweaks that you need to do to @file{krb5.conf} beforehand:
@example
[libdefaults]
- default_etypes = des-cbc-crc
- default_etypes_des = des-cbc-crc
+ default_etypes = des-cbc-crc
+ default_etypes_des = des-cbc-crc
@end example
since otherwise checksum types that are not understood by Windows 2000
-will be generated (@xref{Quirks of Windows 2000 KDC}.).
+will be generated (@pxref{Quirks of Windows 2000 KDC}).
Another issue is salting. Since Windows 2000 does not seem to
understand Kerberos 4 salted hashes you might need to turn off anything
@@ -144,10 +148,11 @@
principals that are going to share keys with Windows 2000.
@example
- [kadmin]default_keys = v5 v4
+[kadmin]
+ default_keys = v5 v4
@end example
-You must also set:
+You must also set: @c fixme: what?
Once that is also done, you can add the required inter-realm keys:
@@ -158,9 +163,9 @@
Use the same passwords for both keys.
-Do not forget to reboot before trying the new realm-trust (after running
-@code{ksetup}). It looks like it might work, but packets are never sent to the
-non-Windows KDC.
+Do not forget to reboot before trying the new realm-trust (after
+running @command{ksetup}). It looks like it might work otherwise,
+but packets are never sent to the non-Windows KDC.
@node Create account mappings, Encryption types, Inter-Realm keys (trust) between Windows 2000 and a Heimdal KDC, Windows 2000 compatability
@comment node-name, next, precious, up
@@ -174,20 +179,23 @@
Click on the Kerberos Names tab and add a new principal from the
non-Windows domain.
+You can also use @command{ksetup} (@pxref{Configuring Windows 2000 to
+use a Heimdal KDC}), probably with the mapping @samp{* *}.
+
@node Encryption types, Authorization data, Create account mappings, Windows 2000 compatability
@comment node-name, next, previous, up
@section Encryption types
-Windows 2000 supports both the standard DES encryptions (des-cbc-crc and
-des-cbc-md5) and its own proprietary encryption that is based on MD4 and
-rc4 that is documented in and is supposed to be described in
+Windows 2000 supports both the standard DES encryptions (@samp{des-cbc-crc} and
+@samp{des-cbc-md5}) and its own proprietary encryption that is based on MD4 and
+RC4 that is documented in, and is supposed to be described in
@file{draft-brezak-win2k-krb-rc4-hmac-03.txt}. New users will get both
MD4 and DES keys. Users that are converted from a NT4 database, will
only have MD4 passwords and will need a password change to get a DES
key.
Heimdal implements both of these encryption types, but since DES is the
-standard and the hmac-code is somewhat newer, it is likely to work better.
+standard and the HMAC code is somewhat newer, DES is likely to work better.
@node Authorization data, Quirks of Windows 2000 KDC, Encryption types, Windows 2000 compatability
@comment node-name, next, previous, up
@@ -210,7 +218,7 @@
@item Run @kbd{ktutil add} to add the key for that principal to a
keytab.
@item Run @kbd{appl/test/nt_gss_server -p 2000 -s authsamp
---dump-auth=file} where file is an appropriate file.
+--dump-auth=@var{file}} where @var{file} is an appropriate file.
@item It should authenticate and dump for you the authorization data in
the file.
@item The tool @kbd{lib/asn1/asn1_print} is somewhat useful for
@@ -221,18 +229,17 @@
@comment node-name, next, previous, up
@section Quirks of Windows 2000 KDC
-There are some issues with salts and Windows 2000. Using an empty salt,
-which is the only one that Kerberos 4 supported and is therefore known
-as a Kerberos 4 compatible salt does not work, as far as we can tell
-from out experiments and users reports. Therefore, you have to make
+There are some issues with salts and Windows 2000. Using an empty salt---which is the only one that Kerberos 4 supported, and is therefore known
+as a Kerberos 4 compatible salt---does not work, as far as we can tell
+from out experiments and users' reports. Therefore, you have to make
sure you keep around keys with all the different types of salts that are
required.
Microsoft seems also to have forgotten to implement the checksum
algorithms @samp{rsa-md4-des} and @samp{rsa-md5-des}. This can make Name
-mapping (@pxref{Create account mappings}) fail if a @code{des-cbc-md5} key
-is used. To make the KDC return only @code{des-cbc-crc} you must delete
-the @code{des-cbc-md5} key from the kdc using the @code{kadmin
+mapping (@pxref{Create account mappings}) fail if a @samp{des-cbc-md5} key
+is used. To make the KDC return only @samp{des-cbc-crc} you must delete
+the @samp{des-cbc-md5} key from the kdc using the @kbd{kadmin
del_enctype} command.
@example
@@ -256,47 +263,49 @@
See also our paper presented at the 2001 usenix Annual Technical
Conference, available in the proceedings or at
-@url{http://www.usenix.org/publications/library/proceedings/usenix01/freenix01/westerlund.html}.
+@uref{http://www.usenix.org/publications/library/proceedings/usenix01/freenix01/westerlund.html}.
-There are lots of text about Kerberos on Microsoft's web site, here is a
+There are lots of texts about Kerberos on Microsoft's web site. Here is a
short list of the interesting documents that we have managed to find.
@itemize @bullet
-@item Step-by-Step Guide to Kerberos 5 (krb5 1.0) Interoperability -
-@url{http://www.microsoft.com/windows2000/library/planning/security/kerbsteps.asp}
-Kerberos GSS-API (in Windows-ize SSPI), Windows as a client in a
+@item Step-by-Step Guide to Kerberos 5 (krb5 1.0) Interoperability:
+@uref{http://www.microsoft.com/windows2000/techinfo/planning/security/kerbsteps.asp}.
+Kerberos GSS-API (in Windows-eze SSPI), Windows as a client in a
non-Windows KDC realm, adding unix clients to a Windows 2000 KDC, and
-adding cross-realm trust (@xref{Inter-Realm keys (trust) between Windows 2000
-and a Heimdal KDC}.).
+adding cross-realm trust (@pxref{Inter-Realm keys (trust) between Windows 2000
+and a Heimdal KDC}).
-@item Windows 2000 Kerberos Authentication -
-@url{http://www.microsoft.com/TechNet/win2000/win2ksrv/technote/kerberos.asp}
+@item Windows 2000 Kerberos Authentication:
+@uref{http://www.microsoft.com/windows2000/techinfo/howitworks/security/kerberos.asp}.
White paper that describes how Kerberos is used in Windows 2000.
-@item Overview of kerberos -
-@url{http://support.microsoft.com/support/kb/articles/Q248/7/58.ASP}
+@item Overview of Kerberos:
+@uref{http://support.microsoft.com/support/kb/articles/Q248/7/58.ASP}.
Links to useful other links.
-@item Klist for windows -
-@url{http://msdn.microsoft.com/library/periodic/period00/security0500.htm}
-Describes where to get a klist for Windows 2000.
-
-@item Event logging for kerberos -
-@url{http://support.microsoft.com/support/kb/articles/Q262/1/77.ASP}.
-Basicly it say that you can add a registry key
+@c fixme: no longer there
+@c @item Klist for windows:
+@c @uref{http://msdn.microsoft.com/library/periodic/period00/security0500.htm}.
+@c Describes where to get a @command{klist} for Windows 2000.
+
+@item Event logging for Kerberos:
+@uref{http://support.microsoft.com/support/kb/articles/Q262/1/77.ASP}.
+Basically it says that you can add a registry key
@code{HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Parameters\LogLevel}
-with value DWORD equal to 1, and then you'll get logging in the Event
+with value @samp{DWORD} equal to 1, and then you'll get logging in the Event
Logger.
-@item Access to the active directory through LDAP
-@url{http://msdn.microsoft.com/library/techart/kerberossamp.htm}
+@c fixme: no longer there
+@c @item Access to the active directory through LDAP:
+@c @uref{http://msdn.microsoft.com/library/techart/kerberossamp.htm}
@end itemize
Other useful programs include these:
@itemize @bullet
-@item pwdump2
-@url{http://www.webspan.net/~tas/pwdump2/}
+@item @command{pwdump2}
+@uref{http://www.bindview.com/Support/RAZOR/Utilities/Windows/pwdump2_readme.cfm}
@end itemize