Postel, J. and J. Reynolds, "TELNET Option Specifications", STD 8, RFC 855, May 1983. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
Detecting Backdoors - Zhang, Paxson (2000) (5 citations) (Correct)
....is NUL, rather than the first byte. This is necessary because we find that clients tend to send their first NUL in its own packet, and the remainder of the prolog information in a second packet. 4. 3 Telnet The Telnet protocol [PR83a] includes a quite general mechanism for negotiating options [PR83b]. Since most Telnet sessions begin with a series of option negotiations, we can attempt to detect these, which have a distinct pattern, taking one of the following four 3 byte formats: IAC WILL option code IAC WON T option code IAC DO option code IAC DON T option code The code values for WILL, ....
J. Postel and J. Reynolds, "Telnet Option Specifications, " RFC 855, Network Information Center, SRI International, Menlo Park, CA, May 1983.
Detecting Stepping Stones - Zhang, Paxson (2000) (13 citations) (Correct)
....an approach is adopted in [SH95] and proves effective. Considerable care must be taken, though, because we will not find a perfect match between two stepping stone connections. They may differ due to translations of characters such as escape sequences, or the varying presence of Telnet options [PR83b]. In addition, suppose we are monitoring connections and , where is the stepping stone the attacker is using to access ( from . If we adopt a notion of binning in order to group activity into different time regions (for example to compute character ....
J. Postel and J. Reynolds, "Telnet Option Specifications, " RFC 855, Network Information Center, SRI International, Menlo Park, CA, May 1983.
Bro: A System for Detecting Network Intruders in Real-Time - Paxson (1998) (103 citations) (Correct)
....presently, the analyzer recognizes one operating system that supports this (VMS) and, for it only, expands the escape sequence into the text of the previous line. Telnet options. The Telnet protocol supports a rich, complex mechanism for exchanging options between the client and server [PR83b] (there are more than 50 RFCs discussing different Telnet options) Unhappily, we cannot ignore the possible presence of these options in our analysis, because an attacker can embed one in the middle of text they transmit in order to disguise their intent for example, ro option ot . The Telnet ....
J. Postel and J. Reynolds, "Telnet Option Specifications, " RFC 855, Network Information Center, SRI International, Menlo Park, CA, May 1983.
Detecting Backdoors - Zhang, Paxson (2000) (5 citations) (Correct)
....is NUL, rather than the first byte. This is necessary because we find that clients tend to send their first NUL in its own packet, and the remainder of the prolog information in a second packet. 4. 3 Telnet The Telnet protocol [PR83a] includes a quite general mechanism for negotiating options [PR83b]. Since most Telnet sessions begin with a series of option negotiations, we can attempt to detect these, which have a distinct pattern, taking one of the following four 3 byte formats: IAC WILL option code IAC WON T option code IAC DO option code IAC DON T option code The code values for ....
J. Postel and J. Reynolds, "Telnet Option Specifications, " RFC 855, Network Information Center, SRI International, Menlo Park, CA, May 1983.
Detecting Stepping Stones - Zhang, Paxson (2000) (13 citations) (Correct)
....an approach is adopted in [SH95] and proves effective. Considerable care must be taken, though, because we will not find a perfect match between two stepping stone connections. They may differ due to translations of characters such as escape sequences, or the varying presence of Telnet options [PR83b]. In addition, suppose we are monitoring connections h 1 h 2 and h 2 h 3 , where h 2 is the stepping stone the attacker is using to access h 3 from h 1 . If we adopt a notion of binning in order to group activity into different time regions (for example to compute character frequencies as ....
J. Postel and J. Reynolds, "Telnet Option Specifications, " RFC 855, Network Information Center, SRI International, Menlo Park, CA, May 1983.
Bro: A System for Detecting Network Intruders in Real-Time - Paxson (1998) (103 citations) (Correct)
....presently, the analyzer recognizes the operating system that supports this (VMS) and, for it only, expands the escape sequence into the text of the previous line. Telnet options. The Telnet protocol supports a rich, complex mechanism for exchanging options between the client and server [PR83b] (there are more than 50 RFCs discussing different Telnet options) Unhappily, we cannot ignore the possible presence of these options in our analysis, because an attacker can embed one in the middle of text they transmit in order to disguise their intent for example, ro option ot . The Telnet ....
J. Postel and J. Reynolds, "Telnet Option Specifications, " RFC 855, Network Information Center, SRI International, Menlo Park, CA, May 1983.
Unknown - (Correct)
No context found.
Postel, J. and J. Reynolds, "TELNET Option Specifications", STD 8, RFC 855, May 1983.
Network Working Group T. Ts'o Request for Comments: 2942 VA.. - Status Of This (Correct)
No context found.
Postel, J. and J. Reynolds, "Telnet Option Specifications", STD
Unknown - (Correct)
No context found.
J. Postel and J. Reynolds, "Telnet Option Specifications," RFC 855, May 1983.
Network Working Group T. Dierks Request for Comments: 2246.. - Version Status Of (Correct)
No context found.
Postel J., and J. Reynolds, "Telnet Option Specifications", STD 8, RFC 855, May 1993.
Unknown - (Correct)
No context found.
Postel, J. and J. Reynolds, "Telnet Option Specifications", RFC 855, USC/Information Sciences Institute, May 1983.
Network Working Group R. Gellens Request for Comments: 2066.. - Status Of This (Correct)
No context found.
Postel, J. and J. Reynolds, "Telnet Option Specifications", STD 8, RFC 855, ISI, May 1983.
Network Working Group T. Murphy, Jr. Request for Comments.. - Status Of This (Correct)
No context found.
Postel, J. and J. Reynolds, "Telnet Option Specifications", STD 8, RFC 855, May 1983.
Unknown - (Correct)
No context found.
Postel, J. and J. Reynolds, "Telnet Option Specification", STD
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC