Sophie: fvwm2-2.2.4-14mdk i586

fvwm2-2.2.4-14mdk.i586.rpm

Info
Deps
Files
Scripts
ChangeLog
Location
Others versions
Analyse

<html>
<head>
<title>The Official FVWM Homepage - Security</title>
</head>
  <body BACKGROUND="black-stone1.jpg"
    bgcolor="#000000" text="#ffffff"
    link="#FFFF88" vlink="#EEDDDD" alink="#ff0000">
<center>
<h1><font color="pink">The Official FVWM Homepage - Security</font></h1>
</center>
<H2><A NAME="SECTION00031000000000000000">Security</A></H2>
<P>
Limited effort has been placed on security issues. In short, modules
can not communicate with Fvwm unless they are launched by Fvwm, which
means that they must be listed in the user's .fvwmrc file.
Modules can only issue commands to Fvwm that could be issued from a
menu or key binding. These measures do not keep a poorly written
module from destroying windows or terminating an X session, but they
do keep users from maliciously connecting to another users window
manager, and it should keep modules from corrupting the Fvwm internal 
databases.
    <hr>
  </body>
</html>