-=> On 03-16-19 04:27, mark lewis wrote to Tony Langdon <=-

 ml> at one time, my makenl was configured to allow operators to submit
 ml> their own individual nodelist entries... it worked quite well when the
 ml> proper format and data was submitted...

Which then relies too much on human input.  Wouldn't be the first time I've
typod something.  I only discovered half of my nodelist was broken when I
started generating DNS RRs for it, and finding that half of the entries didn't
convert.  I don't see why in 2019 we need to be relying so heavily on humans to
validate syntax that can be done by machine.  Let the machine do that and let
the people look at the _content_.

 ml> already done and handled since eons... just no web interface where you
 ml> have to employ more security than necessary to prevent bots and humans
 ml> from attacking, changing others' entries, submitting invalid/false
 ml> data, etc... a NC/HUB should know who is in their segment and not just
 ml> rubber stamp what is sent to them for processing... the RCs/ZCs have to
 ml> have some trust in their NCs but they should also still check the
 ml> segments they generate to send upstream...

Good points re security.  I still think some machine validation of syntax on
entry/generation would be helpful.  Obviously, only a human can verify that the
contents of the nodelist entries are actually correct.

 ml> how do you know if/when invalid data gets in? i'm speaking of data that
 ml> passes the tests but is still invalid/incorrect...

ATM, it's a one man show, so same way you do - manually. ;)


... Error: Bad Or Missing Mouse Driver. Blame The Cat?? (Y/n)
=== MultiMail/Win v0.51
--- SBBSecho 3.03-Linux