From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: "J.P." Newsgroups: gmane.emacs.bugs Subject: bug#53941: 27.2; socks + tor dont work with https Date: Mon, 21 Feb 2022 07:01:58 -0800 Message-ID: <87k0do5km1.fsf@neverwas.me> References: <87pmntfym7.fsf@example.com> <8735kl1v58.fsf@neverwas.me> <87a6emftzx.fsf@example.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="3495"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: 53941@debbugs.gnu.org To: Jacobo Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Feb 21 16:06:12 2022 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 1nMAGR-0000eA-W3 for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 21 Feb 2022 16:06:12 +0100 Original-Received: from localhost ([::1]:58860 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nMAGQ-0002qw-Hx for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 21 Feb 2022 10:06:10 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:39146) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nMADO-0002Il-HT for bug-gnu-emacs@gnu.org; Mon, 21 Feb 2022 10:03:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:44711) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nMADO-0000ni-2a for bug-gnu-emacs@gnu.org; Mon, 21 Feb 2022 10:03:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nMADN-0005rH-Q3 for bug-gnu-emacs@gnu.org; Mon, 21 Feb 2022 10:03:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: "J.P." Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 21 Feb 2022 15:03:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 53941 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 53941-submit@debbugs.gnu.org id=B53941.164545573521313 (code B ref 53941); Mon, 21 Feb 2022 15:03:01 +0000 Original-Received: (at 53941) by debbugs.gnu.org; 21 Feb 2022 15:02:15 +0000 Original-Received: from localhost ([127.0.0.1]:38608 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nMACc-0005XN-KB for submit@debbugs.gnu.org; Mon, 21 Feb 2022 10:02:15 -0500 Original-Received: from mail-108-mta1.mxroute.com ([136.175.108.1]:40489) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nMACa-0005S1-La for 53941@debbugs.gnu.org; Mon, 21 Feb 2022 10:02:13 -0500 Original-Received: from filter006.mxroute.com ([140.82.40.27] 140.82.40.27.vultr.com) (Authenticated sender: mN4UYu2MZsgR) by mail-108-mta1.mxroute.com (ZoneMTA) with ESMTPSA id 17f1ccdc5b20005a20.001 for <53941@debbugs.gnu.org> (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES128-GCM-SHA256); Mon, 21 Feb 2022 15:02:01 +0000 X-Zone-Loop: 2557600d9f6b113017a2a58ac6ba48e0ece56b75b38c X-Originating-IP: [140.82.40.27] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=neverwas.me ; s=x; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date:References: Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=figKuNx6501QgoeDkYL1r+901Iay72/4c65H1ue+nsY=; b=A0zy5VbOV/QnxGnibBrCwcYrc6 LYEzkkTfKwm0OKxoxgyXX4gFwcUXZtbgRhbNlGX8pp0UweNbCY4xpK7NCn7iR43ws7GYF/88EOU28 VKEiEP6PFTfelj2g7d2idQE9pgILIsVu0HAoxQ5GqlKPAexG7idjn4lU1OuIWBynDVaWodVhjQ7ZD e+eKrn0ZPNqyjzZ2rs6r7ovtfVy/nITG8I76hPR3qsEVw5P1xy6S68889v+CTikCEfLPaBDh2QFtd vWnDxO/A/nI5zZufsma7NAU22cBVEQEEpkiGAZW33k3F5VqAiByxyuxfz8azi/m7k7ax6wusyC1Qf VDpQ64Uw==; In-Reply-To: <87a6emftzx.fsf@example.com> (Jacobo's message of "Sat, 19 Feb 2022 22:04:34 +0100") X-AuthUser: masked@neverwas.me X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list 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:227351 Archived-At: Jacobo writes: >> In this day and age, when processes and services resolve host names in >> all manner of ways, how can we be confident there won't be any leaks? > > oh, nevermind I certainly don't want to discourage anyone from trying to solve this. But DNS leaks aside, predicting what ought to be proxied still seems like a serious undertaking (at least from my peabrained perspective). For example, if you connect to an IRC network over Tor and click a hyperlink in a channel, should the resulting connection also happen over Tor? What about when the SOCKS service isn't Tor but something else, like SSH? Should similar follow-on connections also originate from the proxy host (your VPS or shell provider, for example)? >> I also have some examples with shims for 27 running periodically in CI. >> These include a demo of using ERC to connect to Libera.Chat via SOCKS >> over TLS. (But that requires an IRCv3 library, which is still a work in >> progress.) > > Now Ive tryed same in other computer with Trisquel 10, the problem still > happend Sorry, are you saying you repeated the steps in your original post and got the same result (failure) on another computer? If so, that's to be expected because Tor over SOCKS with TLS isn't supported OOTB with any Emacs, not even 29. Apologies if I implied otherwise. >> If you're interested in experimenting with any of this stuff, please >> let me know. That goes for anyone else out there as well. Thanks. > > yes, how can I help? When 28 comes out, you can try applying those patches. Or, if you're not cool with that, I can give you a replacement socks.el to shadow the original. To check whether it's working, do M-: (boundp 'socks--errors-4) RET or similar and then try mimicking the recipe in that last patch (the one named POC demo something). Once that works, try adapting it to your needs for whatever protocol (except for ERC, for which you'll need to install an unofficial WIP version).