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:

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 nameserver

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

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

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

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

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 wr

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 > &

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

[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

[Sks-devel] sks.domainmail.net (new!) is seeking peers.

ttrude.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- iQIzBAEBCgAdFiEECPbAhaBWEfiX