Question

Here is what I would like to do, and I want to know how some people with experience in this field do this:

With three POST requests I get from the http server:

1. widgets and layout
2. and then app logic (minimal)
3. data

Or maybe it’s better to combine the first two or all three. I’m thinking of using pyqt. I think I can load .ui files. I can parse json data. I just think it would be rather dangerous to pass code over a network to be executed on the client. If someone can hijack the connection, or can change the apps setting to access a bogus server, that is nasty.

I want to do it this way because it keeps all the clients up-to-date. It’s sort of like a webapp but simpler because of Qt. Essentially the “thin” app is just a minimal compiled python file that loads data from a server.

How can I do this without introducing security issues on the client? Is https good enough? Is there a way to get pyqt to run in a sandbox of sorts?

PS. I’m not stuck on Qt or python. I do like the concept though. I don’t really want to use Java – server or client side.

Answer 1

Your desire to send “app logic” from the server to the client without sending “code” is inherently self-contradictory, though you may not realize that yet — even if the “logic” you’re sending is in some simplified ad-hoc “language” (which you don’t even think of as a language;-), to all intents and purposes your Python code will be interpreting that language and thereby execute that code. You may “sandbox” things to some extent, but in the end, that’s what you’re doing.

To avoid hijackings and other tricks, instead, use HTTPS and validate the server’s cert in your client: that will protect you from all the problems you’re worrying about (if somebody can edit the app enough to defeat the HTTPS cert validation, they can edit it enough to make it run whatever code they want, without any need to send that code from a server;-).

Once you’re using https, having the server send Python modules (in source form if you need to support multiple Python versions on the clients, else bytecode is fine) and the client thereby save them to disk and import / reload them, will be just fine. You’ll basically be doing a variant of the classic “plugins architecture” where the “plugins” are in fact being sent from the server (instead of being found on disk in a given location).