|
North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical Fwd: You have been removed from the list
I don't understand I am receiving your post fine? The bounce must be someones misstake! Fwd-2 ______________________________________ Subj: PGP authentication for the RADB Date: Thu, Sep 7, 1995 12:53 PM EDT From: [email protected] X-From: [email protected] (Brian Renaud) Sender: [email protected] Resent-from: [email protected] Reply-to: [email protected] To: [email protected] The RADB now supports authentication using PGP-based digital signatures. If you want to use this feature, there are three things you must do: * Register your public key with the RA. * Modify your maintainer object to reflect your use of digital signatures * Sign (via PGP) your RADB transactions. 1. Registering your public key with the RA. You must send your public key to the RA for inclusion onto our PGP keyring. Use the "pgp -kxa" command to generate a copy of your public key suitable for mailing, then mail the resultant file to [email protected] For example: % pgp -kxa [email protected] pubkey ... % mail -s 'please register my public key' [email protected] < pubkey.asc You may use one of two methods of verification: * Fax a copy of a photographic identification (passport or drivers license) to: RADB public key verification +1 313 747 3185 please write your PGP fingerprint and email address on the fax * Attend an RA sponsored key signing session at NANOG or IETF. You will need to bring a copy of your public key with a PGP fingerprint and photo identification. (This will be verification via the identification you bring, rather than having two other people agree that you are who you say you are.) We will be holding a key signing at NANOG on Monday, September 11 at 5:00. If that time is not convenient, you can also accost RA team members at random and present them with with the appropriate information. 2. Modifications to the maintainer object There is a new authentication option for the maintainer object. The syntax for it is: auth: PGP-FROM {PGP User Id} For example, auth: PGP-FROM John Smith <[email protected]> 3. Signing your RADB transactions You will need to PGP-sign each transaction you send to [email protected] Use the "pgp -sta" command to do this. For example: % pgp -sta -u [email protected] routes ... % mail -s 'route updates' [email protected] < routes.asc ----------------------- Headers -------------------------------- >From [email protected] Thu Sep 7 12:54:50 1995 Return-Path: [email protected] Received: from merit.edu (merit.edu [35.1.1.42]) by emin04.mail.aol.com (8.6.12/8.6.12) with ESMTP id MAA03037 for <[email protected]>; Thu, 7 Sep 1995 12:54:37 -0400 Received: (from [email protected]) by merit.edu (8.6.12/merit-2.0) id LAA03917; Thu, 7 Sep 1995 11:52:35 -0400 Resent-Date: Thu, 7 Sep 1995 11:52:35 -0400 Message-Id: <[email protected]> From: Brian Renaud <[email protected]> To: [email protected] Subject: PGP authentication for the RADB Reply-To: [email protected] Date: Thu, 07 Sep 1995 11:52:31 -0400 Sender: [email protected] Resent-Message-ID: <"obcC1.0.5z.2LnJm"@merit.edu> Resent-From: [email protected] X-Mailing-List: <[email protected]> archive/latest/24 X-Loop: [email protected] Precedence: list Resent-Sender: [email protected] --------------------- Forwarded message: From: [email protected] To: [email protected] Date: 95-09-07 12:38:12 EDT Your mail address [email protected] has been removed from the [email protected] mailinglist. It generated an excessive amount of bounced mails. Before sending in a subscription request to [email protected] again, please ensure that this problem has been resolved. When in doubt, ask your system administrator or send mail to "postmaster". The last one of those bounced mails has been quoted below: >From MAILER-DAEMON Thu Sep 7 12:10:01 1995 >Received: from localhost (localhost) by merit.edu (8.6.12/merit-2.0) with internal id MAA03450; Thu, 7 Sep 1995 12:10:01 -0400 >Date: Thu, 7 Sep 1995 12:10:01 -0400 >From: Mail Delivery Subsystem <MAILER-DAEMON> >Subject: Returned mail: User unknown >Message-Id: <[email protected]> >To: [email protected] > >The original message was received at Thu, 7 Sep 1995 11:42:00 -0400 >from [email protected] > > ----- The following addresses had delivery problems ----- >[email protected] (unrecoverable error) > > ----- Transcript of session follows ----- >[email protected] Deferred: Connection timed out during initial connection with nwnexus.wa.com. >... while talking to zippy.cais.net.: >>>> RCPT To:<[email protected]> ><<< 550 <[email protected]>... User unknown >550 [email protected] User unknown >[email protected] Deferred: Connection timed out during initial connection with gxl.woodtech.com. >451 [email protected],[email protected] reply: read error from exodus.databank.com. >451 [email protected],[email protected] timeout waiting for input during client greeting >451 [email protected],[email protected] reply: read error from umx-hub.novell.com. >[email protected],[email protected] Deferred: Connection timed out during initial connection with ums-hub.novell.com. >451 [email protected] reply: read error from mail05.mail.aol.com. >[email protected] Deferred: Connection reset by peer during client greeting with mail05.mail.aol.com. > > ----- Message header follows ----- >Return-Path: [email protected] >Received: (from [email protected]) by merit.edu (8.6.12/merit-2.0) id LAA03439; Thu, 7 Sep 1995 11:42:00 -0400 >Resent-Date: Thu, 7 Sep 1995 11:42:00 -0400 >Date: Thu, 7 Sep 95 11:35:17 -0400 >From: [email protected] (James Cassell) >Message-Id: <[email protected]> >X-Mailer: Ez-Mail v4.4 <Date: Thu, 07 Sep 95 11:41:31 nrm1838> >To: [email protected] >Subject: Re: Pittsburgh directions >Old-Status: N >Resent-Message-ID: <"Rj0Gu.0.hr.7BnJm"@merit.edu> >Resent-From: [email protected] >X-Mailing-List: <[email protected]> archive/latest/23 >X-Loop: [email protected] >Precedence: list >Resent-Sender: [email protected] > > ----- Message body suppressed ----- >
|