Hello Micheal,
I have thought a bit about Genode chat clients, and I think the first concern is to seperate the crypto that protects a conversation from the GUI. If the critical code is isolated in a non-graphical component and a graphical frontend can interact with this core using something like a file system, then isolation of conversation GUIs should not be much of a concern.
Running Nitpicker recursively is possible and practical in some cases, but it may actually weaken isolation as in the recursive case you would have multiple clients drawing to a common session, whereas in flat Nitpicker each client enjoys equal privacy.
I don't want to discourage you though, a Qt chat client would be great. I got as far as porting the Tox library and implementing a very simple terminal interface, but I don't think I will have the chance to work on a Qt frontend in the near future.
Cheers, Emery
On Sat, Jun 25, 2016 at 07:33:50PM +0200, Michael Ullrich wrote:
Hallo,
I'm currently trying to modularize a Qt-based ChatClient. The basic idea is to isolate the parts of some guy-components from each other. I want to use Nitpicker for this. In generally the Client itself should run in a trusted nitpicker session. Now I want to start another nitpicker-sessions inside the quote-client. Meaning by that, I want for example a trusted input-field or a trusted label, isolated from the remaining qt-app. So isolate several graphical components from each other. Is it in generally a good idea, to use nitpicker in that way? Has someone tried something similar, or is there an reference implementation for that?
With kind regards,
Michael Ullrich