Convert most http: links to https:

[wiki.git] / doc / kerberized-server.mdwn

diff --git a/doc/kerberized-server.mdwn b/doc/kerberized-server.mdwn
index a87d552e6e33e3a94c2521a669fc6ac3588864ad..47a338770541dfc0e35eec955183dcae323cb43f 100644 (file)
--- a/doc/kerberized-server.mdwn
+++ b/doc/kerberized-server.mdwn
@@ -2,7 +2,7 @@
 
 If you want kerberized logins on a server you run, you'll need a
 *keytab* from accounts.  Fill out the
-[keytab request form](http://web.mit.edu/accounts/www/srvtabform.html),
+[keytab request form](https://ist.mit.edu/accounts/keytab),
 which sends them an e-mail.
 
 Your new keytab will be in
@@ -41,7 +41,7 @@ later add get this file by default.)
 
 ## Upgrading cryptographic strength
 
-You may wish to change the encryption algorithms (*enctypes*) included in your keytab. With server principals (like `daemon/servername.mit.edu` or `host/servername.mit.edu`) it is particularly important to support *only* strong algorithms. If you support a weak algorithm, an attacker can request a service ticket encrypted with that key, allowing them to do an offline attack and potentially extract your secret key.
+You may wish to change the encryption algorithms (*enctypes*) included in your keytab. With server principals (like `daemon/servername.mit.edu` or `host/servername.mit.edu`) it is particularly important to support *only* strong algorithms. If you support a weak algorithm, an attacker can request an initial ticket encrypted with that key, allowing them to do an offline attack and potentially extract the secret key.
 
 To change the supported enctypes, run `kadmin`: