Replying to
@opa334@infosec.exchange Ah okay, that makes more sense now.
Remote
etas0n
@etas0n@ioc.exchange
mastodon 4.8.0-alpha.3+glitch0 Followers
0 Following
9 Posts
Joined March 13, 2026
Replying to
@opa334 @github@infosec.exchange @GitHub@mstdn.social @github@hachyderm.io @githubprojects so from now how could we see WIP ?
PAC used in 2024 seems like working on coruna 😍
@Arthurhsg@mastodon.social @Renero@infosec.exchange @opa334@infosec.exchange // escalate to policy layer via OPA hook
id target = objc_getAssociatedObject(self, @selector(currentAnnoyingActor));
if (target && ((BOOL (*)(id, SEL))objc_msgSend)(target, sel_registerName("isPersistentlyNoisy"))) {
void *opa_ctx = dlsym(RTLD_DEFAULT, "opa_eval_ctx_acquire");
((void (*)(void *, id))dlsym(RTLD_DEFAULT, "opa_enforce_block"))(opa_ctx, target);
((void (*)(id, SEL))objc_msgSend)(target, sel_registerName("invalidateSession"));
}
😘 Opa continuing to be the hero we definitely do not deserve, but the hero we need…@opa334@infosec.exchange
Replying to
@Renero@infosec.exchange @opa334@infosec.exchange Keep iterating on it and share it once it’s in a usable state
Replying to
@opa334@infosec.exchange do you think iPhone 17 models will be compatible due to new memory integrity enforcement ? Even if we get PPL/SPTM bypasses
Replying to
@opa334@infosec.exchange When you say support for iOS 17.0–18.7.1 (arm64), do you literally mean arm64-only devices, or does this also include arm64e devices like A12+ ?
I’m asking because A12+ is arm64e hardware, so the wording confused me a bit.