X-Git-Url: https://sipb.mit.edu/gitweb.cgi/wiki.git/blobdiff_plain/b77165053caeeae1ac8b47eec6dff8cf5bbb1bab..a8e1835c8fad770505eb24715fa15aa543656286:/doc/zcrypt.mdwn

diff --git a/doc/zcrypt.mdwn b/doc/zcrypt.mdwn
index cb27e71..4b744e4 100644
--- a/doc/zcrypt.mdwn
+++ b/doc/zcrypt.mdwn
@@ -17,7 +17,7 @@ The last line creates the key, which should be a random byte string of at least
 
 ## Subbing to a `zcrypt`ed zephyr class
 
-This may vary between clients. For traditional zephyr clients, you should sub as usual (in Barnowl, run `:sub classname`).
+This may vary between clients. For traditional zephyr clients, you should sub as usual (in BarnOwl, run `:sub classname`, or edit your `.zephyr.subs` file, then run `:loadsubs` in BarnOwl).
 
 You should also have been told a key path. In the example above, that would be `/mit/user/Public/zcrypt/label/key.zcrypt` (where `user` is your Athena username).
 
@@ -27,4 +27,4 @@ You can configure the key by running
 
 Replace `classname` and the path appropriately. (You can also leave off "AES:" to use the key with 1DES, but that is very weak, and should not be used in new classes.)
 
-<small>* This is only mostly true. Zephyr supports limiting who can sub to zephyr classes, and Moira has support to control zephyr's support. However, there's no self-service support for setting up ACL'd classes, and I don't believe anybody with the relevant bits in interested in setting up classes for student groups or similar uses, so the technical ability isn't practically useful.</small>
+<small>* This is only mostly true. Zephyr supports limiting who can sub to zephyr classes, and Moira has support to control zephyr's support. However, there's no self-service support for setting up ACL'd classes, and I don't believe anybody with the relevant bits is interested in setting up classes for student groups or similar uses, so the technical ability isn't practically useful.</small>