On Sat, Jan 04, 2020 at 12:53:23PM +0900, Bryan Linton wrote: > Hello ports@ > > After upgrading to Firefox 71, I was no longer able to input > Japanese due to the newly-added unveil and pledge support. After > some debugging, I found that adding the following lines to > /etc/firefox/unveil.main allowed me to input Japanese as usual. > > ---------8<---------- > --- /usr/local/lib/firefox/browser/defaults/preferences/unveil.main Sat Dec > 21 15:08:23 2019 > +++ /etc/firefox/unveil.main Fri Jan 3 12:25:53 2020 > @@ -3,6 +3,12 @@ > /dev/video rw > /dev/video0 rw > > +# for launching the anthy input method from uim > +/etc/anthy-conf r > +~/.anthy r > +~/.tomoe r > +~/.uim.d r > + > /etc/fonts r > /etc/machine-id r > ---------8<---------- > > However, this raises some interesting questions. How far down > this path do we want to go? The above patch enables the UIM+Anthy > combination to work again, but what about SCIM+Anthy? Ibus+Anthy? > SCIM+Pinyin? There are 26 ports in ports/inputmethods; do all of > them get added to unveil.main? > > While I'm aware that adding every possible contingency to unveil > largely defeats its purpose, I'm also concerned that the > alternative would be users simply disabling pledge+unveil > entirely if they find that they can no longer input CJK text. > > Which then brings us full circle to the security model of unveil > being defeated...
Let's be practical here. It's already a pain in the ass to figure out how to input non-european scripts into programs. So if you add one more step, people are very likely to just disable unveil. I say we should go for what people actually use AND can test. So, you're using one specific method to input japanese characters. Let's start with adding THAT one. And let's tell people (on this ml, or possibly in the README) to chime in with whatever method they are using. That way, we get a set of unveil that actually gets tested by actual users.
