-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 19/11/16 04:16, Michael Jones wrote:
> On 18/11/16 23:55, Kristian Fiskerstrand wrote:
>> On 11/19/2016 12:43 AM, Valentin Sundermann wrote:
Hi,
>> Do you mind me asking how you got those charts on your
>> page? Tried the Github
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 18/11/16 23:55, Kristian Fiskerstrand wrote:
> On 11/19/2016 12:43 AM, Valentin Sundermann wrote:
>>> Hi,
> Do you mind me asking how you got those charts on your
> page? Tried the Github files linked to at the bottom but
> they only
On 11/18/2016 8:09 PM, Gunnar Wolf wrote:
> Jeremy T. Bouse dijo [Fri, Nov 18, 2016 at 02:29:12PM -0500]:
>> I'm just curious if anyone has looked at running SKS within
>> containers using Docker? I've seen a couple images on the Docker hub
>> that appear to be based on Alpine Linux but was
On 11/19/2016 12:43 AM, Valentin Sundermann wrote:
> Hi,
>> Do you mind me asking how you got those charts on your page? Tried the
>> Github files linked to at the bottom but they only appear to give me a
>> different key search page.
> Oh, I could have known that this leads to confusion. I
On 11/17/2016 11:28 AM, Valentin Sundermann wrote:
> Hey,
>
>> Obviously I need to resolve the peer timeout issue but any advice how I
>> might speed up the gossip process in general? I've noticed looking at
>> the stats that the new/updated keys seem to come in bursts during a
>> window between
I'm just curious if anyone has looked at running SKS within
containers using Docker? I've seen a couple images on the Docker hub
that appear to be based on Alpine Linux but was curious if anyone on
here had attempted.
smime.p7s
Description: S/MIME Cryptographic Signature
On 17/11/2016 5:28 pm, Valentin Sundermann wrote:
> Best regards,
> Valentin Sundermann
>
>
> [1] https://keys.vsund.de/stats/
>
>
Do you mind me asking how you got those charts on your page? Tried the
Github files linked to at the bottom but they only appear to give me a
different key search
On 18/11/2016 10:35 am, Kim Minh Kaplan wrote:
> The DNS server does respond but it is *not* responsive (not quick
> enough) over TCP.
>
> $ dig +norecurse +noall +stats @66.33.206.206 pgp.key-server.io
> ;; Query time: 133 msec
> ;; SERVER: 66.33.206.206#53(66.33.206.206)
> ;;
On 11/18/2016 11:35 AM, Kim Minh Kaplan wrote:
> $ dig +norecurse +noall +stats +tcp +time=20 @66.33.206.206
> pgp.key-server.io
> ;; Query time: 14056 msec
> ;; SERVER: 66.33.206.206#53(66.33.206.206)
Still better than me not getting there at all:
$ traceroute 66.33.206.206
Danny Horne wrote:
> On 18/11/2016 8:29 am, Kristian Fiskerstrand wrote:
>> http://dnsviz.net/d/pgp.key-server.io/dnssec/
>>
>> "key-server.io zone: The server(s) were not responsive to queries over
>> TCP. (66.33.206.206)"
>>
>
> https://intodns.com/key-server.io
>
> 'OK. Seems all your DNS
On 18/11/2016 8:29 am, Kristian Fiskerstrand wrote:
> http://dnsviz.net/d/pgp.key-server.io/dnssec/
>
> "key-server.io zone: The server(s) were not responsive to queries over
> TCP. (66.33.206.206)"
>
https://intodns.com/key-server.io
'OK. Seems all your DNS servers allow TCP connections. This
On 11/18/2016 05:15 AM, Carles Tubio Terrón wrote:
> El Sun, 6 Nov 2016 15:58:43 +
> Danny Horne escrigué:
>
>> On 06/11/2016 2:57 pm, Carles Tubio Terrón wrote:
>>> Thank you Moritz and Danny,
>>> Im so sorry, i was investigating and had the service down at that
>>>
12 matches
Mail list logo