Make secure communication default #46
Conversation
|
In light of zeromq/pyzmq#1148, should we advise Windows users not using an Anaconda Python distribution to set |
|
This will prevent BIAS from talking to zlock at Monash, unless they set Since zlock talks raw strings that it doesn't do much with (a denial of service attack on being politely asked not to open HDF5 files, anyone?) it is not as important to secure as Python programs unpickling arbitrary data sent to them, so I'm going to look into zlock being able to talk to both encrypted and unencrypted clients. Last time I looked into I couldn't figure it out but I'll give it another shot. Otherwise I can: a) write a proxy script that encrypts/decrypts on behalf of a client that doesn't know how to talk crypto, that would work like: b) add an option specifically to disable encryption for zlock |
Yes, I think so. Though I'm going to have a stab at fixing that bug. It'll really slow down image data being sent back to tabs from camera workers, and big dataframes being sent to lyse analysis subprocesses - most communication of all the small stuff we send around will still be fast.. |
Their setup.py is 1366 lines long 😨 |
Actually I think we should advise windows users not on a trusted network to use conda until it's resolved. |
Create a shared secret at profile creation time and add it to labconfig. Raise an error if such an entry is not present, unless allow_insecure is set instead.
chrisjbillington
force-pushed
the
security-default-on
branch
from
71efb17 to
76633d8
Compare
Create a shared secret at profile creation time and add it to
labconfig. Raise an error if such an entry is not present, unless
allow_insecure is set instead.