Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • H HTTPS Everywhere EFF
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 251
    • Issues 251
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Applications
  • HTTPS Everywhere EFF
  • Issues
  • #1649
Closed
Open
Created Jul 02, 2010 by Georg Koppen@gkDeveloper

Segmentation fault while using HTTPS-Everywhere for Mozilla

Hi,

I get a segmentation fault while surfing to http://mxr.mozilla.org/mozilla1.9.2/ and entering, for instance, "SSL" into the "Search For:" field there and pressing ENTER.

But this occurrs probably only if you have an extension installed that tries to modify the Accept-Header (via setrequestheader). (At least that was how I recognized the problem.)

It turned out that the problem is due to the fact that you forgot to put the code in the replaceURI-function in HTTPSRules.js in a try-catch clause. After having done that, everything worked fine again.

Steps to reproduce:

  1. Put HTTPS-Everyhwere and an extension that modifies the accept-Header (e.g. the JonDoFox extension which you may found here: http://anonymous-proxy-servers.net/en/jondofox/download) in a new profile
  2. Make sure the Mozilla checkbox in the HTTPS-Everywhere preference is checked and surf to http://mxr.mozilla.org/mozilla1.9.2/
  3. There, type "SSL" (or whatever) into the Search For: field and hit ENTER.

Result: Segmentation fault

Reproducible: always, on Linux- as well as on Windows-systems

If you need further information or just want our extension (and not the whole browser profile with a bunch of extensions) for testing purposes, feel free to drop me an email to g.koppen@jondos.de

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking