I'm interested in setting up dynamic dns with an elk panel doing the work, using changeip.com.
I'd like to do this with my changeip user name and password encrypted, not in the clear... but it isn't clear to me that the Elk can do this. But before I give up on it, and put some other (not otherwise necessary) device on the network to take care of running a secure changeip update client. I'd rather not go that route, because that is another point of failure and that already bit me: I'm looking into this because in the past I had a webcam and relied on it, but then after an ISP IP change the camera died and I could not RP to my still-working alarm till I could physically visit it and figured out the new IP!
On the changeip FAQ at http://www.changeip.com/clients.asp they describe various URLS that will work, such as
https://nic.ChangeIP...e=my.domain.com
which would let changeip automatically detect your IP, and then they change the address DNS serves up for "my.domain.com". They highly recommend using "https" and not "http" so that your user name and password get encrypted (not just base64 scrambled, but really encrypted). But they are talking about doing this from a web browser, which always shows either http or https in the URL bar, and is clearly capable of doing the encryption.
Looking at the M1XEP doc, the example says it works with changeip. In the first box, I think it wants just an IP address, or a fully qualified name like "nic.ChangeIP.com". Then it wants user + password in the next two, and finally it just wants "my.domain.com" in the last box. So M1XEP doesn't want to use that specially constructed URL thing at all.
Am I correct that this means the M1XEP can't encrypt the user name/password, so if that bugs me, I have to put some other device on my LAN to run a more secure change IP client?
Thanks.
I'd like to do this with my changeip user name and password encrypted, not in the clear... but it isn't clear to me that the Elk can do this. But before I give up on it, and put some other (not otherwise necessary) device on the network to take care of running a secure changeip update client. I'd rather not go that route, because that is another point of failure and that already bit me: I'm looking into this because in the past I had a webcam and relied on it, but then after an ISP IP change the camera died and I could not RP to my still-working alarm till I could physically visit it and figured out the new IP!
On the changeip FAQ at http://www.changeip.com/clients.asp they describe various URLS that will work, such as
https://nic.ChangeIP...e=my.domain.com
which would let changeip automatically detect your IP, and then they change the address DNS serves up for "my.domain.com". They highly recommend using "https" and not "http" so that your user name and password get encrypted (not just base64 scrambled, but really encrypted). But they are talking about doing this from a web browser, which always shows either http or https in the URL bar, and is clearly capable of doing the encryption.
Looking at the M1XEP doc, the example says it works with changeip. In the first box, I think it wants just an IP address, or a fully qualified name like "nic.ChangeIP.com". Then it wants user + password in the next two, and finally it just wants "my.domain.com" in the last box. So M1XEP doesn't want to use that specially constructed URL thing at all.
Am I correct that this means the M1XEP can't encrypt the user name/password, so if that bugs me, I have to put some other device on my LAN to run a more secure change IP client?
Thanks.
