Thanks for answers. @dan mclaughlin. But how to prevent attacker going out of chroot? Do you think that this is possible to prevent this using pledge(2)?
Thanks for links. Especially Jonathan's "Re: making firefox less insecure" mail dated 2014-11-23 is worth reading for me. I wonder if pledge(2), in theory, can be used to extend his program.