diff for duplicates of <1530025017.27091.1.camel@intel.com> diff --git a/a/1.txt b/N1/1.txt index 9364922..fe0d951 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -22,3 +22,8 @@ I will look into that. Thanks, Yu-cheng + +-- +To unsubscribe from this list: send the line "unsubscribe linux-doc" in +the body of a message to majordomo@vger.kernel.org +More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/a/content_digest b/N1/content_digest index e8c2542..eaaa3f8 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -49,6 +49,11 @@ "I will look into that.\n" "\n" "Thanks,\n" - Yu-cheng + "Yu-cheng\n" + "\n" + "--\n" + "To unsubscribe from this list: send the line \"unsubscribe linux-doc\" in\n" + "the body of a message to majordomo@vger.kernel.org\n" + More majordomo info at http://vger.kernel.org/majordomo-info.html -bddb4e32fea5c1004edcfeeeacd7d460c9f3df4bc9fa4975b5bb031fc86a3ca1 +6296e67036860d97f88043c389b41abf66fe2d89b2cda342a8adb9b2483acb75
diff --git a/a/1.txt b/N2/1.txt index 9364922..8972a92 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -5,10 +5,10 @@ On Mon, 2018-06-25 at 22:26 -0700, Andy Lutomirski wrote: > > > > This series introduces CET - Shadow stack > I think you should add some mitigation against sigreturn-oriented -> programming. How about creating some special token on the shadow +> programming.A A How about creating some special token on the shadow > stack that indicates the presence of a signal frame at a particular > address when delivering a signal and verifying and popping that token -> in sigreturn? The token could be literally the address of the signal +> in sigreturn?A A The token could be literally the address of the signal > frame, and you could make this unambiguous by failing sigreturn if > CET > is on and the signal frame is in executable memory. diff --git a/a/content_digest b/N2/content_digest index e8c2542..abd5406 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -33,10 +33,10 @@ "> > \n" "> > This series introduces CET - Shadow stack\n" "> I think you should add some mitigation against sigreturn-oriented\n" - "> programming.\302\240\302\240How about creating some special token on the shadow\n" + "> programming.A A How about creating some special token on the shadow\n" "> stack that indicates the presence of a signal frame at a particular\n" "> address when delivering a signal and verifying and popping that token\n" - "> in sigreturn?\302\240\302\240The token could be literally the address of the signal\n" + "> in sigreturn?A A The token could be literally the address of the signal\n" "> frame, and you could make this unambiguous by failing sigreturn if\n" "> CET\n" "> is on and the signal frame is in executable memory.\n" @@ -51,4 +51,4 @@ "Thanks,\n" Yu-cheng -bddb4e32fea5c1004edcfeeeacd7d460c9f3df4bc9fa4975b5bb031fc86a3ca1 +075b22e6a14eac5ce2c95a2f9bad89ac9cd6f4f1afe36d79990467d8bead2d00
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.