Talk:Sigreturn-oriented programming

Just wondering if the graphic with the caption "Stack content while handling a signal (linux x86/64) including sigcontext structure" has been verified. I notice there are a few differences between the image and some of the data in 'struct sigcontext_64' from http://elixir.free-electrons.com/linux/latest/source/arch/x86/include/uapi/asm/sigcontext.h. Not a big deal, but I just wanted to see if there were any thoughts on this? The image that Dqkk made is really helpful, and I was going to volunteer to help clean it up if I could! Thanks everyone!

Hawkinsw2005 (talk) 06:07, 21 October 2017 (UTC)hawkinsw2005

I don't remember if I double checked that structure. Feel free to verify and fix. Dqkk (talk) 21:34, 21 October 2017 (UTC)

Will do, thanks! Again, I really thought that the graphic was great. I just wanted to verify that I wasn't imagining things! Hawkinsw2005 (talk) 21:17, 23 October 2017 (UTC)hawkinsw2005

RAP relevance
I just read the RAP paper and didn't see anything in it about sigreturn-oriented programming. In fact, as I understand the paper, I don't see how it could be relevant -- the paper talks about constructing the program's flow graph, but signal call and return are outside the statically-analyzed flow graph. A signal return jumps to the instruction to be executed when the signal was received which could be any instruction. -- BT 24 June 2019  — Preceding unsigned comment added by 24.20.150.255 (talk) 14:32, 24 June 2019 (UTC)