You have been subscribed to a public bug by Marc Deslauriers (mdeslaur):
Binary package hint: firestarter
It looks like a minor Firestarter bug to fall into a particular pattern.
First I thought it had something to do with hibernation -- it is not the
case. Firefox and Chrome leave stale entries in Firestarter GUI under
Status tab with Active Connections expanded. Active connections has
stale source|dest|port|service|program entries. This bug apparently
concerns interaction between (any browser except opera so far -- didn't
try it yet) browser and firewall GUI. It occurs after Ethernet cable is
physically disconnected and the browser is still turned on. It can be
easily reproduced and it is user interface (timing) bug.
Netstat seems to report all connections have been closed properly (it could be
trojaned which is very unlikely). Firestarter GUI does not clear network
connections associated with web browsers under Status tab, active network
connections. As a matter fact, only connections to ports 80 and 443 do not
clear after Ethernet cable is plugged in again.
observations:
don't want to reboot but it does not look neat.
the question is if this minor bug has other implications (if it introduces
security vulnerability so i am marking it).
both entries (could be more depending on how many tabs are open) resolve (DNS)
to loadbalanced Google hosts
findings:
No need to reboot! Now the entries have magically disappeared. Most likely
client wanted to restore loadbalanced connections, but they have been torn down
by the loadbalancer. The entries remained there until I have been loadbalanced
back to the same server (Google host) and the entries matched in UI
and...cleared. there are no stale entries and I am speculating here because I
don't have TCPDUMPS or headers and there must be some sort of GUI bug.
** Affects: firestarter (Ubuntu)
Importance: Undecided
Status: New
--
Firestarter GUI: stale entries in Active Connections do not clear properly
https://bugs.edge.launchpad.net/bugs/613678
You received this bug notification because you are a member of Ubuntu Bugs,
which is a direct subscriber.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
