Re: [Sks-devel] Keyservers and GDPR
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, 2019-05-27 at 14:28 +0100, Andrew Gallagher wrote: > On 27/05/2019 12:47, deloptes wrote: > > it is a matter of an agreement between the person and the authority > > hosting the information of the public key > > This is the problem though: there is no single identifiable authority > (data controller in GDPR jargon) with whom to make such an agreement. > Keyservers are distributed not just operationally and geographically, > but also legally. Furthermore, it is not always the data owner who > uploads it to the keyserver network, so neither party to the GDPR > consent model need be present during the transaction, or need even exist. Is that a binding legal opinion or a personal one? I ask, because in the USA (and presumably most western countries) there need not be a single identifiable entity necessary to bring suit. Doe subpoenas and multi-party lawsuits are real things. - -Jim P. -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEECPbAhaBWEfiXj/kxdRlcPb헹ᐔॳ꾩ꀀ⠤䇔数 fkX8ORAAmWG9BMllnQdBCaxZ7rbauKtcnM2WAuIZwyQCF0y1IfPMIuO4IjcfFBZj B/dvzDNdXZho/7ugDTSA7Ilل殫ᮼ펾쮪⿋䀩䨷�➿元뜿䕯 d/PJz두걢㠱뇞뀹꜄粈ᰴ䀪㎗䉝쿋�빤ᓘ뷲̆抆楹츁 TzcchQ6ZMYyoDxrSP6TCdN瀑䍮壾慵�䊖媓울⽆习⻎컲◪衴蕩 1YcFrgmJ0h8CD5dGoJAfxkWVyyLSDrAfKhkRhWGKIUKP7tCqQWgA4x9ojB濱 kGtXqeCtMNiA㟏籞㑈㖰瑻ぞ嚕⮯땑먣᪘떰䐒끕ꅐ BKtb/JFszauaMumDuMSMn33Tp8HIQmjxCG91bsIw1sl1TAEYjIMjRwRPHy9fwTys 67S7L1tzGsyL68YN1EZ9tEbUZgDtmji7NsHb5HLaei4E9Kn3k6j9FOilze1w/8D3 w4ioVbwl/EHlDCN4LYm8faVT3negT0nAqC4Tw3MlP6R5Wtu㸃⥺⣳辬 6YESgVmXf8B88KGF72BHcsIwZLmjyᜳ㤜믆磖ﰭ䘨ᵚ鶼⦝ᘧ푘 AdKYb2PpsVumbsdkdSP224vYAK2p/Qw0qcJGt6hTSqxuiJUsIJE= =xrBX -END PGP SIGNATURE- ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] DNS broken for hkps.pool.sks-keyservers.net
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Mon, 2019-03-18 at 11:42 -0400, Jim Popovitch wrote: > On Mon, 2019-03-18 at 08:27 -0700, Sparr wrote: > > hkps.pool.sks-keyservers.net does not seem to resolve currently, > > from public or local or whois-authoritative nameservers. > > There's also been quite a few DNSSEC validation errors for RSIGs, for some > time now. Sorry, wrong error for that domain. sks-keyservers.net has EDNS0 issues not RSIG errors. (DNS Flag Day was last month) https://ednscomp.isc.org/ednscomp/57d26bc180 - -Jim P. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEECPbAhaBWEfiXj/kxdRlcPb+1fkUFAlyPvVsACgkQdRlcPb+1 fkXdnw//Xga1uS9YPH/3OoavB26YgQ5vaPHoPNBPggSWK++F9idoSK11+NF5Hg1S s2rW00zuoQyIIMbJ5Zel582i1ZgP+arfNDMmY7wlhgFf+XIcMIaLsuzZ6SohTbdm H6P+97KMvLeIaSD6YyWFg+kZV6e/U9HGMUQewECKGKbpvfgu/6jMRKmuSiSq1mQ4 7zUBgCUop8l+bk6kYFim93+Jx764Y+JJtdDJeqJtfiJv2LYYIvJ++PJq7uC6HPIy FnGxAdoRtZ0ZK1mSwlAkuz2f4mOxIhlW0MJaW5S1X30gFDrIpeMFeTYM1RSn+wbf MEelNPgunjzI2kosrJ5OeYbgI0eTMOKyvymZt0CIfPDSWnGYlCUirI3kQaFpNJy8 6bCo5dYBj5x6iK1Rx5nzZC4fa0jECONc0XrgNbaIPT6xEd+/dGdzBTMCzeml+LOX +3Ils4w6Qn6UJPPB925iRd+slxZcMnSUAFSsNMa9fH4u/4XPJtOq/ju4fAhSnUzL iqaP61WNYb20gtm+CgSd6xka+Eq5ltUkoQY6Ut5IziRItg7SQ7WQruzfW5BL3d+Y KgcsC1J7KiukaxtmjD6lOZbiLTH7AqVj4RUKJ+5hFMSIkjq+wy2i738wn/ShMkg3 26b5qyQEQ4yy6Eeq93KFJj/vn0kv8IIJd9Xm9FRCYc+bmQ8M6Lk= =cFT6 -END PGP SIGNATURE- ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] DNS broken for hkps.pool.sks-keyservers.net
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Mon, 2019-03-18 at 08:27 -0700, Sparr wrote: > hkps.pool.sks-keyservers.net does not seem to resolve currently, > from public or local or whois-authoritative nameservers. There's also been quite a few DNSSEC validation errors for RSIGs, for some time now. http://dnsviz.net/d/sks-keyservers.net/dnssec/ The outage is also mentioned here: https://lists.gnupg.org/pipermail/gnupg-users/2019-March/061771.html - -Jim P. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEECPbAhaBWEfiXj/kxdRlcPb+1fkUFAlyPvF0ACgkQdRlcPb+1 fkVFTQ//dgHWZIw4fekFhSCMAFLTkqsy7hdlr1Su4dUJmxFZmwzhs6ZMS4DhvX90 hY9VC2iFwks8SzJGvsr62an89JaybuVbMzlpGLoQ02TctjoiSUdvuDwCCPCJsE21 OZIl9jEIJIeG7xkPk64wqxTm/wM94tUyeI3NNiDfmVBaDnfZNRnpzveFEZ14IF7L DCUBrr4J5RQtmzEsD4vVLfPFLk1uXLUOK3/35xtfcbHjV9vFQHVh4ClZ1Ui5FrlF TWpVjP6eM7WFFlA1zF3fkQ/0p5jE1KYKW8vqfmZx2MXC6/hTjHyhetYpk64tfX/v d4ZNrT615K/GGdl1BbNWHFkQSjqGvKfIi3Sd0S3LYp/vp0CwWZ4V62kGfB+Vkw5g AfVEk3cUupid7/qyKcKeY/J0s1ZAEUurSCoqakcn1Q2RVgGVeuO5h8WnozpLAxwl GS6+Q0ll7I4PBELp4NSYywF1NtqZvYUXGDEacdbWEpA0VfZsGaKMOyrKE7VvTXzz XgW7cwlVjE7COS2nVKOXmew44Suas0vkXrk2GYwfVTXxlQAPV3inYRz91UxRiqBa 0byUv7bNBK1lkU092ZWnQmuc4JBh+dD8ABMdBWaNGPgIknyOo34uEX6V1YUPYHtm VLIW8cgh+D364mcwp7PL7hfpixPlDRXjgyqQlkFPzD/UC5ahSXk= =EeDV -END PGP SIGNATURE- ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] SKS Performance oddity
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Sat, 2019-03-09 at 00:22 -0500, Jeremy T. Bouse wrote: > I've been fighting with this for a several days now... Anyone else > out there seeing this behavior or if not and have similar resourced > servers care to share details to see if I'm missing something here. > > The particulars are that all nodes are Debian 9.8 (Stretch) 64-bit. I'm running a near identical setup of SKS (but single instance) and I too am seeing the same behaviour. A fresh import from Matt's daily data yields a nice experience. Once the service is active and online the data quickly (within hours) slowly becomes corrupted with bogus invalid unsanitized uid data (which is putting it nicely, it's not really uid data) - -Jim P. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEECPbAhaBWEfiXj/kxdRlcPb+1fkUFAlyD0WoACgkQdRlcPb+1 fkXYkxAAq/prjHxKLqcx+xz9T3181ZvBcO9vGJ+y2ex1miy5XfevIPyxGv5pQn5j zSPjVFgnNTsT82l1qxKOsloVhIK0DQ+Zuv/X7VOv4M/iLRhBRsjZGqcgWEZH+LR2 pbCUUY4yFg8vn0mFo+UVtG7dBsWdoE31+G9y+X1ezlSYkOcUtGqiuEwPc/6EHiGK LO6TFo1rdx8/7J3nvcGRwGi7UnRyLdJ3QJUC27wLyeE/uRsjmoG1op6jTFNo2Ebx 1yzkPQjfR7mTg3WKx/p9pMV+nEMDf3akHTPPP9OxROkOm2O5xXnjvhgw9jHnlwR8 vh8wnWwk5DTpIIgUiVYF2h/V7ELJwSG1m1AhwpbFHbrd69rLWeEdFfve8s6XkeKc IYTbC0BFqX3nZrv4YaFy5BtZ6blfrN4fhYCdav4YHM4PVImgRxN301E8Nij9CSVj eLlyFeAahFtdni2xjJ3IYoWfNcf9MJ1iOWinG63l8fxvrW6u6rCjB5daPyHg4it6 4wgDpqKj8byiqhYiYyggo36NQxfmMP3JFsWx+M8iqH9sG9lFlXx4mLrpX7Rgc+AW kNS3lQSODn+vbNLOOyx6ABgSuOWtFmYCo59BQM1qLwmP3L29hYDWwU1yQQj5rqBF +J5nFJl1APKKTmyrwiSxKS020GE2RHQ2giSn2oPUYaUI3N+pr3w= =expD -END PGP SIGNATURE- ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] Data protection concern[Ref. RFA0751305]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Fri, 2019-03-08 at 15:15 +0100, Kristian Fiskerstrand wrote: > > and no further action will be taken from them. ..at this time. IANAL, but you should really talk to a lawyer to make sure that you (and your assets) are fully protected from future ICO or private action by claimant. Never, ever, ever put faith in the words of a lawyer of judicial agency that you haven't personally paid for advice. The system sucks, but that's how it works. - -Jim P. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEECPbAhaBWEfiXj/kxdRlcPb+1fkUFAlyCma8ACgkQdRlcPb+1 fkUw4g//dg9vDItd3TY54yQd1Ghu6ePwlBd803AWvSqXAxjmxVcAT/Tas8D0KHen CM0PoZrPgF7w1GOPoMEULrdw4RZF+ZzssEH/CTetomqDB7yNVXhzz2LIVQ5Jkv1w 3Q5h+1PDhYHd3MFoonkFe4lC/5h+KedZCc6oWNk3wFpgWvxTLH56ehnWbAuid7F/ FYNSgDOxFGY3qCOJ3dPXqYPJg9u2SiNPo1Ner+2nnsSV5n+y+k43SzolMEktZavi uEAnbWy1vjod2jUQUaN7ykKFWNuvQxhtN8ZG1d5rQzRav+0ufA/6V7ZVZ09V7Sjd x7z+abrfhAkmE7tdE6IksDRkOqtSAXTMKp9DanKUc0060+01ObWyJLRVjKFL0iWR 6svQrfk9IAk3OUYzOmwMCGccyLXL44bLwAf+34QulZO+d8xdU5zNSvMmf8vtQkK4 tRGsvEqmH4r0sFpJW4yoGc6UsTuRkvuuP9ud/lkxAnn5d2k/6p8UAHtKM3Sz8cLM guUNN64OmBuc6+YivrRI76DhfbHhubOyRVBWKj3nNtCG2RP8B4yEFqpc3cJbwmwT Hl5GxFeAKyWEL5LxhvhJv/EtE8FjyY4qf1CA0uR+konJZF7xNzUZTeXwPh/j2P8O 1A5YtoKIdRLy3944mc+xaSE4KLRZ+IRntaNlgyCtNHFYr/h4/ZY= =f4Pl -END PGP SIGNATURE- ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] Debugging a corrupted key
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Wed, 2019-03-06 at 22:33 -0800, Todd Fleisher wrote: > If I understand your statement, if you are trying to remove bad data from a > key that’s already in the network that is not possible. Once it’s in the > network you can only append new attributes to the key, you cannot remove > existing data from it. It’s basically a one-way street. > I understand the bad data from a key issue, but I believe this is different than that historical discussion. What I'm seeing is bogus key data, that serves no key purpose, and corrupts the sks output. If the bogus key data can't be removed, than at a minimum sks shouldn't choke on it. - -Jim P. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEECPbAhaBWEfiXj/kxdRlcPb+1fkUFAlyBEkgACgkQdRlcPb+1 fkXw8A//ewp8wvDAGcUqY2s0CNRPJkX+H+2rVISrfmMcRtSn4oIGL1ojuFbPEt8X S4lcRT36cvhRTWqAH6p2LKcEEnkyJ2lc4VGY36u4+qXrY+E8ovU/MF5kAOVbBKM5 PHFwQXCdk+cM9enfkwN7Ws0dxqHbtXn6AZKoRp9pzKmE4rI6ROjz6gKPfYvvuDwa 14YVEfQyVfO+dtY3Yr0/YfSxiEy6qxUHwruF1f6EXk2t4W1iTMzG+3QHgjTHoeSS T8PvbcBhHCzYY5qrJYIUzr32i2nM0VpNAalJrHTNTW9G5SbgLSdVPaQbyKH01AhG M98qzYAxcoRpbqFDYfim+KPNa9zo9ftcaYELKSQ0ItxT80YcYX3c1Afx91KY+6Go TzEK3Eth9YAG+cphP56pMdRQMNXZMV97rjLA1XqvArH0EfglwySp4XQkkPxDfX63 oVRf22c0QDsOZfhjkSkoX6qfhXWwzqgG+XNRTwbiPL0z6ADK2bOvWTEAnVvs4HJO Zx50OF0t+l9ido/1+h7LPovts7gfogn4ORQoDUrmuQRcZlAe0lE7Xfn1vH1Mv05g iqQJt7Njz50vyr15pJVK+/Y/692T0lxjv5u4DYaE1LlSwXi2LNK+YTNZYlkOJ/7g K63Bd+9JOFRPMg0li9GphyG5FcuX63R4HWjXE8fMW/AgENpAjBs= =ASn0 -END PGP SIGNATURE- ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] Debugging a corrupted key
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Wed, 2019-03-06 at 16:29 -0500, Jeremy T. Bouse wrote: > On 3/6/2019 12:01 PM, Jim Popovitch wrote: > > On Wed, 2019-03-06 at 11:44 -0400, Jason Harris wrote: > > > On Wed, Mar 06, 2019 at 09:57:58AM -0500, Jim Popovitch wrote: > > > > Hello! > > > > > > > > What are some investigative techniques to determine how my GPG key was > > > > corrupted. > > > > > > > > gpg --keyserver pool.sks-keyservers.net --recv-key > > > > 0x3F1C1EF2E6019EAC646CE45227155EB4C45A2705 > > > > gpg: packet(13) too large > > > > gpg: read_block: read error: Invalid packet > > > > gpg: no valid OpenPGP data found. > > > > gpg: Total number processed: 0 > > > Look at all the bad userids that need to be filtered out: > > > > > > > http://keyserver.timlukas.de:11371/pks/lookup?op=index=0x3F1C1EF2E6019EAC646CE45227155EB4C45A2705 > > > > > Get and save the key for analysis: > > > > > > > http://keyserver.timlukas.de:11371/pks/lookup?op=get=0x3F1C1EF2E6019EAC646CE45227155EB4C45A2705 > > > > > Then: > > > %pgpdump lookup | less > > > > > > OK, now what. :-) > > > > Ideally what I'm looking for is where did that bad key come from, what > > was the > > source of entry into the pool? > > > > -Jim P. > > > > I've also been taking a look and it appears to have occurred on more > keys at least from what I can find... I've even found a uid on > Kristian's 0x16e0cf8d6b0b9508 key that appears to have been corrupted as > well but I didn't see it on the > 0x94CBAFDD30345109561835AA0B7F8B60E3EDFAE3 key listed for > server_contact. Quickest way to see it is when doing a keyserver search > is with a vindex op call. I'm not sure if simply re-uploading a clean > copy of the key will fix it or if it's essentially a key that's > permanently corrupted in the network. FWIW, I tried, and was unable, to drop and re-upload a clean copy of my key. The drop logged as if the key was removed, but a search found the corrupted key remained. I rebuild the DB and my key is presently clean, but I do find others (ad...@pgp.pm is one of them) - -Jim P. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEECPbAhaBWEfiXj/kxdRlcPb+1fkUFAlyAPqwACgkQdRlcPb+1 fkXx2RAAihqT0BA5BVG7v/oD2xiQWPBtg5P8DQwqiJvrtdeCV7YZivezYNjM69Jx EtRwwD9wayZVCAYum45B9K7dbO5c1LKeXAcKkgLz/VZrgEClIwhwwPL+Dn4K6/Ns +xigZVykN4ofGCNpbA+AiYp5epe4sr5qVOl9YZ+t0yy5NjmcAGTTCPDu49toehPv XN3jgHszz8wyfg8skLl8mluHL4aiaKjXuVUhU2cGiblwrJCBqLeBzl2xke3kyIr+ Cj5jyKdqbNk9ClSaOLVuU86HOzoxbed5k7SFIIGMFDGCCMk+GHfX6aE8U6OfGD/T GT8icafAPWJufbMcgSmuglXwbaeq+qI2lHZuBlZuNdFuDxtTTKE+tKK38Ax5xAm0 Z7LIMS9MczxswNFizuEkY7gf5cv4Wr+gp/NyeHs1kDEiw8gfbhdSVeukrbjuCzrr 9UTFUghlBrcr0gcQGodF9PEsUsHmW7NPpxN7LXkUWbH4wFnpRaEnHuo3g3kNouS2 i0W3l7mYq/VJSn0ZFIQQf4ONzm6+sgIb9FR0f7R6W38nQtvTBj4NE5znStzi9N+C MUT5vmt3O0PtbQw8utRh3cUftjVfDtEF7m3EnsrBHeb3H9zWKwhYBdggW/8f6AyI TO5mAbNp7s8tRMyPGgYd+9jiZ9O/QEEVKtEDv1iyWa7SSoGbVmk= =i3kN -END PGP SIGNATURE- ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] Debugging a corrupted key
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Wed, 2019-03-06 at 11:44 -0400, Jason Harris wrote: > On Wed, Mar 06, 2019 at 09:57:58AM -0500, Jim Popovitch wrote: > > Hello! > > > > What are some investigative techniques to determine how my GPG key was > > corrupted. > > > > gpg --keyserver pool.sks-keyservers.net --recv-key > > 0x3F1C1EF2E6019EAC646CE45227155EB4C45A2705 > > gpg: packet(13) too large > > gpg: read_block: read error: Invalid packet > > gpg: no valid OpenPGP data found. > > gpg: Total number processed: 0 > > Look at all the bad userids that need to be filtered out: > > > http://keyserver.timlukas.de:11371/pks/lookup?op=index=0x3F1C1EF2E6019EAC646CE45227155EB4C45A2705 > > Get and save the key for analysis: > > > http://keyserver.timlukas.de:11371/pks/lookup?op=get=0x3F1C1EF2E6019EAC646CE45227155EB4C45A2705 > > Then: > > %pgpdump lookup | less OK, now what. :-) Ideally what I'm looking for is where did that bad key come from, what was the source of entry into the pool? - -Jim P. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEECPbAhaBWEfiXj/kxdRlcPb+1fkUFAlx//OYACgkQdRlcPb+1 fkUMjw//ceuXz9Tx2wF78qmOJlJ6+t21seoknevi52Hnn/ePugq/za+PrZfUjmts XrTDgEZDUdfeQN9Wf6Bg2Ew6FmA3GWVNDYl0xrLvVZDYaRA9BiRopi+UvEpSCw32 y/eOFuj5hquwt2g4QtSqEVvG0fVwLQi9BwieL1FWnoy8XIQY8aQd5HX/bqVv4VEZ qai2zydRoFn3lWFhhU3IX7TWv2X8emTN9t6Hj1tagHyGNBhiPu69bvQRm/KbQB9z +pfxVT62+WOxdys8ZCWdD68ROCzDe+HUIRGYmzLTso0LNmNhYbuzkFmbF7TCVYux oH3ob96bIFjyPZzjEaRCQEleZpbyzFNt7IfdYsnPge27/KaZ3UEmODfV6Elb0ZW6 yUzw1418ZacyINuIlxtPuhgs0m1eDxMdIUkLp2gk4IRs3qzs2OEmR+6HsBusSO4I L6f+5viWoL0EETATlR9OoQct1zdiVw2zYT0mNGxashGuR5ZVdKrjZsRU+XfAb3r1 qcQd5J6mMHwVeRyuqJ0Zhnte/lYxCjqI/vLct3YgbyACOw4UfXHW0DPj6sAfIymj E0271b30KbStwuuRbhfw7FkZhozR2qlunV4mnv2Ua6fHVyNlCgALZxG8fbPTVT6a M7JZJQBFBg6Lh5zEs7aHxSoU2X4dhBW6sH95Blkgs0r40IXqnZ8= =syu2 -END PGP SIGNATURE- ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
Re: [Sks-devel] seeking peers for sks.teknoloji360.com
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Wed, 2019-03-06 at 17:49 +0300, fuat wrote: > Hi, > > I am looking for peers for a new SKS keyserver installation. > > I am running SKS version 1.1.6, on sks.teknoloji360.com. > The server is physically located in Turkey (TR). > The machine has not IPv6 connectivity. Only IPv4. > > I have loaded > https://keyserver.mattrude.com/dump/current/sks-dump-*.pgp files. > I see 65733 keys loaded. > > For operational issues, please contact me directly. > > sks.teknoloji360.com11370 # Fuat Bölük < > f...@teknoloji360.com>0x03E48A51 > > Thank you, > Fuat Bölük My advice to you, as another new keyserver operator, is to judiciously validate and verify who you are willing to peer with and accept key data from (because you will be re-transmitting the key data they send you). - -Jim P. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEECPbAhaBWEfiXj/kxdRlcPb+1fkUFAlx/4ukACgkQdRlcPb+1 fkUn9RAAhU3k4w8p0IiUegcdxKtkUd5IlkT6UIQqNlW2AeUOfOAhLYg4NdcsllN4 SU4/Xc8vUBExJohgdJiW6ghNIBNQeVFciUzcTHAD9F4HQMmaXfovuRsERedWa4RK KN7797RzkiWM8LCpxycWaPJp8zF4kI28WSxeICq8E44QiW3x7OmKtuDcGJmzBiql 4CLy0+S+ysWtUUghZrlgX24g2sryNs6o3ps0WOeFn8QWmFLhB57HU0OLAji3UyOF Jtq1vXR1+iL4+pFR1qmm18RFXnp/8rYRDOQno4zNN8thKVdkOhRhuABUg2OkCdSq +DLAh/Vc3Wl66NUXPdwFlJc7uvtWsh9aLCl9o5Ha9ZBknd4fdy6UEDf7Xv2a2Kcn RwRebeUA3uGammOGZJsThC8bqdvopy44Cg1q2lPZjyzFLdiPgm+QPutKh+5M/vMF wb9NX8b/Slni4p5I4pNHlAaVGkrCavPY3SHMnr9ADYA6HPCNJ6vuEJeJEHjmVe4O b+qcRjsV5jfxxA5j2PWXZYdK+pxmRsk4rJg2fSlCU/zOnphi9jICbV96BUh4y0FJ oexgSIRMjVn/GkeWxzsiMR1DdScGqlIPaQRC4jPwXbwrg1gXOewdXHIM/cJPvatZ MH3a7f3NkmUiiXPiSYpqt59Z0jxSEMKlq9B86nPTaBqebtyFpgM= =p6jG -END PGP SIGNATURE- ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
[Sks-devel] Debugging a corrupted key
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello! What are some investigative techniques to determine how my GPG key was corrupted. gpg --keyserver pool.sks-keyservers.net --recv-key 0x3F1C1EF2E6019EAC646CE45227155EB4C45A2705 gpg: packet(13) too large gpg: read_block: read error: Invalid packet gpg: no valid OpenPGP data found. gpg: Total number processed: 0 tia, - -Jim P. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEECPbAhaBWEfiXj/kxdRlcPb+1fkUFAlx/3/YACgkQdRlcPb+1 fkXQJxAAtCw2RhLou6SW5FGBn2CmTTiuHkV0+kXS5122Zs6nZBMfTXHP7O5m+nGD GjolSfBLeBZzGOPbyS+jEqIGucULY/K2EvThgafh0oNDOXbCIWQr7cxsMIQuLDyf J42wvi4Hgtqq6EEQSlcGhJ9uxmNGjFmccmeXXQ9liEGAN89h3pVdXwImnUW2zWkP 6sfjECfrA5+iZxJmUgfMbfvrAEuKQPPw4yzAmLrd4vkinUWipwFZzmQ3kwpNzAtd CXO4bggNs4GLeFzV9Fy/QkzsFMS3hZa/iOHNQ0FcHYzDUye8n8/62cFLGCI5eyV3 aSGew3c+IavVgXs57Z4uGaAgSL1OIQ6uV3ZKBZhG73EwikL3L1mdZoUvziC2fB1+ Csm72n2FndHBSeUQDP0IzPQh1XXWhMewoWvj6sorLbtQNEPhauJK14BXfHaycbgc 0aa1SZA0N70KB/2VLowYWuN+bfM4cvcX3qTZBYXGhAIdpwv5EQUoBibM6hE3/Hnj gyNk7yF3x5ts9NcYH/zqeiiJTxnRxtOsU+kVVfo4kTNnBP4tfDIY3/vEIG23p9IX P57ehAtl6Newg2w3Lm3rXkZ+oqTeg+QTBtsrARhGx8WT9YA5ULsOQrDkNbcohVfT 4Vt2Tr0La3G0319/sA6GV86bGtSloZUDOP2UyCCyX/i14S1LjB0= =nNNM -END PGP SIGNATURE- ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
[Sks-devel] sks.domainmail.net (new!) is seeking peers.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello! I'm seeking peers for a new SKS keyserver in Atlanta, GA, USA at sks.domainmail.net. DomainMail, LLC provides Mailman mailing list services. The server is running sks v1.1.6-4 (Debian/Stretch), it was "primed" from keyserver.mattrude.com on 4-Mar-2019 with a total of 5443075 keys. My membership line: sks.domainmail.net 11370 # Jim Popovitch 0x3F1C1EF2E6019EAC646CE45227155EB4C45A2705 Please contact me for any operational issues. Thanks!! - -Jim P. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEECPbAhaBWEfiXj/kxdRlcPb+1fkUFAlx98x4ACgkQdRlcPb+1 fkWIbA/8D+rZz+xL9gIEjxBMl0hcoKU2bJ0haJCYy0zw4UDxlbO2CZ7DVtKymKSG aFgaLakBJQfBVZdy6c+fNiu1/tOUav4F9Ttuc8ZJ45r6ZoHuT+uSibzEmoJfpswq L0mvvHwcQI3iFZTrQPdQrokRGZL4hJdb66lqPeiB5/NUKqPM1vFDm4oSBGsI4c2r JmVCfbE1dW/J2IjV5fd0zfMrVnk6k5is69IUPvoUaXY8nGQ5O/FkjDl30WohhGZM MBB51kZPhGSNRZQ0lr7/t/bspH0TDCFrBAaXEEJRzx7EZWXeTInkh5SReCaCbm3h BYehauWwi1fat+vTLi1BAim5ANitUrteNyhBq1zGU20H7VehNcNMak9HFg27MpW7 Wj26DKRnrxHa+4vt7tWZ8zBOBSP1iLzd/OhyktSphvojsgs2aVXu+16/+xnUMqsd omCFmZstnZc4tQCTEcBx9CH0usCokkbJSzVfxD1m5rN34ocCr0Dc2XoOvMIp5bli fj61FjDepDKb4gDZnUpWgHHKuCh9fbP72pcMmKMyI638mQjBYcTDOwm6DMVob/Oi yqzoqQ1oRiKIHS5fSjKTHnSP3s+vZtQk69UhnQvZBWRq3SMBnvKPWDjNItuWjAR+ 8Tg3rNKBIsWO4tiGKOhl7X+nhwMZ1GWOd1lJf1Z8pF1t4N33Wvc= =9HvN -END PGP SIGNATURE- ___ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
