Omero clients connection on port 4064 and data encryption

[xkunes]

Hello,
I have a question about the connection to the server.

If I use the connection port 4064, which should be secured by SSL, is it necessary to use the icon of a lock on the login screen? Will be there a difference in the data encryption.

Or on the other hand if I use the port 4063 and I will use the lock icom, will be there data encrypted?

Thanks

[jmoore]

If I understand correctly, the application will try to force you to make your initial connection (incl. especially the login) to 4064 so that your password is not sent in the clear. The lock then determines whether or not the client (whether web or insight GUI) drops out of SSL for improved performance.

Cheers,
~Josh.

[carandraug]

I found that to be a bit odd. Even though the specified port is 4064, it then actually uses port 4063 (ice-router non encrypted).

I have read on omero documentation about notes on performance as the reason for why. How much of an issue is this really? Are there any measurements done?

[jmoore]

I found that to be a bit odd. Even though the specified port is 4064, it then actually uses port 4063 (ice-router non encrypted).

Correct. Currently the lock icon decides whether or not OMERO.web (acting as a client of OMERO.server) drops from SSL to TCP when communicating. This isn't a user concern and should be removed: https://trello.com/c/sc79fkLw/58-drop-lock-icon-in-web

I have read on omero documentation about notes on performance as the reason for why. How much of an issue is this really? Are there any measurements done?

I don't have any numbers though they should be fairly easy to come up with. I have experienced the slowness (or more specifically the CPU use!) of doing a tight loop over an SSL connection to OMERO. This matches my expectation, so I've likely never taken this further. Happy to have it proven that the SSL overhead is negligible.

Cheers,
~Josh