Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Convergence FF 0.3 Plugin not disabled when disabled? #52

Closed
Lcstyle opened this issue Sep 7, 2011 · 1 comment
Closed

Convergence FF 0.3 Plugin not disabled when disabled? #52

Lcstyle opened this issue Sep 7, 2011 · 1 comment

Comments

@Lcstyle
Copy link

Lcstyle commented Sep 7, 2011

Clicking the convergence icon to disable convergence enables default browser certificate verification. However, it does not prevent Convergence from proxying requests.

I observed this behavior because I am running a notary, and noticed that URL's I needed to access were popping up in my convergence notary log. The problem of course is that when convergence is disabled, it should be completely disabled. It shouldn't require you to disable it via the extensions control panel and then restart firefox.

The other problem is that bugs in the convergence proxy can interfere with requests, and it is in fact interfering with requests. File transfers to google apps fail. See my other Issue, #46. In that issue, gmail file attachment transfers are not working. Clicking the convergence icon to disable it is enough to workaround the problem.

However in the new behaviour I am observing with Google Doc's, downloading of documents is broken, even by disabling convergence by clicking the convergence Icon. In order to work around this issue, you have to disable it completely via the extensions control panel and restart FF.

So three things:

  1. Convergence should be completely disabled from making any kind of requests when the icon says it is disabled without having to be disabled in the extension control panel and restarting firefox.
  2. Convergence MITM proxying is broken for file transfers to various google applications. Possibly due to Serialization or some other Twisted Network library issue (not sure).
  3. might be related, observe the behavior across browser windows, in one, Convergence is enabled, in the other, disabled. If Convergence can't keep track of its own state across windows, then it should function appropriately for each window in which it is open.

Screenshot of Behavior Here:
http://www.dumpt.com/img/viewer.php?file=o67wit8f9hcw3pv2c0c0.jpg

I can provide log data and other items necessary for successful reproduction, ask and you shall receive.

@Lcstyle Lcstyle closed this as completed Sep 7, 2011
@Lcstyle Lcstyle reopened this Sep 7, 2011
@moxie0
Copy link
Owner

moxie0 commented Oct 13, 2011

I can't reproduce this. Toggling the convergence icon disables the nsiproxy interface, so no new traffic should be proxied through Convergence. It could be possible that existing sockets are lingering, but no new requests should be transmitted. It's also possible that the browser is caching the internal proxy settings, in which case there's nothing we can do.

@moxie0 moxie0 closed this as completed Nov 4, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants