netdev - Fw: [Bug 202287] New: netfilter/iptales prevents Tor Browser from closing cleanly

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 15 Jan 2019 11:27:32 -0800
From:   Stephen Hemminger <stephen@...workplumber.org>
To:     netdev@...r.kernel.org
Subject: Fw: [Bug 202287] New: netfilter/iptales prevents Tor Browser from
 closing cleanly



Begin forwarded message:

Date: Tue, 15 Jan 2019 16:18:13 +0000
From: bugzilla-daemon@...zilla.kernel.org
To: stephen@...workplumber.org
Subject: [Bug 202287] New: netfilter/iptales prevents Tor Browser from closing cleanly


https://bugzilla.kernel.org/show_bug.cgi?id=202287

            Bug ID: 202287
           Summary: netfilter/iptales prevents Tor Browser from closing
                    cleanly
           Product: Networking
           Version: 2.5
    Kernel Version: 4.20
          Hardware: Intel
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: IPV4
          Assignee: stephen@...workplumber.org
          Reporter: jb.1234abcd@...il.com
        Regression: No

Created attachment 280501
  --> https://bugzilla.kernel.org/attachment.cgi?id=280501&action=edit  
Tpr Browser and kernels run log

Since kernel 4.20 there is a problem with Tor Browser (TB) on close.
The last good kernel was 4.19.12 .

Tested:
kernel 4.20.1 and 4.19.12 .
Tor Browser 8.0.4 (prod version).

Tor Browser (TB) and kernel run logs (as attached):
tor-netfilter-4.20.1-and-4.19.12.txt

kernel 4.20.1
Results:
There is a problem with TB on close:
- TB process left behind
- INVALID messages (ACK FIN and ACK PSH FIN) cought in OUTPUT chain of
iptables,
  on lo interface, and logged to system log/journal.
  -A OUTPUT -m conntrack --ctstate INVALID -j loginv

kernel 4.19.12
Results:
There is no problem with TB, i.e. clean close.

There is an old reference to this problem
https://www.linode.com/community/questions/2495/iptables-drop-ackfin-as-invalid

-- 
You are receiving this mail because:
You are the assignee for the bug.