Telnet Protocol specification

Postel, J.; Reynolds, J. K.

doi:10.17487/rfc0764

Cited by 67 publications

(14 citation statements)

References 1 publication

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…CodeRed uses HTTP [12]. Other vulnerabilities exploit Telnet [29], SMB [38], HTTP or RPC. We have also examined some other protocols such as RTP [36] and SMTP [17] during the design of our policy language.…”

Section: Methodsmentioning

confidence: 99%

Shield

Wang

Guo

Simón

et al. 2004

Proceedings of the 2004 Conference on Applications, Technologies, Architectures, and Protocols for Computer Communications

147

View full text Add to dashboard Cite

Software patching has not been effective as a first-line defense against large-scale worm attacks, even when patches have long been available for their corresponding vulnerabilities. Generally, people have been reluctant to patch their systems immediately, because patches are perceived to be unreliable and disruptive to apply. To address this problem, we propose a first-line worm defense in the network stack, using shields -vulnerability-specific, exploit-generic network filters installed in end systems once a vulnerability is discovered, but before a patch is applied. These filters examine the incoming or outgoing traffic of vulnerable applications, and correct traffic that exploits vulnerabilities. Shields are less disruptive to install and uninstall, easier to test for bad side effects, and hence more reliable than traditional software patches. Further, shields are resilient to polymorphic or metamorphic variations of exploits [43].In this paper, we show that this concept is feasible by describing a prototype Shield framework implementation that filters traffic above the transport layer. We have designed a safe and restrictive language to describe vulnerabilities as partial state machines of the vulnerable application. The expressiveness of the language has been verified by encoding the signatures of several known vulnerabilites. Our evaluation provides evidence of Shield's low false positive rate and small impact on application throughput. An examination of a sample set of known vulnerabilities suggests that Shield could be used to prevent exploitation of a substantial fraction of the most dangerous ones.

show abstract

Section: Methodsmentioning

confidence: 99%

Shield

Wang

Guo

Simón

et al. 2004

Proceedings of the 2004 Conference on Applications, Technologies, Architectures, and Protocols for Computer Communications

147

View full text Add to dashboard Cite

show abstract

“…Analyzing the ratio of different types of traffic in the total transit route traffic revealed that monitoring (management) traffic occupied negligible capacity compared to total network requirements. Telecommunication equipment is most frequently monitored using Telnet [45], SSH [46], SNMP [47], and TR-69 CPE WAN [48] management protocols. These protocols use two-way communication and losing packets hinders their interactive functioning.…”

Section: Impact Of Network Performance On Monitoring Internet Andmentioning

confidence: 99%

Network Performance Criteria for Telecommunication Traffic Types driven by Quality of Experience

Ramadža¹,

Pekić

Ožegović

2019

J. commun. softw. syst. (Online)

View full text Add to dashboard Cite

A common reason for changing the chosen service provider is the users' perception of service. Quality of Experience (QoE) describes the end user's perception of service while using it. A frequent cause of QoE degradation is inadequate traffic routing, where, other than throughput, selected routes do not satisfy minimum network requirements for the given service or services. In order to enable QoE-driven routing, per traffic type defined routing criteria are required. Our goal was to obtain those criteria for relevant services of a telecom operator. For the purpose of identifying services of interest, we first provide short results of user traffic analysis within the telecom operator network. Next, our work presents testbed measurements which explore the impact of packet loss and delay on user QoE for video, voice, and management traffic. For video services, we investigated separately multicast delivery, unicast HTTP Live Streaming (HLS), and unicast Real Time Streaming Protocol (RTSP) traffic. Applying a threshold to QoE values, from the measured dependencies we extracted minimum network performance criteria for the investigated different types of traffic. Finally, we provide a comparison with results available in the literature on the topic.

show abstract

“…• Telnet server is setup at server side of the network for accepting Telnet requests, commonly over TCP port 23 [31].…”

Section: Telnet Servermentioning

confidence: 99%

Embedded Network Firewall on FPGA

Ajami

Dinh

2011

2011 Eighth International Conference on Information Technology: New Generations

View full text Add to dashboard Cite

In presenting this thesis in partial fulfilment of the requirements for a Postgraduate degree from the University of Saskatchewan, I agree that the Libraries of this University may make it freely available for inspection. I further agree that permission for copying of this thesis in any manner, in whole or in part, for scholarly purposes may be granted by the professor or professors who supervised my thesis work or, in their absence, by the Head of the Department or the Dean of the College in which my thesis work was done. It is understood that any copying or publication or use of this thesis or parts thereof for financial gain shall not be allowed without my written permission. It is also understood that due recognition shall be given to me and to the University of Saskatchewan in any scholarly use which may be made of any material in my thesis.

show abstract

Telnet Protocol specification

Cited by 67 publications

References 1 publication

Shield

Shield

Network Performance Criteria for Telecommunication Traffic Types driven by Quality of Experience

Embedded Network Firewall on FPGA

Contact Info

Product

Resources

About