RESCANNED 3:770/1   
   MSGID: 1:3634/12.0 8a601d0b   
   PID: PostIt v3.07br BK000000   
   TZUTC: -0500   
   CHRS: CP437 2   
   TID: FastEcho 1.46.1 7617   
   -----BEGIN PGP SIGNED MESSAGE-----   
      
      
    PUBLIC_KEYS Echo Guidelines:                             rev.  2 JUL 01   
    Posting Frequency: 1st and 15th of the month.   
    -----------------------------------------------------------------------   
      
    It is recommended that individual, public-keys be made available via   
    Netmail or by file-request with the magic filename: PGPKEY and that the   
    public-key provided for that request by given a distinctive filename   
    using part or all of each provider's name and address. For example, on   
    my system, a file-request of PGPKEY will give MFLKEY.ASC to the   
    requesting system. A magic filename of KEYRING will yield my working   
    Public Keyring as MFLPUB.PGP. INETRING will give you PUBKEYS.PGP which   
    is a ring i downloaded from one of the large public keyservers some   
    years back. This will avoid duplicate overwriting and make it easier   
    to track the keys. Using standard magic filenames will make it easier   
    to find keys and keyrings on different systems.   
       
    The PGP and Privacy and encryption related files on each system should   
    be maintained with a magic filename for file request. PGPFILES should be   
    set on all participating systems to allow your current related files to   
    be picked up at any time. It is suggested that the actual filename   
    indicate the origin of the list to avoid confusion and overwriting.   
    PGPFILES requested from this system =currently= returns no files.   
       
    This Echo should currently be available on all fidonet backbones. It   
    has been EListed since ELIST211. Please feel free to announce this Echo   
    in all Nets and Networks.   
       
    A companion Echo for the purpose of submitting public-keys only is now   
    available as PKEY_DROP Echo. PKEY_DROP may be obtained via the same   
    channels as PUBLIC_KEYS.   
       
    NOTE:   
       
    If you lose your secret-key password [or forget it] or your secret-key   
    in a drive crash [because you failed to back it up on floppy], you   
    cannot issue a revocation certificate. In that case, you should make a   
    general announcement in all related Echos that your old key should be   
    disabled using the PGP disable command [PGP -kd userid] for your userid.   
    That keeps your useless key on their keyrings [so they won't be replaced   
    from other lists who didn't get the word] and permits them to add a new   
    key from you without one interfering with the other. BACKUP! BACKUP!   
    BACKUP! [clear?] [grin]   
       
    Thanks.   
       
    Mark Lewis, 1:3634/12, wkitty42@alltel.net   
      
    Conference Moderators   
      
      
   -----BEGIN PGP SIGNATURE-----   
   Version: 2.6.2   
   Comment: Privacy is a right to fight for.   
      
   iQCVAwUBO0SvtJsj1FW2DCDFAQHMvAP+IaxDQVDuMmjxT9iSprBDeQicK7VwFisS   
   Aj2wa4GxjjJDk+sqQGYa9c2BTcMTLuwmWhOYaQ0HTXyd/Mm0/DeU9SFRk52vrQ10   
   Ii+0jOODRq+Cu+tZ8dGmeIGmeMpcMA3tY5tKaBJClB99+aA3+IXthGgwm4woj85q   
   Xd5+t7KPtqI=   
   =dfsV   
   -----END PGP SIGNATURE-----   
      
    * Origin: (1:3634/12)   
   SEEN-BY: 1/123 19/33 34/999 57/0 90/1 116/18 120/331 340 601 123/131   
   SEEN-BY: 123/500 128/2 187 135/364 140/1 153/250 757 218/700 220/70   
   SEEN-BY: 222/2 226/0 17 30 160 227/114 702 229/101 424 426 664 1014   
   SEEN-BY: 230/150 240/1120 5832 249/206 303 317 400 250/306 261/38   
   SEEN-BY: 261/100 266/185 1413 267/155 800 280/464 1027 282/1057 292/854   
   SEEN-BY: 292/907 908 310/31 311/2 317/3 320/119 322/757 762 340/400   
   SEEN-BY: 340/1000 342/200 393/68 396/45 633/260 712/848 770/0 1 100   
   SEEN-BY: 770/340 772/0 1 220 230 500 801/161 189 5030/1256   
   PATH: 3634/12 123/500 261/38 712/848 770/1 229/664 426