Package: chromium
Version: 76.0.3809.100-1
Native Client (NaCl) appears to be explicitly disabled in the Debian
build of Chromium with the enable_nacl=false option here:
https://salsa.debian.org/chromium-team/chromium/blob/master/debian/rules#L85
FWIW, Ubuntu seems to do the same. This in particular breaks the Secure
Shell app which relies on NaCl. That problem is described in this bug:
https://bugs.chromium.org/p/chromium/issues/detail?id=957708
I was able to trace this flag change back to a combination of this bug
(claiming a licensing issue
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753761) and an earlier
commit
(https://salsa.debian.org/chromium-team/chromium/commit/301651c647badb1a525cc5e3b83655efe5b8f3e7)
which doesn't really explain why the flag was disabled.
There don't appear to be any obvious licensing conflicts (per
https://bugs.chromium.org/p/chromium/issues/detail?id=957708#c15), but I
admit I don't understand how all of these dependencies fit together.
Is it feasible to enable the NaCl flag for the Debian build?
