Good evening, I am currently playing around with L4Linux+DOpE and would like to 1. Start and kill L4 processes at runtime (fprov-l4 and run-l4 do not work). 2. Disable the DOpE mouse pointer in the L4Linux console window. 3. Resize the L4Linux console window without just stretching it. 3. Play Quake :) (where do I get it?) Any hints highly appreciated. Regards, Michael -- Sirrix AG security technologies - http://www.sirrix-ag.de Michael Scheibel eMail: m.scheibel@sirrix.com Tel +49(234) 610 071-124 Public key on demand Fingerprint 009B 9963 7B28 4356 CA43 5BFD 17A4 AE0F 6943 4B54 This email may contain confidential legal information: if received by not authorised person please advice our firm and destroy it. Anyway every transmitted information shall be treated strictly confidentially.
Hi Michael, On Thursday 10 November 2005 17:19, Michael Scheibel wrote:
I am currently playing around with L4Linux+DOpE and would like to
1. Start and kill L4 processes at runtime (fprov-l4 and run-l4 do not work).
Please could you be a little bit more specific? "Does not work" does not help us in finding the bug. Normally, you start fprov-l4 as L4Linux application in a directory. fprov-l4 provides a service which is used by run-l4. run-l4 depends on the loader, so if you don't have started the L4 loader at runtime, run-l4 will not be able to locate it but run-l4 will show you an appropriate message -- at least more than "does not work" :-)
2. Disable the DOpE mouse pointer in the L4Linux console window. 3. Resize the L4Linux console window without just stretching it.
AFAIK these features are not implemented in DOpE.
3. Play Quake :) (where do I get it?)
The Quake port is not available for public use. Frank -- ## Dept. of Computer Science, Dresden University of Technology, Germany ## ## http://os.inf.tu-dresden.de/~fm3 ##
On Thursday 10 November 2005 17:34, Frank Mehnert wrote:
Hi Michael,
On Thursday 10 November 2005 17:19, Michael Scheibel wrote:
I am currently playing around with L4Linux+DOpE and would like to
1. Start and kill L4 processes at runtime (fprov-l4 and run-l4 do not work).
Please could you be a little bit more specific? "Does not work" does not help us in finding the bug. Normally, you start fprov-l4 as L4Linux application in a directory. fprov-l4 provides a service which is used by run-l4. run-l4 depends on the loader, so if you don't have started the L4 loader at runtime, run-l4 will ^^^^^^^^^^ Sorry, at boottime (from your menu.lst) of course.
not be able to locate it but run-l4 will show you an appropriate message -- at least more than "does not work" :-)
2. Disable the DOpE mouse pointer in the L4Linux console window. 3. Resize the L4Linux console window without just stretching it.
AFAIK these features are not implemented in DOpE.
3. Play Quake :) (where do I get it?)
The Quake port is not available for public use.
Frank
-- ## Dept. of Computer Science, Dresden University of Technology, Germany ## ## http://os.inf.tu-dresden.de/~fm3 ##
Am Donnerstag 10 November 2005 17:42 schrieb Frank Mehnert:
On Thursday 10 November 2005 17:34, Frank Mehnert wrote:
Hi Michael,
On Thursday 10 November 2005 17:19, Michael Scheibel wrote:
I am currently playing around with L4Linux+DOpE and would like to
1. Start and kill L4 processes at runtime (fprov-l4 and run-l4 do not work).
Please could you be a little bit more specific? "Does not work" does not help us in finding the bug. Normally, you start fprov-l4 as L4Linux application in a directory. fprov-l4 provides a service which is used by run-l4. run-l4 depends on the loader, so if you don't have started the L4 loader at runtime, run-l4 will
^^^^^^^^^^ Sorry, at boottime (from your menu.lst) of course.
not be able to locate it but run-l4 will show you an appropriate message -- at least more than "does not work" :-)
The loader is used to load l4linux via bmodfs: loader --fprov=BMODFS l4linux26.cfg fprov-l4 seems to register correctly. "run-l4 vscrtest" then results in l4lx: l4x_syscall_guard: Syscall2 was forbidden for fprov-l4(2028) at 0x080 l4lx: 48476
2. Disable the DOpE mouse pointer in the L4Linux console window. 3. Resize the L4Linux console window without just stretching it.
AFAIK these features are not implemented in DOpE.
Where do I start best to implement these features? Writing emails can be a horrible thing without them :) Regards, Michael -- Sirrix AG security technologies - http://www.sirrix-ag.de Michael Scheibel eMail: m.scheibel@sirrix.com Tel +49(234) 610 071-124 Public key on demand Fingerprint 009B 9963 7B28 4356 CA43 5BFD 17A4 AE0F 6943 4B54 This email may contain confidential legal information: if received by not authorised person please advice our firm and destroy it. Anyway every transmitted information shall be treated strictly confidentially.
On Thu Nov 10, 2005 at 18:09:01 +0100, Michael Scheibel wrote:
l4lx: l4x_syscall_guard: Syscall2 was forbidden for fprov-l4(2028) at 0x080 l4lx: 48476
I've commited a fix for this. Adam -- Adam adam@os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/
Am Sonntag 13 November 2005 14:32 schrieb Adam Lackorzynski:
On Thu Nov 10, 2005 at 18:09:01 +0100, Michael Scheibel wrote:
l4lx: l4x_syscall_guard: Syscall2 was forbidden for fprov-l4(2028) at 0x080 l4lx: 48476
I've commited a fix for this.
Hi Adam, thank you for the fix, unfortunately cvs diff does not report it yet. What file(s) did you modify? Regards, Michael -- Sirrix AG security technologies - http://www.sirrix-ag.de Michael Scheibel eMail: m.scheibel@sirrix.com Tel +49(234) 610 071-124 Public key on demand Fingerprint 009B 9963 7B28 4356 CA43 5BFD 17A4 AE0F 6943 4B54 This email may contain confidential legal information: if received by not authorised person please advice our firm and destroy it. Anyway every transmitted information shall be treated strictly confidentially.
On Monday 14 November 2005 12:21, Michael Scheibel wrote:
Am Sonntag 13 November 2005 14:32 schrieb Adam Lackorzynski:
On Thu Nov 10, 2005 at 18:09:01 +0100, Michael Scheibel wrote:
l4lx: l4x_syscall_guard: Syscall2 was forbidden for fprov-l4(2028) at 0x080 l4lx: 48476
I've commited a fix for this.
Hi Adam,
thank you for the fix, unfortunately cvs diff does not report it yet. What file(s) did you modify?
The modified file is arch/l4/kernel/hybrid.c. Which command did you use to check for updates? 'cvs diff' will not work because it would show you the difference of the files you checked out against the _corresponding versions_ of the reporsitory. The command you need is 'cvs -n update'! I've just checked our remote_cvs: The patch is comitted. Frank -- ## Dept. of Computer Science, Dresden University of Technology, Germany ## ## http://os.inf.tu-dresden.de/~fm3 ##
On Monday 14 November 2005 13:00, Frank Mehnert wrote:
On Monday 14 November 2005 12:21, Michael Scheibel wrote:
Am Sonntag 13 November 2005 14:32 schrieb Adam Lackorzynski:
On Thu Nov 10, 2005 at 18:09:01 +0100, Michael Scheibel wrote:
l4lx: l4x_syscall_guard: Syscall2 was forbidden for fprov-l4(2028) at 0x080 l4lx: 48476
I've commited a fix for this.
Hi Adam,
thank you for the fix, unfortunately cvs diff does not report it yet. What file(s) did you modify?
The modified file is arch/l4/kernel/hybrid.c. Which command did you use to check for updates? 'cvs diff' will not work because it would show you the difference of the files you checked out against the _corresponding versions_ of the reporsitory. The command you need is 'cvs -n update'!
Or 'cvs diff -rBASE -rHEAD' of course. Frank -- ## Dept. of Computer Science, Dresden University of Technology, Germany ## ## http://os.inf.tu-dresden.de/~fm3 ##
On Mon Nov 14, 2005 at 13:00:11 +0100, Frank Mehnert wrote:
On Monday 14 November 2005 12:21, Michael Scheibel wrote:
Am Sonntag 13 November 2005 14:32 schrieb Adam Lackorzynski:
On Thu Nov 10, 2005 at 18:09:01 +0100, Michael Scheibel wrote:
l4lx: l4x_syscall_guard: Syscall2 was forbidden for fprov-l4(2028) at 0x080 l4lx: 48476
I've commited a fix for this.
Hi Adam,
thank you for the fix, unfortunately cvs diff does not report it yet. What file(s) did you modify?
The modified file is arch/l4/kernel/hybrid.c. Which command did you use to
That's a little typo, it's syscall_guard.c. Adam -- Adam adam@os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/
Am Montag 14 November 2005 13:37 schrieb Adam Lackorzynski:
On Mon Nov 14, 2005 at 13:00:11 +0100, Frank Mehnert wrote:
On Monday 14 November 2005 12:21, Michael Scheibel wrote:
Am Sonntag 13 November 2005 14:32 schrieb Adam Lackorzynski:
On Thu Nov 10, 2005 at 18:09:01 +0100, Michael Scheibel wrote:
l4lx: l4x_syscall_guard: Syscall2 was forbidden for fprov-l4(2028) at 0x080 l4lx: 48476
I've commited a fix for this.
Hi Adam,
thank you for the fix, unfortunately cvs diff does not report it yet. What file(s) did you modify?
The modified file is arch/l4/kernel/hybrid.c. Which command did you use to
That's a little typo, it's syscall_guard.c.
Yep, now it works. Thanks! Regards, Michael -- Sirrix AG security technologies - http://www.sirrix-ag.de Michael Scheibel eMail: m.scheibel@sirrix.com Tel +49(234) 610 071-124 Public key on demand Fingerprint 009B 9963 7B28 4356 CA43 5BFD 17A4 AE0F 6943 4B54 This email may contain confidential legal information: if received by not authorised person please advice our firm and destroy it. Anyway every transmitted information shall be treated strictly confidentially.
Hi, On Thu, Nov 10, 2005 at 05:19:02PM +0100, Michael Scheibel wrote:
2. Disable the DOpE mouse pointer in the L4Linux console window.
Why do you want to do this? Dope is your (secure) GUI and it should always be able to indicate its focus and the mouse position. What does X11 with the mouse cursor if you write an email? Nonetheless, you could hack dope to not only "grab" the mouse, but also "make it invisible".
3. Resize the L4Linux console window without just stretching it.
To change this, the L4Linux console stub must be modified. As we only use one stub for l4con (fixed resolution) and dope, we will not implement such a feature. A modified stub would try to adapt to window size changes (hopefully) propagated by dope.
3. Play Quake :) (where do I get it?)
Maybe there's an install package for your Linux distribution or Windows around. For my Debian, there is :-) Ciao -- Christian Helmuth TU Dresden, Dept. of CS Operating Systems Group http://os.inf.tu-dresden.de/~ch12
Am Freitag 11 November 2005 12:26 schrieb Christian Helmuth:
Hi,
On Thu, Nov 10, 2005 at 05:19:02PM +0100, Michael Scheibel wrote:
2. Disable the DOpE mouse pointer in the L4Linux console window.
Why do you want to do this? Dope is your (secure) GUI and it should always be able to indicate its focus and the mouse position. What does X11 with the mouse cursor if you write an email?
Well, it's quite difficult to pull down menus because the two mouse pointers do not overlay and the DoPE mouse pointer cannot leave the (active) L4Linux console window.
Nonetheless, you could hack dope to not only "grab" the mouse, but also "make it invisible".
Unfortunately this won't solve the problem stated above.
3. Resize the L4Linux console window without just stretching it.
To change this, the L4Linux console stub must be modified. As we only use one stub for l4con (fixed resolution) and dope, we will not implement such a feature. A modified stub would try to adapt to window size changes (hopefully) propagated by dope.
Maybe I am going to take a look in a spare minute. A q&d hack might do the job, don't you think?
3. Play Quake :) (where do I get it?)
Maybe there's an install package for your Linux distribution or Windows around. For my Debian, there is :-)
Actually I would prefer a secure Quake ;) Hm, this seems to be a low latency list - thank you! Regards, Michael -- Sirrix AG security technologies - http://www.sirrix-ag.de Michael Scheibel eMail: m.scheibel@sirrix.com Tel +49(234) 610 071-124 Public key on demand Fingerprint 009B 9963 7B28 4356 CA43 5BFD 17A4 AE0F 6943 4B54 This email may contain confidential legal information: if received by not authorised person please advice our firm and destroy it. Anyway every transmitted information shall be treated strictly confidentially.
Well, On Fri, Nov 11, 2005 at 02:31:42PM +0100, Michael Scheibel wrote:
Am Freitag 11 November 2005 12:26 schrieb Christian Helmuth:
Hi,
On Thu, Nov 10, 2005 at 05:19:02PM +0100, Michael Scheibel wrote:
2. Disable the DOpE mouse pointer in the L4Linux console window.
Why do you want to do this? Dope is your (secure) GUI and it should always be able to indicate its focus and the mouse position. What does X11 with the mouse cursor if you write an email?
Well, it's quite difficult to pull down menus because the two mouse pointers do not overlay and the DoPE mouse pointer cannot leave the (active) L4Linux console window.
That changes everything - I thought you were talking about Linux _console_ applications on L4Linux's _console_ :-)
Nonetheless, you could hack dope to not only "grab" the mouse, but also "make it invisible".
Unfortunately this won't solve the problem stated above.
Yes, that's annoying. I always use a combination of "xset m 0 0" and moving the cursor into the upper left corner. We have no better solution so far. An L4Linux and X driver for absolute coordinates would solve this issue but is not as easily available as the current one.
3. Resize the L4Linux console window without just stretching it.
To change this, the L4Linux console stub must be modified. As we only use one stub for l4con (fixed resolution) and dope, we will not implement such a feature. A modified stub would try to adapt to window size changes (hopefully) propagated by dope.
Maybe I am going to take a look in a spare minute. A q&d hack might do the job, don't you think?
Be free to modify dope at will. I suggest to begin with dope/server/common/vscreen.c.
Hm, this seems to be a low latency list - thank you!
Latency will increase the next two days and on next Wednesday ;-) -- Christian Helmuth TU Dresden, Dept. of CS Operating Systems Group http://os.inf.tu-dresden.de/~ch12
participants (4)
-
Adam Lackorzynski -
Christian Helmuth -
Frank Mehnert -
Michael Scheibel