|
Although this may be a very elegant solution but in most of the cases it would be an overkill. Most apps. are designed to tackle the situation where the internet conection may be down or non existant. They usually provide an alternative registering scheme where by you call by phone and type in the reg. info.
Only in the case of apps. which require verification from an internet host before accepting reg. info or doing anything usefull this method would be needed. But implementing this would require either sniffing an actual (real) conversation between the app. and its server or extensive reverse engineering of the app. code to unravel the expected server response. Added to this is the fact that each app. would employ different app. to server interaction scheme/protocol. All this will make this approach rather tedious to implement for all the different apps.
I think that more and more apps will go this "live internet server verification" route in the future but I feel that this can be tackled by turning off (patching) such checks instead of providiing elaborate fake server emulations. As long as the app. contains all the needed functionality code we can fix it to work without the server checks. Also, if it downloads functionality code from the server then we need to snoop just once to snag the needed code and patch it in permanently.
I hope the experts here might shed more light on it.
|