Re: Assignment papers

[Richard Stallman <rms@gnu.org>]

    So would it be possible to put the Emacs assignment document up on the
    web somewhere so that I could download it once in a while and refer
    to it easily?

We have decided not to publish this list, but you're supposed to be
able to get an account on fencepost so you can look at the file.
Please write to accounts@gnu.org to get an account.  Below is more
info on how to do it.

Miles wrote:

    Maybe a more constrained interface would be more acceptable, for instance a
    form that queries for a name, and then returns the assignments for the given
    person

We could consider putting a mechanism on savannah so that certain
project leaders can access the file that way.  Someone would have to
write the code, and then we would have to security-audit it.
But it should be possible.


                           How Logins Now Work

Moving forward, all GNU and FSF machines accept only SSH user logins and
will accept only Protocol 2 SSH connections.  You will be able to connect
via SSHv2 with a standard SSHv2 key (generated by OpenSSH or LSH).

We also strongly urge everyone to begin using GNU Privacy Guard (GPG) for
at least signing email communications.  In particular, when communicating
with FSF (such as to restore your account, see below), it is helpful for
us to confirm your identity via GPG.


                          Reactivating Accounts

                      SSHv2 Public Key Reactivation

To reactivate your fencepost account using an SSHv2 public key, please
follow these procedures:

  * Generate a SSHv2 key if you do not already have one (you may want to
    consider generating a new one, particularly if your private key ever
    lived on fencepost).

    ** For OpenSSH, use the command "ssh-keygen -t type", where type can
       be either "dsa" or "rsa".

    ** For LSH, use the command "lsh-keygen | lsh-writekey"

  * Email to <accounts@gnu.org> your SSHv2 public key along with the
    "Needed Information" below.

    ** For OpenSSH, please attach either your ~/.ssh/id_dsa.pub or
       ~/.ssh/id_rsa.pub file.

    ** For LSH, please attach your ~/.lsh/identity.pub file.

  * Include all of the "Needed Information" below in your message.  We
    will contact you to confirm your SSHv2 fingerprint.  Please be ready
    to tell us the fingerprint of your public key.  You can get this by
    running "ssh-keygen -l -f ~/.ssh/id_dsa.pub" (or rsa.pub) for OpenSSH,
    and "sexp-conv --raw-hash < ~/.lsh/identity.pub" for LSH.

  * If possible, please use GnuPG to sign your email to
    <accounts@gnu.org>.  If we can determine that we sufficiently trust
    your GnuPG signature, we may end up not needing to contact you to
    confirm your SSHv2 public key fingerprint.


                            Needed Information

    1. Your primary uses of your fencepost account
       (e.g., "GNU Maintainer of GNU Foobar")
    2. fencepost account username
    3. An email address that does not deliver via FSF or GNU
    4. Phone numbers and time of day where we can contact you to
       confirm fingerprints.
    5. Postal mailing address
    6. SSHv2 *public* key from ~/.ssh/id_{dsa,rsa}.pub or
       ~/.lsh/identity.pub


                      New Fencepost SSH Public Server Keys

The fingerprint of fencepost's new SSH public server keys are:

  1024 20:28:96:d6:a4:bc:61:4c:b0:85:19:59:0c:97:2a:5b fencepost.gnu.org RSA
  1024 c7:ac:07:57:a3:1d:e0:8a:0f:53:33:0c:46:01:70:59 fencepost.gnu.org DSA

SSH should prompt you with one of these keys when you first try to log
into fencepost after restoration of your account.  Be sure to compare
what it shows you with the host fingerprints above before confirming the
host key.
 

                   Other Methods of Account Activation

If, for some reason, none of these methods of reactivation will work for
your situation, please contact us at <accounts@gnu.org> or +1-617-542-5942
(starting the morning of Monday 4 August 2003), and we will make special
arrangements.

Please note that we will not have much time this weekend to restore
accounts this weekend (Saturday 2 August 2003 and Sunday 3 August 2003).
We will try to do a few, but we will begin in earnest on Monday 4 August
2003 to process all account restoration requests from the weekend.