Search the FAQ Archives

3 - A - B - C - D - E - F - G - H - I - J - K - L - M
N - O - P - Q - R - S - T - U - V - W - X - Y - Z
faqs.org - Internet FAQ Archives

comp.windows.x Frequently Asked Questions (FAQ) 6/7
Section - 132) How do I get around the frame-buffer security hole?

( Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Single Page )
[ Usenet FAQs | Web FAQs | Documents | RFC Index | Restaurant inspections ]


Top Document: comp.windows.x Frequently Asked Questions (FAQ) 6/7
Previous Document: 131) How do I get around the SunOS 4.1 security hole?
Next Document: 133) TOPIC: BUILDING X PROGRAMS
See reader questions & answers on this topic! - Help others by sharing your knowledge

	On many systems the frame-buffer is unsecured by default; this permits 
anyone who can log into your workstation to peek at your windowing session by 
accessing the frame-buffer directly, or, as less of a privacy issue but perhaps
more annoying, to [accidentally] start up a second X session on your console 
display. Check the man page for fbtab(5).

[Thanks to Art Mulder (art@cs.ualberta.ca); 2/93.]

User Contributions:

Comment about this article, ask questions, or add new information about this topic:



Top Document: comp.windows.x Frequently Asked Questions (FAQ) 6/7
Previous Document: 131) How do I get around the SunOS 4.1 security hole?
Next Document: 133) TOPIC: BUILDING X PROGRAMS

Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Single Page

[ Usenet FAQs | Web FAQs | Documents | RFC Index ]

Send corrections/additions to the FAQ Maintainer:
faq%craft@uunet.uu.net (X FAQ maintenance address)




Last Update March 27 2014 @ 02:12 PM