On 9 July 2015 at 11:25, Tomasz Bursztyka <[email protected]> wrote: > Hi Jussi, >> >> Hi, >> >> Now that we're talking about the online check... I've talked to people >> who considered this behaviour "calling home" and thought it >> unreasonable that >> a) it's not possible to prevent the online check from happening via >> configuration and > > > Why would you prevent it to happen? This check is something extra anyway, > being "ready" means you are connected. In a way, people should not care too > much not seeing there service being set to "online", since such check can't > be bullet-proof.
It's not about connman functionality at all. It's (as an example) about people building a super secret embedded product demo on top of Yocto suddenly realizing that their device is connecting to a web server they don't control or even know about (aka "who is this Marcel Holtmann why is our IOT Fridge fetching web pages from him?") FWIW, I totally understand the point Patrik makes in the previous discussion: > If the URL is configurable, upstream > does not have the means to fix online related bug reports as we'd be > unable to confirm the online checking service to work properly in the > first place. In the worst case even the URL accessed is not known, not > even to the person submitting the bug report. This is a compelling argument as well -- I'm not in favor of making this too easy. I do think there are legitimate use cases where people do not want to rely on Marcel (or Intel) handling their online checks. Since the required patches are not big (as shown by Pasi, thanks!) just adding clear documentation to Yocto about the online check Connman makes and instructions on how to modify it may be a sufficient alternative. - Jussi _______________________________________________ connman mailing list [email protected] https://lists.connman.net/mailman/listinfo/connman
