|
Server : Apache/2.4.62 System : FreeBSD fbsdweb2.web.rcn.net 14.1-RELEASE FreeBSD 14.1-RELEASE releng/14.1-n267679-10e31f0946d8 GENERIC amd64 User : www ( 80) PHP Version : 8.3.8 Disable Function : NONE Directory : /domains/wsmith.enteract/ |
Upload File : |
<html> <head> <title>SafeX</title> </head> <body bgcolor="#0000ff" text="#000000"> <img src="safex-hdr.gif" alt="[etc safex banner]" width=467 height=68> <br> <h3>Don't get caught unprotected!</h3> Is your X window system protected from prying clients? Someone could be running a client on your server without you even being aware of it. But not if you have SafeX. SafeX allows you to control explicitly which applications have access to your X server. SafeX has numerous features to help enhance your X server security. <p> The most basic access control that SafeX provides is the ability to make you aware of every client that connects to your X server. 99% of the time you know whether or not a client should be connecting to your server. With SafeX you have complete control over whether new connections are accepted or rejected, and this control is above and beyond whatever access mechanism you are currently using. With SafeX you can even use "xhost +" and remain secure. <p> With normal X security mechanisms once a client obtains access to your server it can do anything (essentially every client is the equivalent of super-user). However, with SafeX you can control the behavior of untrusted applications. Should that shareware program really be reading keyboard events from your terminal windows? With SafeX you can prevent this and more. <p> Features: <br> <ul> <li>Motif(tm) style user interface <li>Works with your existing X server software <li>Runs standalone or under XDM <li>Allows all client connections to be controlled <li>Helps limit the behavior of untrusted clients <li>User selectable security controls on a per-client basis <li>Currently runs on SunOS 4.1.x and Solaris 2.x <li>Works with MIT X or OpenWindows servers </ul> <br> </body> </html>