SEUL: New policy for website updates

[Roger R Dingledine <arma@mit.edu>]

Ok, so this automatic cvs update thing we've got working isn't, well,
working, and in fact has been breaking further as I do upgrades. And it's
tough to fix.
So I'm going to simplify everything a lot.

From now on, this is how you update the website:
1) Modify your file in cvs like you've been doing.
2) Do a cvs commit like you've been doing.
3) ssh seul@belegost
4) cd public_html, cvs update -d -P
5) make sure the permissions are correct on files you just updated
(you'll likely want to do a chmod a+r on them)

All of these steps should be self-explanatory except for step 3. This is
how you will do that:
3a) run ssh-keygen from your cran account. Hit enter when it asks you to
give it a passphrase (or give it a passphrase, if you know what you're
doing and like extra security).
3b) send me mail or otherwise tell me to copy your identity.pub over to
seul@belegost so it will work.
3c) then you just do an ssh seul@belegost from your cran account, and
you will magically be logged in.

Why do I have step 5 on there? Because the umask on seul@belegost is set
for the cvs updates such that it makes them x00 rather than xxx. If
somebody wants to fix this, by all means. :)

This means that I need to trust you guys to not screw up the public
website (and the archives also live in that account). But hey, if I can't
trust you, who can I trust?

Let me know if you have any questions.
(If you're on seul-commits and you're doing stuff, but you're not on
seul-pub-www, you should fix that (mail majordomo@seul.org with body of
'subscribe seul-pub-www'.))

Thanks,
--Roger