Re: [Sks-devel] disk full, keys.niif.hu crashed

[Tom at FlowCrypt]

I should have added, DB_LOG_AUTOREMOVE should probably be a default, too.

Whatever makes the servers more likely to survive out in the wild.

On Sat, Jun 16, 2018 at 6:34 PM, Tom at FlowCrypt <address@hidden> wrote:

I think there should be a default setting on all installations with a clear max key size.

8M is a good start, 1M is even better. 1MB well generous enough for a public key.

As a user, I shouldn't need to do download megabytes of fluff for every person I want to message.

I propose that we set and enforce max size by default.

On Sat, Jun 16, 2018 at 4:32 PM, Paul Furley <address@hidden> wrote:

Alternatively, we can view this as a great opportunity to improve the resilience of this critical infrastructure.

This is a serious, serious flaw... I'm grateful to the individual for taking the time to research and highlight this issue. Sure, not ideal that the network is struggling as a result, but at least we'll have to find a way to fix it!

Paul


  Original Message  
From: address@hidden
Sent: 16 June 2018 4:02 pm
To: address@hidden
Subject: Re: [Sks-devel] disk full, keys.niif.hu crashed

On 2018/06/15 22:42, tiker wrote:
> Well, it turns out that the cause of our issues, the method to re-create
> these keys and make things worse is already posted publicly.

There are two main ways in which critical internet infrastructure goes
on fire: a government TLA takes it down for nefarious purposes, or some
random gobshite sets it ablaze as an experiment.

The history of the internet shows that it is almost always the latter.

A

_______________________________________________
Sks-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/sks-devel
_______________________________________________
Sks-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/sks-devel