The 10/27/2023 15:55, Edgecombe, Rick P wrote: > Do you have any updated plans to share around your earlier ideas for > token schemes that try to shoot for more compatibility or security? not really. i don't like that shadow stack overflow cannot be handled, so we have to allocate huge shadow stacks to avoid overflow. i had ideas how to handle overflow with sigaltstack, but it is complicated (unwinding, longjmp, swapcontext,..) so "allocate huge shadow stack" is currently our best design. the compatibility issues i see: - dlopen of incompatible lib (multi thread case) - makecontext shadow stack leaks (userspace api issue) - huge shadow stack runs into resource limits - hand crafted stack switching code needs updates - minor issues around sigaltstack + swapcontext i don't have an alternate design that makes these go away. IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
