Message Area
Casually read the BBS message area using an easy to use interface. Messages are categorized exactly like they are on the BBS. You may post new messages or reply to existing messages! You are not logged in. Login here for full access privileges. |
Previous Message | Back to Public-Key Discussion Echo <-- <--- | Return to Home Page |
|
||||||
From | To | Subject | Date/Time | |||
Moderator | All | PUBLIC_KEYS Echo Suggestions |
September 1, 2018 12:00 AM * |
|||
-----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) |
||||||
|
Previous Message | Back to Public-Key Discussion Echo <-- <--- | Return to Home Page |
Execution Time: 0.0814 seconds If you experience any problems with this website or need help, contact the webmaster. VADV-PHP Copyright © 2002-2024 Steve Winn, Aspect Technologies. All Rights Reserved. Virtual Advanced Copyright © 1995-1997 Roland De Graaf. |