"What I actually advocate is security through proper management of technology where it's necessary rather than always borrowing blindly from someone else."

And yet you're looking at tty, because 'badbots don't use it these days'. Seriously, a protocol isn't secure because stuff doesn't use it, it's secure because stuff _does_ and it's still proven pretty resilient.

"It is professionally incompetent to go looking from the outset for technology to solve your problems."

If I need to open a tin can, I will go and buy a can opener. If I find that the can opener I buy is not suitable for the job, then I may look at inventing my own. But more likely, I'll go and find someone else who makes can openers to see if theirs does a better job.

Which is more or less what you're doing when you're looking at using perl, NetServer::Generic to implement your new project.

"Correct technical design is a from-scratch process in which only when it is complete and harmonious do you go looking for shortcuts and trade-offs and even then you need to know the full functional story 100% rather than assembling together a bunch of things you don't fully understand."

Maybe, but by definition if you're doing so on a computer system build by someone else, running an OS written by someone else, using an interpreted language designed by someone else, you're _not_ starting from scratch.

It's not necessary to start from scratch. Look at what you've got. Look at what you're trying to do. Then try and figure out how to get from one to the other. Personally, I don't think implementing a new protocol is the way to go, since you'll pretty much _have_ to have traffic hitting your firewall anyway. Unless you're not planning to use the IP suite, but at that point you're going to have traffic that's not routable across the public internet. It's actually more intensive for a firewall to perform protocol inspection - look at a whole packet, and try and understand what it 'is' than it is to just check the 'inbound port' field in the IP packet, and base it on that.

In reply to Re^5: How to implement a fourth protocol by Preceptor
in thread How to implement a fourth protocol by Moron

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.