Hi team,
let's assume we have multiple eBlocker solutions/boxes "out in the field" and for minimal user interaction and security update purposes, we set them all to automatic SW update.
How can we make sure that all devices will still run after they autoupdate themselves?
What is the "guarantee" or "confidence" you can provide to achieving a 100% uptime?
Would there be a way to e.g. "delay" the automatic SW deployment in order to allow us SW-HW tests prior to your deployment and then enable our push?
In relation to this, are there any plans to implement a remote management administrator console which would allow us to remotely support devices (obviously with secure user acceptance) or even do a SW update push manually?
Thanks
Danny
How can we make sure that all devices will still run after they autoupdate themselves?
We are doing our best in the team to test that each update runs well - but of course we can not "make sure" that everything and under all circumstances runs well. You are invited to join the team to beta-test ahead of release.
What is the "guarantee" or "confidence" you can provide to achieving a 100% uptime?
We are maintaining a non commercial open source project run by volunteers. The usage of open source software is always "at your own risk" - and of course without any "guarantees".
Would there be a way to e.g. "delay" the automatic SW deployment in order to allow us SW-HW tests prior to your deployment and then enable our push?
I'm not sure where you are heading with your question(s)? Why would you delay an update to "allow us SW-HW tests"? There is a stage system for beta test before release.
After successful beta testing we provide the updates in our in update infrastructure. As soon as the update is out any eBlocker using our infrastructure can pull the update. Of course you can set up your own infrastructure and delay whatever to "your" eBlockers - but this wouldn't make much sense from my perspective unless you want to take over the project...?!
plans to implement a remote management administrator
Nope. Our mission is privacy and therefore "zero knowledge" about our users. We even don't know how many people are using an eBlocker, where they are based or which HW/SW version they run.
Any "remote management" is always a security backdoor that can be abused and therefore bares a risk of privacy infringement. Sorry mate, but I highly doubt anyone finds this a good idea.
Again, I feel your questions are quite "off topic". What is your goal?