-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 21 Mar 2003 09:27:17 +0100 Vesselin Kolev <[EMAIL PROTECTED]> wrote:
> Blagodaria mnogo za informaciata. > > Interesnoto v sluchaia e, che programata PGP FreeWare ima interface > za keyserver, koito pak obshtuva s web interface-a na servera, no tam niama > tozi problem. Sega shte razgledam source code-a na PGP imenno v chastta > za tozi key browser. Edinstveniata nachin tozi PGP FreeWare da izbiagva > tozi bug e .. da izteglia kliuchovete pri sebe si, da opredelia pravilno > sherstnadesetichnoto im ID i fingerprint. GNUPG napravo obshtuva s > web interface-a na keyservera i zatova dava neprevilni otgovori. > > Interesnoto e, che problemyt otsystva pri LDAP bazirani interface-i na > keyserverite (makar, che sa ot syshtata versia kato tezi, koito se polzvat > za osnova na web interface-ite). Naprimer ldap://europe.keys.pgp.com. > > Mnogo blagodaria na Pavel za otgovora. Pone mi spesti pisnae do MIT. > > Pozdravi i blagodarnosti > > Vesselin Kolev > malko paste ot gnupg-users-list s oshte po temata On Tue, Mar 11, 2003 at 04:49:32AM +0100, Andy McDowell wrote: > I have subscribed here to find an answer to a pain-in-the-arse problem > to do with my 4096b RSA sign-only public key ID being modified when the > key is uploaded to the MIT PGP keyserver. > > I see this problem has already been discussed in the thread "Problem > with GnuPG 1.2.1 generated Key (Broken Key or Keyserver Problem)" - > OP'er Bjoern Buerger. > > David Shaw wrote back and said he had a patch prepared and it was > waiting for release. It was released a few weeks ago as part of pks 0.9.6. > So just a couple of questions to follow up. > > - -1- After the patch is applied will the RSA (public) key need to be > uploaded once again to the MIT PGP keyserver to correct the key id, or > will the key id be corrected automatically once the key applied? Automatically corrected. > - -2- Is there any timeline for when the patch will be applied to the > keyserver? You'll have to ask the pgp.mit.edu administrator. I do know they were testing the new keyserver version, but I don't know what their plans are. The pks software is changing fast, so they may be waiting for the next release. > - -3- Is there a preferred alternative keyserver for GPG generated keys, > where the key id's for RSA keys are not modified? There are a few keyservers that have upgraded, or who don't run pks so the bug never applied to them. Try: keyserver.bu.edu blackhole.pca.dfn.de pgp.cns.ualberta.ca keyserver.stinkfoot.org keyserver.kjsl.com You can also use the PGP.com LDAP server: ldap://keys.pgp.com David ima patch za problema ot David Shaw , koito e vleznal v pks 0.9.6 no kakto kazva toi mit.edu ne sa upgradnali po neznaini pri4ini hubavoto e che sled upgrade-a ID she se korigirat a drugoto interesno e 4e kogato keyserver-a list-va signatures na key-a , ne se razpoznava self-signature Type bits /keyID Date User ID pub 2048R/42B7AFF1 2003/02/01 Pavel <[EMAIL PROTECTED]> sig BCB0C3F4 (Unknown signator, can't be checked) :))) BCB0C3F4 e originalnoto ID pri razni keyanalyze na trust sigurno she ima problem :) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iQEVAwUBPnxZRMGmSji8sMP0AQLjLgf8CoByENjHJTfxUqDIO8RAk/Q9F/opebMn DFlMYljkWLvq9pD0m9qmeKfjehAaU19z6RF2tPaTntLH8yZEnj9aW5SPigXtfAnu PHGNxiD8eLQiPrFodVlLE+46XGtik0oRoWLakryLsfPBxZqChK+qf9VEsZEvecee tM/KMb87DH19HK3Hjys7p+Agcy7iDQVuaEZVfSyyuOR3vS0LodHMSy5BVUDRwVj9 3JEyIFZ/H7+NTeLVVHv9N0q+JGMaqJJMB/1OvLspaUDzzQx0rTXGXzXobYGTY1wU CwICfRy/L2Y2Ewm9B2rkFvxlgXlGQ4dY65SxCMhOvkzUCd5vThwITQ== =D5U2 -----END PGP SIGNATURE----- ============================================================================ A mail-list of Linux Users Group - Bulgaria (bulgarian linuxers). http://www.linux-bulgaria.org - Hosted by Internet Group Ltd. - Stara Zagora To unsubscribe: http://www.linux-bulgaria.org/public/mail_list.html ============================================================================
