asciilifeform: the realization comes from the fact that you don't really need accurate time, just an oscillator that is reasonably independence of amplitude
asciilifeform: other folks can perhaps work it out if i say that the solution is based on dynamic 'predator-prey' equilibrium
asciilifeform: which is why before saying any more, i will have to model it.
asciilifeform: must also work on uclibc and, possibly, musl
asciilifeform: as in, one that jurov would be willing to read & sign
asciilifeform: what is the shortest known implementation ?
asciilifeform: familiar with term 'attack surface' ?
asciilifeform: what'll folks propose to put on this poor box next? 'samba' ?
asciilifeform: jurov: flood is not the only known past ntp vuln
asciilifeform: shinohai: jurov just described a 'business class' that ~will bother~
asciilifeform: rather than the classical 'ocean of shit down your pipe' sense
asciilifeform: jurov: again, i was speaking of ddos in the sense of 'if it is trivial to take out pogo with a nudge that no one else will notice, it will be done'
asciilifeform: and that the thing can be taken out of commission entirely by the cheapest mitm.
asciilifeform: ntp means that you now have a multimegabyte leprous turd on your box.
asciilifeform: (the latter is an entirely separate conversation)
asciilifeform: i am concerned with 'pogos will fall like dominoes from simple and cheap nudge' rather than 'in the dark future where being a known bitcoin user merits gassing'
asciilifeform: this is not a mechanical problem, yes
asciilifeform: jurov: if they're 5000 residential lines in usa, just send the gasenwagen, aha
asciilifeform: the 'ddos' i'm concerned with is more that we are setting up a box with unique vulnerabilities
asciilifeform: who, precisely, can ddos (in the traditional sense) 5,000 ip ?☟︎
asciilifeform: we know the basic shape of the answer, just not the particulars.
