Yes, TFTP is normally done over UDP, but there's nothing that says it must be. In fact, IIRC, the RFC explicitly states that other transport layers are OK. Be sure to check out some the extentions to it that can improve efficiency.

A quick google found RFCs 783, and 1350---does it having only two RFCs associated with it sound right to you?

Also, does it support sessions? (I'd think not), because I would guess that multiple files will need to be sent with some requests--files that I would prefer not to waste time authenticating over again

Actually, I could probably make it a session based tftp... but...

I guess, I am more confuse now than before--I have much to grok.

In reply to Re: Re: Re: Re: CGI/FTP security question by dakedesu
in thread CGI/FTP security question by dakedesu

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.