Files
JargonFile/original/html/S/screaming-tty.html
2014-03-27 18:54:56 +00:00

13 lines
2.3 KiB
HTML
Raw Permalink Blame History

This file contains invisible Unicode characters
This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
<?xml version="1.0" encoding="ISO-8859-1" standalone="no"?>
<html xmlns="http://www.w3.org/1999/xhtml"><head><title>screaming tty</title><link rel="stylesheet" href="../../jargon.css" type="text/css"/><meta name="generator" content="DocBook XSL Stylesheets V1.61.0"/><link rel="home" href="../index.html" title="The Jargon File"/><link rel="up" href="../S.html" title="S"/><link rel="previous" href="scream-and-die.html" title="scream and die"/><link rel="next" href="screen.html" title="screen"/></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">screaming tty</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="scream-and-die.html">Prev</a> </td><th width="60%" align="center">S</th><td width="20%" align="right"> <a accesskey="n" href="screen.html">Next</a></td></tr></table><hr/></div><dt><a id="screaming-tty"/><dt xmlns="" id="screaming-tty"><b>screaming tty</b>: <span xmlns="http://www.w3.org/1999/xhtml" class="grammar">n.</span></dt></dt><dd><p> [Unix] A terminal line which spews an infinite number of random
characters at the operating system. This can happen if the terminal is
either disconnected or connected to a powered-off terminal but still
enabled for login; misconfiguration, misimplementation, or simple bad luck
can start such a terminal screaming. A screaming tty or two can seriously
degrade the performance of a vanilla Unix system; the arriving
&#8220;<span class="quote">characters</span>&#8221; are treated as userid/password pairs and tested
as such. The Unix password encryption algorithm is designed to be
computationally intensive in order to foil brute-force crack attacks, so
although none of the logins succeeds; the overhead of rejecting them all
can be substantial.</p></dd><div class="navfooter"><hr/><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="scream-and-die.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="../S.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="screen.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">scream and die </td><td width="20%" align="center"><a accesskey="h" href="../index.html">Home</a></td><td width="40%" align="right" valign="top"> screen</td></tr></table></div></body></html>