On 6/17/19 4:29 AM, Carlos E. R. wrote:
On 17/06/2019 00.28, Dave Howorth wrote:
On Sun, 16 Jun 2019 22:41:08 +0200 "Carlos E. R." <> wrote:
On 16/06/2019 21.08, Dave Howorth wrote:
On Sun, 16 Jun 2019 13:18:08 -0500 Stevens <> wrote:
These days when I look at reviews of consumer products in this area, they all seem to concentrate on the apps and the cloud storage, neither of which I need or want. Indeed stopping IoT devices from phoning home is something I'm trying to learn about. If you know of any good products that include proprietary algorithms, I'm open to ideas.
The only IoT gadget I own doesn't phone home till it gets an account. Ie, till I register it. Which means, the phone applet can not connect to it without registration. But there is no problem controlling it with a computer inside the LAN, which is perferct.
Well that's a nice well-behaved IoT-bot then. But how can you know that in advance (if you don't trust the supplier) or deal with devices that are known to phone home?
It is mostly an educated guess on my part: their server can not store the data my gadget may send because it doesn't know where to store it, without an account name (well, they might use a serial number, but they wouldn't know the person, only approximate location). I think they mention this on the instructions. And of course, there is no way for an application on the phone to contact my gadget (and only my gadget) till it knows the account outside to contact.
This is true for any gadget that says can be controlled from anywhere, inside or outside the house. Maybe with IPv6 the need for an external intermediate server could be obviated.
It needs careful reading of the specifications before purchase to know if the gadget can be controlled from the LAN only without outside intervention.
The Google Chromecast device bypasses some of this, using identification via bluetooth, I think. But it does need to know the account, later.
The NVR systems that I deal with aren't usually consumer grade - or priced - and although many use some form of DDNS and offsite (and off shore?) servers, others do not. One I installed recently allowed the programming of specific phone numbers so it could call and/or text alert messages. The LAN also can be configured with port forwarding with the dedicated port numbers for remote viewing. Using the DDNS server also lets you skip over the LAN configuration in case the client is overly paranoid (and ignorant) about remote access. As far as proprietary algorithms are concerned, most systems have those embedded in the NVR OS and each manufacturer has their own take on what is important. They are all in China and all are market driven (odd for a communist gov't to be controlling such a thriving capitalist system) so what is included now may not be around tomorrow. (A side note about China, Inc. - I smile when thinking about how difficult it must be for central planners to control a system where the citizenry sees the gov't as just another cost of doing business in one of the most cutthroat market economies on the planet. Oh, yeah - off topic so don't reply on list!) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org