look(1): Capsicumise
@oshogbo can you review this?
@kfv Can you also fix the style issues reported by GitHub Actions?
@oshogbo: The style checks are already passing, but I assume you're referring to the warnings for lines exceeding 80 characters. I’ll go ahead and address those as well, sure.
@oshogbo: I applied soft wrapping but kept mmap() on line 162 unwrapped for clarity. I also removed WITHOUT_CAPSICUM by handling ENOSYS as suggested. I’ll just need to go over the code again to address the dynamic stack allocation we discussed.
Sorry, why haven't we used capsicum_helpers here?
@markjdb any final comments?
@markjdb any final comments?
@oshogbo 's comments still apply here: these should just use capsicum helpers (i.e., caph_* routines which handle ENOSYS), and the dynamically allocated stack array is kind of iffy and should be converted to an explicit allocation.
@kfv What are your plans here? This seems to be stuck waiting for addressing the helper feedback comments.
Hi, apologies for the extended delay in addressing the requested changes. The past year has been personally and geopolitically challenging, and I appreciate your patience. I make sure to go through all the pending requests within the coming week at most. Thank you again for your understanding.
I think this is ready for final review. Let me know if I’ve missed anything or if there’s anything else you'd like me to adjust.
What do you think @markjdb and @bsdimp ?