为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

isn't firefox's remote execution capability on linux a security violation?

  • 1 个回答
  • 1 人有此问题
  • 1 次查看
  • 最后回复者为 John99

more options

If I run firefox remotely on a different machine over a secure connection without using the --no-remote option, it starts locally instead.

Also, if I have a secure connection to a remote machine where firefox is running (without --no-remote), and I start firefox locally, the remote instance paints a window on the screen.

How does that work? Are only X facilities used? Which ones? Also, can someone point me to the files in the source version that implement this functionality, and whether there is a compile-time variable to disable it? A related question - if I build my own version according to the mozilla directions, can I expect it to be as fast as the pre-compiled version?


In the first case, take this example:

  $ ssh -fX remote xterm -ls
  $ firefox &

When I start firefox remotely in this configuration, I expect that it asks X to open a window and X sees that the graphic server is remote and paints a window there. Without firefox knowing about it.

I consider it a trojan horse that firefox should look around to determine what my configuration is. This is exactly what I don't want applications to do.

At the very least - i.e. without running a general inventory - it seems that firefox needs to ask if the graphics server is remote or not, and if so, it has to attempt to start an arbitrary executable (but hopefully only firefox) on the server machine.

That that kind of activism doesn't seem like infringement to others is amazing to me.

If I run firefox remotely on a different machine over a secure connection without using the --no-remote option, it starts locally instead. Also, if I have a secure connection to a remote machine where firefox is running (without --no-remote), and I start firefox locally, the remote instance paints a window on the screen. How does that work? Are only X facilities used? Which ones? Also, can someone point me to the files in the source version that implement this functionality, and whether there is a compile-time variable to disable it? A related question - if I build my own version according to the mozilla directions, can I expect it to be as fast as the pre-compiled version? In the first case, take this example: $ ssh -fX remote xterm -ls $ firefox & When I start firefox remotely in this configuration, I expect that it asks X to open a window and X sees that the graphic server is remote and paints a window there. Without firefox knowing about it. I consider it a trojan horse that firefox should look around to determine what my configuration is. This is exactly what I don't want applications to do. At the very least - i.e. without running a general inventory - it seems that firefox needs to ask if the graphics server is remote or not, and if so, it has to attempt to start an arbitrary executable (but hopefully only firefox) on the server machine. That that kind of activism doesn't seem like infringement to others is amazing to me.

所有回复 (1)

more options

It does not look as if anyone on this forum is going to answer. Developers are unlikely to see a post on this forum.

I suggest you either try to find a more suitable forum

where developers may find the post, or even consider filing a bug for this.