From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.bugs Subject: bug#39448: 26.1; ERC connect wierdness Date: Thu, 20 Feb 2020 14:34:15 +0100 Message-ID: <878skx5qnc.fsf@gnus.org> References: Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="9187"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: 39448@debbugs.gnu.org To: Corwin Brust Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Feb 20 14:35:14 2020 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1j4lyz-0002Ce-O2 for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 20 Feb 2020 14:35:13 +0100 Original-Received: from localhost ([::1]:42334 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j4lyy-00047O-NS for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 20 Feb 2020 08:35:12 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:33229) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j4lyp-00044q-SS for bug-gnu-emacs@gnu.org; Thu, 20 Feb 2020 08:35:04 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1j4lyo-0001y9-Ql for bug-gnu-emacs@gnu.org; Thu, 20 Feb 2020 08:35:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:38057) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1j4lyo-0001y3-NB for bug-gnu-emacs@gnu.org; Thu, 20 Feb 2020 08:35:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1j4lyo-0006dm-Jg for bug-gnu-emacs@gnu.org; Thu, 20 Feb 2020 08:35:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Lars Ingebrigtsen Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 20 Feb 2020 13:35:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 39448 X-GNU-PR-Package: emacs Original-Received: via spool by 39448-submit@debbugs.gnu.org id=B39448.158220566625466 (code B ref 39448); Thu, 20 Feb 2020 13:35:02 +0000 Original-Received: (at 39448) by debbugs.gnu.org; 20 Feb 2020 13:34:26 +0000 Original-Received: from localhost ([127.0.0.1]:44027 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1j4lyE-0006cf-Bm for submit@debbugs.gnu.org; Thu, 20 Feb 2020 08:34:26 -0500 Original-Received: from quimby.gnus.org ([95.216.78.240]:46966) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1j4lyD-0006cQ-Am for 39448@debbugs.gnu.org; Thu, 20 Feb 2020 08:34:25 -0500 Original-Received: from cm-84.212.202.86.getinternet.no ([84.212.202.86] helo=marnie) by quimby.gnus.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1j4ly3-0003EZ-TC; Thu, 20 Feb 2020 14:34:18 +0100 In-Reply-To: (Corwin Brust's message of "Sat, 8 Feb 2020 13:29:11 -0600") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:176282 Archived-At: Corwin Brust writes: > Once I completely disabled the Comcast security feature, whatever it's called, > ERC connects without difficulty. > > I think this may still be a valid bug, however, as I was able to > connect to Freenode (used for testing in all cases) from rcirc even > while Comcast's anti-productivity software was active. I'm curious > how the two different IRC implementations handle/depend on IDENT. > I'll dig into this if I can and report with such clues or questions as > I find. Whatever "security" software they were using could be using deep packet inspection; i.e., blocking the connection based on the protocol contents of the packets. It does sound rather unlikely that anybody would bother to do that for IRC, but who knows these days... Did you find any further clues? -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no