I already can do per-window themes based on executables, here's the issue..
Say I want to start up a virtual machine in VMWare. I can make the VM Workstation or Player executable associated with a window "style" but can't currently base the style on the selinux security label of the vmware vmx file. This is the goal. I currently am showing a proof of concept by having the window name (based on the VM file run) be the basis for the window style. This allows multiple window stylesfor the same executable (VMPlayer). The problem is that this is relatively easy to spoof and our client, needless to say, is as picky as you could imagine about security. Dave -----Original Message----- From: Dan Espen [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 15, 2006 12:19 PM To: Thomson, David-P63356 Subject: Re: FVWM for "government" system You'll do better replying to the list than to me. The window manager knows nothing about the executables name. If all the executables are your own, you can change the window class, resource, or name to get fvwm's attention. -----Original Message----- Subject: RE: FVWM for "government" system Date: Tue, 15 Aug 2006 12:15:18 -0700 From: "Thomson, David-P63356" <[EMAIL PROTECTED]> To: "Dan Espen" <[EMAIL PROTECTED]> Thanks. Correct on selinux. That's the integration we have to do. Associate a window theme with the executables security label. Dave -----Original Message----- From: Dan Espen [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 15, 2006 12:12 PM To: Thomson, David-P63356 Cc: fvwm@fvwm.org Subject: Re: FVWM for "government" system "Thomson, David-P63356" <[EMAIL PROTECTED]> writes: > FVWM Developers, > > I was told I can only ask questions on here if I am sufficiently vague > about what we are doing. I work for a government contractor and we are > currently working on a contract for one of those 3-lettered agencies to > do something with PCs and I am in charge (at the moment) of the UI > design. Suffice it to say that our final project will be used by most > every gov/mil agency at some point in the coming years. We did a market > survey of window managers for the UI a while back and actually have > chosen FVWM. Enough said... > > Here's my hopefully simple task: learn enough about FVWM to modify it > to meet our needs. Seeing as I am still an amateur in modifying WMs, I > hope to pick all your brains, and maybe get a little help while writing > these changes. Having FVWM on many MANY systems in 3-letter abbreviated > organizations and "special operations" type organizations along with > getting your beloved FVWM to become pretty ubiquitous may be motivating > factors. > > Let me know if this is the place to ask questions and if any of you are > "willing and able". > > My first task involves SELinux security labels and per-window > decoration. > > Dave Please don't send html to this list. To ask questions about fvwm, use the email address [EMAIL PROTECTED] SELinux security labels seem to be properties of the file system, not x windows. I'm not clear on what you want to do. -- Dan Espen E-mail: [EMAIL PROTECTED]
