@flameeyes What FFI?
-
-
Replying to @flameeyes
@flameeyes oh, that. I remember that. grsec/hardened? I need to remind myself of what that was about... It's not Let's Encrypt's fault.1 reply 0 retweets 0 likes -
Replying to @marcan42
@flameeyes something something grsec emutramp kernel pax flags.1 reply 0 retweets 0 likes -
Replying to @flameeyes
@flameeyes let me look up the exact setup once I'm in front of a PC shortly.1 reply 0 retweets 0 likes -
Replying to @flameeyes
@flameeyes you need CONFIG_PAX_MPROTECT_COMPAT=n CONFIG_PAX_EMUTRAMP=y and python2.7 is pax flagged -E--- (PT or XATTR matching kernel)1 reply 0 retweets 0 likes -
Replying to @marcan42
@flameeyes IIRC my problem was MPROTECT_COMPAT=y. https://forums.grsecurity.net/viewtopic.php?f=3&t=4360 …1 reply 0 retweets 1 like
@flameeyes Probably. That kernel option lies. The description even says Python needs it (old versions, sure). It's more like MPROTECT_LIES.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.