From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jacobo Newsgroups: gmane.emacs.bugs Subject: bug#53941: 27.2; socks + tor dont work with https Date: Sat, 19 Feb 2022 22:04:34 +0100 Message-ID: <87a6emftzx.fsf@example.com> References: <87pmntfym7.fsf@example.com> <8735kl1v58.fsf@neverwas.me> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="31567"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 53941@debbugs.gnu.org To: "J.P." Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Feb 19 22:05:34 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 1nLWv8-0007ym-00 for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 19 Feb 2022 22:05:34 +0100 Original-Received: from localhost ([::1]:60172 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nLWv6-0006r6-7g for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 19 Feb 2022 16:05:32 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:53690) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nLWuc-0006p4-S0 for bug-gnu-emacs@gnu.org; Sat, 19 Feb 2022 16:05:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:36689) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nLWuc-0000j1-Ho for bug-gnu-emacs@gnu.org; Sat, 19 Feb 2022 16:05:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nLWuc-0000Lb-EB for bug-gnu-emacs@gnu.org; Sat, 19 Feb 2022 16:05:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Jacobo Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 19 Feb 2022 21:05:02 +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.16453046841283 (code B ref 53941); Sat, 19 Feb 2022 21:05:02 +0000 Original-Received: (at 53941) by debbugs.gnu.org; 19 Feb 2022 21:04:44 +0000 Original-Received: from localhost ([127.0.0.1]:58813 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nLWuJ-0000Kd-UO for submit@debbugs.gnu.org; Sat, 19 Feb 2022 16:04:44 -0500 Original-Received: from mx1.riseup.net ([198.252.153.129]:44756) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nLWuI-0000KO-E7 for 53941@debbugs.gnu.org; Sat, 19 Feb 2022 16:04:43 -0500 Original-Received: from fews1.riseup.net (fews1-pn.riseup.net [10.0.1.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.riseup.net", Issuer "R3" (not verified)) by mx1.riseup.net (Postfix) with ESMTPS id 4K1LfX4FSwzF44M; Sat, 19 Feb 2022 13:04:36 -0800 (PST) X-Riseup-User-ID: C84BA236F5101290351971B5CC63B5D706A0B5CABE282B6EA335C44739BD944D Original-Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews1.riseup.net (Postfix) with ESMTPSA id 4K1LfW5r9pz5vMd; Sat, 19 Feb 2022 13:04:35 -0800 (PST) In-Reply-To: <8735kl1v58.fsf@neverwas.me> (J. P.'s message of "Mon, 14 Feb 2022 04:37:39 -0800") 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:227206 Archived-At: "J.P." writes: > Jacobo writes: >> Emacs can not resolve domains when it is https if you are using a >> socks proxy (socks.el) [...] It works, load http://gnu.org (HTTP in >> plain) Also work with .onion domains in HTTP plain No problems with >> HTTP but When I try: M-x eww RET https://gnu.org RET >> Return an error: Bad Request > It's certainly possible (see attached). But can it be done responsibly? > 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 > At present, the main interfaces to various protocol stacks (for > example, url-gw.el and friends) don't seem geared toward making those > kinds of assurances. (Not that they ought to be.) That said, > providing the building blocks on the SOCKS side doesn't seem like the > crime of the century. I've been sitting on what became the basis for > these patches for a while now, but these here were hastily adapted and > might come with some warts. Still, I believe them straightforward > enough to illustrate a basic means of achieving what you're after. >> In GNU Emacs 27.2 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.30, > 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 > 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? -- Emacs Lover. FSF Member. Free/Libre Software supporter. stallmansupport.org - Disinformation succeeds because so many people care deeply about injustice but do not take the time to check the facts.