Security/Sandbox/2016-05-05

From MozillaWiki
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

« previous week | index | next week »

aklotz

  • bug 1270018 - NS_APP_CONTENT_PROCESS_TEMP_DIR should only return the sandbox writeable temp - IMHO it's not the directory service part that we should fix here, but rather the deletion part. Comments?
    • Let's create a new infallible directory service key specifically for crash reporter so that we can loosen the coupling. Make NS_APP_CONTENT_PROCESS_TEMP_DIR fallible.

bobowen

  • bug 1035125 - On Windows, plugin-container.exe is linked against the sandbox_s library twice - patches up for review, but there could be a problem with VS2015 (see bug 1265615)
  • bug 1189846 - Print Edit 15.10 - patches up need to find reviewers
  • bug 1255336 - Printing results in empty page with print.always_print_silent=true - regression in release, should be able to print with it disabled and then will work - patch up for review

haik

tedd

  • bug 1176099 - gmain signal handling - landed, caused a lot of crashes (topcrash of the day)
  • bug 1270147 - remote nsIOService::SpeculativeConnect to the parent - one part of the sys_clone problem in bug 1259508

round table

  • bug 1269878 - TB is asking if we can move sandbox config to browser/. I told them to --disable-content-sandbox for the immediate term.
  • bug 1269930 - Crash on windows when logging AEC data from about:webrtc - what should our policy be on file write access in the child for new things?