Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

Ran "no-remote" instead of "-no-remote" and homepage was hijacked

  • 2 답장
  • 1 이 문제를 만남
  • 10 보기
  • 최종 답변자: kobe

more options

I'm running Firefox 26.0 on Ubuntu. I've been messing with profiles and this morning I ran 'firefox -p "default" no-remote' instead of 'firefox -p "default" -no-remote' When I ran the browser with "no-remote", instead of going to my homepage (reuters) I was redirected through a number of nasty spam pages. I panicked and reinstalled a few things, but on running with "-no-remote" my browser loads fine while running "no-remote" continues to send me to spam pages.

I'm still learning with the terminal, what exactly did I do when I ran the command "no-remote"? Is my browser still safe to use?

I'm running Firefox 26.0 on Ubuntu. I've been messing with profiles and this morning I ran 'firefox -p "default" no-remote' instead of 'firefox -p "default" -no-remote' When I ran the browser with "no-remote", instead of going to my homepage (reuters) I was redirected through a number of nasty spam pages. I panicked and reinstalled a few things, but on running with "-no-remote" my browser loads fine while running "no-remote" continues to send me to spam pages. I'm still learning with the terminal, what exactly did I do when I ran the command "no-remote"? Is my browser still safe to use?

글쓴이 jspet 수정일시

모든 댓글 (2)

more options

You probably have domain fix-up enabled and the keyword service disabled.

When you start Firefox with something that isn't a startup switch and looks like it could be a web address (e.g., intranet), it will go through the standard name resolution process. If the DNS service returns site not found (404) then either Firefox will submit the query to your current search provider (typically Google) or try the text with www before and com after. In this case, your browser must have requested http://www.no-remote.com/ and gotten a redirect from the server to the site you mentioned.

By design, the search function will take priority, but if it is disabled, then domain guessing will happen. These are the preferences to check in about:config:

  • keyword.enabled (defaults to true)
  • browser.fixup.alternate.enabled (defaults to true)

Does that make sense?

more options

Be VERY careful when doing things in the terminal, it gives you a lot of power.