I’m not denying the contribution of pax-future.txt, which, as its title indicates, was “future work” at the time. Mentioning “prototype” somewhere doesn’t count as an actual definition of a type-based CFI algorithm. This was my last post on this thread.
1
2
So "magic based off a callee's prototype" being used for the check isn't clearly the basis for type-based CFI to you, got it. What else could it possibly be I wonder? It's too bad you can't be honest/sensible with something as clear as this, no wonder you're not taken seriously.
2
3
You match based on function prototypes for the returns which is a massive over-approximation and, for the majority of applications, not a strong defense. You don't mention anything about the forward edge as it gets more complicated. (But I've told you this before...) 🙃
1
4
Is there a RAP paper/implementation somewhere? I suspect there would be more citations and acknowledgment if RAP was more discoverable to those doing research in the field.
2
7
RAP works, which is more than I can say for a good number of academia papers. There is a public presentation (RAP: RIP ROP) and source. I doubt anyone today can claim to do CFI research and not know about it.
1
3
10
Yeah, the presentation was mentioned a couple of times but it is incredibly sparse and lacks, e.g., target set discussions and other details. Most CFI academics know RAP but it's hard to evaluate/compare without details/specification
2
2
(I have long ago stopped following this -imo useful, if heated - discussion -- but afaik grsec ships RAP? So at least in theory asking would be possible? Apologies for intruding into the thread from the sidelines with dangerous half-knowledge).
1
3
I really didn't want to enter the heated part, was just pointing out that RAP is likely well known at this point in academia :)
1
1
I sincerely doubt it. I myself get a paywall when trying to get the RAP kernel patches. Where is the public version? Its hard to find. If @paxteam wants RAP to become a mainstream academic reference, they should release a PoC code for public evaluation and write a detailed paper.
2
1
your google skills notwithstanding, how does this effort of yours mesh with nitter.vloup.ch/gannimo/status/1… where you said you had already tried (and failed, for unspecified reasons) to evaluate RAP?
Also, we once tried to compare against RAP in a project but ran into compatibility issues and gave up in the end as it was not worth the effort compared to the (stronger?) LLVM-CFI/shadow stack combination.
Dec 21, 2018 · 12:18 AM UTC
1






