On Fri, Nov 12, 2010 at 1:27 PM, Niels Mayer <nielsma...@gmail.com> wrote: > network: e.g. > http://xizhizhu.blogspot.com/2010/08/basic-samples-for-ssl-communication.html
Correction: the appropriate technology to use for SSH support in Qt is QCA via hybrid C++/QML: http://delta.affinix.com/qca/ http://delta.affinix.com/docs/qca/sslservtest_8cpp-example.html One more thing. Many times media capture/conversion/output may require special access to hardware devices etc, or running with special privileges, priorities, or permissions. By using the "restricted SSH shell" to actually run the subprocesses, a separate account could be setup with the different privilege needed to access media hardware; the rest of the GUI program can run with standard "user" privileges. Ultimately, this can lead to a better security/performance architecture where http://en.wikipedia.org/wiki/Separation_of_concerns can be used to grant special access for specific subcomponents of the application. For example, the special "user" created to run the subprocesses can be granted specific nice, rtprio, or memlock priviledges in /etc/security/limits.conf which shouldn't be available to the main GUI program invoking the components. Furthermore, since separate programs are invoked in the subprocess, these can be individually setup to run with specific group id's, and their associated media devices allowing read/write/lock only from only specific gids. This is already done with groups like pulse, pulse-rt, pulse-access, audio, video, setup to designate these different acceses for media. Niels http://nielsmayer.com _______________________________________________ Qt-qml mailing list Qt-qml@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-qml
