| |||||||||||||
Quotes of the weekQuotes of the weekPosted Sep 22, 2011 10:12 UTC (Thu) by niner (subscriber, #26151)In reply to: Quotes of the week by james Parent article: Quotes of the week
"Microsoft makes opening .txt files dangerous" would probably have been the most correct version
(Log in to post comments)
Quotes of the week Posted Sep 22, 2011 14:41 UTC (Thu) by rgmoore (✭ supporter ✭, #75) [Link] I think you mean "Microsoft makes opening
Quotes of the week Posted Sep 22, 2011 22:04 UTC (Thu) by Tuna-Fish (subscriber, #61751) [Link]
Well technically, it only made starting programs that try to load nonexistent dll's dangerous. There's bound to be *at least one* program on windows that doesn't have that problem?
Dangerous .txt files Posted Sep 25, 2011 12:34 UTC (Sun) by pjm (subscriber, #2080) [Link]
Opening text files on Free Unix systems is also potentially dangerous. The first example I thought of was truetype rendering bugs, but the problem of text files being dangerous on Unix systems is much older than that, probably predating Linux: various terminals have escape codes that allow either direct insertion of characters into the input stream, or at least binding a key to send an arbitrary string of characters, so one might bind a key to "<arbitrary commands>;clear\n" for example. There have also been bugs in terminal emulators (I think including gnome-terminal/libvte) that could be triggered by "cat foo.txt".
Macro viruses Posted Sep 25, 2011 13:20 UTC (Sun) by pflugstad (subscriber, #224) [Link]
Any editor that supports macros (Word, Emacs, Vi, etc, etc, etc) is potentially dangerous. Macro viruses have existed in Emacs since 1992 (according to Secrets and Lies).
|
|||||||||||||