This project is read-only.

Securing the Service

Apr 21, 2016 at 10:25 AM

I was wondering how may I secure the camera proxy? In my case, accessing the camera proxy through a company network and ensuring the images and authentication information is not captured by the corporate servers.

I have it accessed through http only at the moment. If the proxy can be configured to access through https only, would you mind giving me some pointers how?

Thank you!
Apr 21, 2016 at 10:29 AM
Oops I realised you had the instructions for this in the setup guide already...

Apr 21, 2016 at 2:41 PM
Hi me again.

I noticed that browsers would pop up a warning about obsolete ciphers being used for the SSL connection.
Is there a way I can update the cipher used in the proxy?

Apr 21, 2016 at 2:58 PM
I imagine it can be done with a minor code change. I will look into that.
Apr 21, 2016 at 4:29 PM
Edited Apr 21, 2016 at 4:36 PM
I uploaded a long-overdue update, which has TLS 1.2, 1.1, and 1.0 available (1.0 only remains available because a significant number of Android devices don't support better).

Note it now requires .NET framework 4.5.2.

There are a lot of other changes. Specifically I think the image URLs are different now and web server files go in a different place. It should all be documented in the readme file.
Apr 27, 2016 at 2:39 AM
Thank you so much!

That was an extremely quick response - you're amazing!

Let me try it out tonight
Apr 27, 2016 at 2:54 AM
Just one more question - as I've been worried about possible brute force hacking attempts (e.g. perhaps by nosy corporate IT staff in their spare time), does the proxy generate logs (which I was unable to locate), in particular failed access attempts?

Thank you.
Apr 27, 2016 at 3:33 AM
It does not log anything in this case. Nor does it make any attempt to limit login attempts. Sorry :)