197 lines
8.7 KiB
Plaintext
197 lines
8.7 KiB
Plaintext
¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒƒ¦ƒ¦ƒ¦ƒ¦ƒ¦
|
||
ƒ cOmIN at ya with the DOPE tip ta Filter that dOme on yer |îxcerpt # o1
|
||
ƒ .-=ù. THE shoulders`--------. 2
|
||
ƒ / / //|| //|| ãÍÍÍÍ // ãÍÍÍÍ //|| _..._ _ .. . . ` 3
|
||
ƒ/ / //_||_ || \\___ // \\___ || / _ \ (_all 4
|
||
ƒ³ \_ . ``-||- || ____/\ // ____/\ || ( (_) ) -³-Glå-nut!¨ 5
|
||
ƒ \ \__/³ "" "" -----' // -----' "" `-----' \ mmmm... 6
|
||
ƒ \_____/ Sc‘nClub TheÃÅollow's ’lliance' 7
|
||
ƒ Sup SDBP... presents... @ 415-236-2371 thpt! 8
|
||
ƒ An îxcerpt from the Book of Crescent... snkt! 9
|
||
ƒ tHe 1st of buku articles commin at you, so remember "Kï•WœŠDGä ‹ Pø(/\)<29>R" 0
|
||
¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦
|
||
|
||
Network Working Group B. Miller
|
||
Request for Comments: 1097 CMU-NetDev
|
||
1 April 1989
|
||
TELNET SUBLIMINAL-MESSAGE Option
|
||
|
||
Status of this Memo
|
||
|
||
This RFC specifies a standard for the Internet community. Hosts on
|
||
the Internet that display subliminal messages within the Telnet
|
||
protocol are expected to adopt and implement this standamd.
|
||
Distribution of this memo is unlimited.
|
||
|
||
1. Command name and code.
|
||
|
||
SUBLIMINAL-MESSAGE 257
|
||
|
||
2. Command meanings.
|
||
|
||
IAC WILL SUBLIMINAL-MESSAGE
|
||
|
||
The sender of this command REQUESTS permission to, or confirms
|
||
that it will, display subliminal messages.
|
||
|
||
IAC WONT SUBLIMINAL-MESSAGE
|
||
|
||
The sender of this command REFUSES to display subliminal messages.
|
||
|
||
IAC DO SUBLIMINAL-MESSAGE
|
||
|
||
The sender of this command REQUESTS that the receiver, or grants
|
||
the receiver permission to, display subliminal messages.
|
||
|
||
IAC DONT SUBLIMINAL-MESSAGE
|
||
|
||
The sender of this command DEMANDS that the receiver not display
|
||
subliminal messages.
|
||
|
||
IAC SB SUBLIMINAL-MESSAGE <16-bit value> <16-bit value> <string> IAC
|
||
SE
|
||
|
||
The sender specifies a message to be subliminaly displayed by the
|
||
remote host. If the client has agreed (via the standard WILL WONT
|
||
DO DONT mechanism) to display subliminal messages, it must accept
|
||
this subnegotiation and attempt to display the message string on
|
||
the users console for the specified duration and continue to do so
|
||
at fixed intervals until another SUBLIMINAL-MESSAGE subnegotiation
|
||
is received. The position and rendering of the message of
|
||
|
||
Miller [Page 1]
|
||
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
|
||
implementation dependent.
|
||
|
||
The first 16-bit value specifies the duration of the message in
|
||
milliseconds. It is sent MSB first. The second 16-bit value
|
||
specifies the frequency with which the message is displayed. It
|
||
represents the number of seconds between displays and is also sent
|
||
MSB first. The final parameter is the message itself.
|
||
|
||
The syntax for this subnegotiation is:
|
||
|
||
IAC SB SUBLIMINAL-MESSAGE
|
||
DURATION[1] DURATION[0]
|
||
FREQUENCY[1] FREQUENCY[0]
|
||
MESSAGE_STRING
|
||
IAC SE
|
||
|
||
As required by the Telnet protocol, any occurence of 255 in the
|
||
subnegotiation must be doubled to destinguish it from the IAC
|
||
character (which has a value of 255).
|
||
|
||
3. Default.
|
||
|
||
WONT SUBLIMINAL-MESSAGE
|
||
|
||
DONT SUBLIMINAL-MESSAGE
|
||
|
||
i.e., subliminal messages will not be displayed.
|
||
|
||
4. Motivation for the option
|
||
|
||
Frequently the use of "Message of the day" banners and newsletters is
|
||
insufficient to convince stubborn users to upgrade to the latest
|
||
version of telnet. Some users will use the same outdated version for
|
||
years. I ran across this problem trying to convince people to use
|
||
the REMOTE-FLOW-CONTROL Telnet option. These users need to be gently
|
||
"persuaded".
|
||
|
||
5. Description and implementation notes.
|
||
|
||
The quality of the client implementation will depend on it's ability
|
||
to display and erase text strings in a small amount of time. The
|
||
current implementation at CMU takes into acount terminal line speed,
|
||
advanced video capabilities, and screen phospher persistance when
|
||
calculating how long to wait before erasing a message.
|
||
|
||
While it is permitted for the client to display the message text
|
||
"in-line", best results at obtained by printing the message at the
|
||
top or side of console screen where it will just catch the corner of
|
||
|
||
Miller [Page 2]
|
||
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
|
||
the user's visual field.
|
||
|
||
A version is currently under development at CMU to display the
|
||
message using morse-code over the keyboard caps-lock LED.
|
||
|
||
6. Examples
|
||
|
||
In the following example all numbers are in decimal notation.
|
||
|
||
1. Server suggests and client agrees to use SUBLIMINAL-MESSAGE.
|
||
|
||
(Server sends) IAC DO SUBLIMINAL-MESSAGE
|
||
(Client sends) IAC WILL SUBLIMINAL-MESSAGE
|
||
(Server sends) IAC SB SUBLIMINAL-MESSAGE 0 5 0 20 "Use VMS" IAC SE
|
||
|
||
[The server is "suggesting" that the user employ a stable
|
||
operating system, not an unreasonable request...]
|
||
|
||
The client should immediately begin displaying the message and
|
||
should continue to do so at regular intervals.
|
||
|
||
2. Server preempts previous subliminal message.
|
||
|
||
(Server sends) IAC SB SUBLIMINAL-MESSAGE 0 5 0 20 "Go home" IAC SE
|
||
|
||
The client should now no longer display the previous message and
|
||
should immediately begin displaying the new one.
|
||
|
||
3. Server has messed with user enough for one day.
|
||
|
||
(Server sends) IAC SB SUBLIMINAL-MESSAGE 0 0 0 0 "" IAC SE
|
||
|
||
The client must cease display of any subliminal messages.
|
||
|
||
7. Acknowledgements.
|
||
|
||
We do things just a little sneakier here at CMU.
|
||
|
||
Miller [Page 3]
|
||
|
||
¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ¦ƒ
|
||
Now wouldn't it be fun to implement that on a system. Have it flash
|
||
"HOT SEX"
|
||
every few milliseconds. Maybe you could catch the system manager on the
|
||
system and show him "SET UP UNPASSWORDED ACCOUNTS" or "COOPERATE WITH A HACK"
|
||
.. anyways.. . .
|
||
|
||
This only works on systems specially setup for the Subliminal Message
|
||
protocol on the Internet or similar networks. Try it out if you hack one, I
|
||
haven't had the chance. You may not find it setup though, most would probably
|
||
think it isn't practical. Except maybe CMU, and that cocky ass Miller only
|
||
gives you another reason to hack their systems heh ...
|
||
|
||
Await the the next coming MoonChildren.. . . .
|
||
415/510 ScanClub (c) 2001
|
||
|
||
|
||
|
||
|
||
X-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-X
|
||
Another file downloaded from: NIRVANAnet(tm)
|
||
|
||
&TOTSE 510/935-5845 Walnut Creek, CA Taipan Enigma
|
||
Burn This Flag 408/363-9766 San Jose, CA Zardoz
|
||
realitycheck 415/666-0339 San Francisco, CA Poindexter Fortran
|
||
Governed Anarchy 510/226-6656 Fremont, CA Eightball
|
||
New Dork Sublime 805/823-1346 Tehachapi, CA Biffnix
|
||
Lies Unlimited 801/278-2699 Salt Lake City, UT Mick Freen
|
||
Atomic Books 410/669-4179 Baltimore, MD Baywolf
|
||
Sea of Noise 203/886-1441 Norwich, CT Mr. Noise
|
||
The Dojo 713/997-6351 Pearland, TX Yojimbo
|
||
Frayed Ends of Sanity 503/965-6747 Cloverdale, OR Flatline
|
||
The Ether Room 510/228-1146 Martinez, CA Tiny Little Super Guy
|
||
Hacker Heaven 860/456-9266 Lebanon, CT The Visionary
|
||
The Shaven Yak 510/672-6570 Clayton, CA Magic Man
|
||
El Observador 408/372-9054 Salinas, CA El Observador
|
||
Cool Beans! 415/648-7865 San Francisco, CA G.A. Ellsworth
|
||
DUSK Til Dawn 604/746-5383 Cowichan Bay, BC Cyber Trollis
|
||
The Great Abyss 510/482-5813 Oakland, CA Keymaster
|
||
|
||
"Raw Data for Raw Nerves"
|
||
X-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-X
|