This report is about large, general-purpose system modules. After the first batch, these are the most likely to write user-sensitive information to their `__crash_info` sections. I worked through everything they might write there, and I didn't find anything that might be user-sensitive. So it looks like Apple is quite careful about what it writes to `__crash_info`. I'll keep my eyes open. If I find problems, I'll open security-sensitive bugs about them. But I doubt I'll find anything. It seems like what I reported above about `/usr/lib/libnetwork.dylib` is very much the exception. Unless something more comes up, I don't plan on writing any more of these reports.
Bug 1709658 Comment 25 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
This report is about large, general-purpose system modules. After the first batch, these are the most likely to write user-sensitive information to their `__crash_info` sections. I worked through everything they might write there, and I didn't find anything that might be user-sensitive. So it looks like Apple is quite careful about what it writes to `__crash_info`. I'll keep my eyes open. If I find problems, I'll open security-sensitive bugs about them. But I doubt I'll find anything. It seems like what I reported above about `/usr/lib/libnetwork.dylib` is very much the exception. Unless something comes up, I don't plan on writing any more of these reports.