Thanks for explaining it, you're absolutely correct. I assume the assumptions came from Saurik's comparison of Cydia Substrate to Xposed, which makes several of such misleading and untrue claims, especially regarding security.
Besides that (and as mentioned in the edit above), I'm working on making only selected methods/fields/classes "public", but the only reason is that there finally was a conflict with an app which did everything right and crash nonetheless. It's basically finished and will very likely be part of the next version.
So does your new work no longer require any of this:
// disable some access checks patchReturnTrue((uintptr_t) &dvmCheckClassAccess); patchReturnTrue((uintptr_t) &dvmCheckFieldAccess); patchReturnTrue((uintptr_t) &dvmInSamePackage); //if (access(XPOSED_DIR "conf/do_not_hook_dvmCheckMethodAccess", F_OK) != 0) patchReturnTrue((uintptr_t) &dvmCheckMethodAccess);
Regarding Cydia, it might be a cleaner/nicer implementation but I wouldn't know, what I do know is that it's not opensource and is less compatible with vendor-modified natives; and Saurik isn't exactly timely in supporting them - so I don't care for it