ImHereToCrash
First Officer
Flight distance : 5381368 ft
United States
Offline
|
forced updates tend to mean something important is found and patched. like with game consoles, not every single update is mandatory and not every update you will even see popup as availble unless you manually check.. its only important updates that patch a vulnerability/exploit or add a new feature set and upset frameworks that are typically seen by most people.
its actually irresponsible from developer stand point to want to push all updates as mandatory. why you may ask, well what if there is a ticking time bomb in the code, everything is fixed up, etc etc but some minor issue in the code that triggers bigger issues later on, it may work for a couple of weeks, but something unseen could cause issues. then have issues with mandatory updates being enforced makes rolling back extremely difficult without first revealing to modders exact how they plan on dealing with that. if it is enforced via server verification only, then DJi has already lost the battle acount FW mods since intercepting and changing expected response is too easy or using saved blobs/signatures/activation scripts again too easy. and if DJi ever has to issue rollback of FW, well RIP secuirty, just basically gave modders the keys to the backdoor.
long story short, i half agree with enforced updates. they are good when well implemented, not all updates are enforced, and they use a branch method of signing updates can make them exceptionally strong but incredibly complicated to manage, specially if they have hands tied behind their backs with a bad update. but they are bad as well since the force everyone to update to unproven firmware, some people have found safe grounds on older updates where newer updates cause problems or they risk issues..
bigger issue is the fact that now to enforce updates and deadline, the app and aircraft are now forced to sync with server every so often.. this basically goes against the DJi offline update
|
|