From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Kangas Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] Keep network security info buffers after use Date: Sun, 24 Dec 2023 05:52:48 -0800 Message-ID: References: <87plz4irev.fsf@red-bean.com> <83frzufo9x.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="5750"; mail-complaints-to="usenet@ciao.gmane.io" Cc: kfogel@red-bean.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Dec 24 14:53:46 2023 Return-path: Envelope-to: ged-emacs-devel@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 1rHOvJ-0001K5-Rr for ged-emacs-devel@m.gmane-mx.org; Sun, 24 Dec 2023 14:53:46 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rHOuV-0003kh-WB; Sun, 24 Dec 2023 08:52:56 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rHOuT-0003kP-Id for emacs-devel@gnu.org; Sun, 24 Dec 2023 08:52:53 -0500 Original-Received: from mail-ed1-x532.google.com ([2a00:1450:4864:20::532]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1rHOuS-0002HX-1s; Sun, 24 Dec 2023 08:52:53 -0500 Original-Received: by mail-ed1-x532.google.com with SMTP id 4fb4d7f45d1cf-54c7744a93fso3481710a12.2; Sun, 24 Dec 2023 05:52:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1703425969; x=1704030769; darn=gnu.org; h=content-transfer-encoding:cc:to:subject:message-id:date :mime-version:references:in-reply-to:from:from:to:cc:subject:date :message-id:reply-to; bh=trP2r1LEnGqow0DAdQDLoJkXoTydnK7bQl1WskghPmo=; b=AsP47hZQ8dUuObOBL5wNZ28aVbZ36gtVYxVPKYYMBeuF4T+VW/JzaoTqAxz6kttrLk kbgNQaGOYQF8G4nl66Noc31Tw+Vhnwvg0BrmvCXjq5OD3AhxA7+KrlD0XfM2NW/EJYF+ 9AJyGa/fero3X4sG71g0k3JkOSroD9iPMyS7gmr3+QRJkCREGhlmb+C+QKORe7rtxtOm Y63/d9aYhsXGKkI8QH86gYI6Ty/PaBLeS6GX78JHLDUFIy83GkPV2xKlgYrs1NbnPrdt knF5C6udmsg75rUlkhEW8ydZ2MbD+Isg9FzClM71iO5uRHuL5xKW/RSU6z4bLOxCYDp2 PFbQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1703425969; x=1704030769; h=content-transfer-encoding:cc:to:subject:message-id:date :mime-version:references:in-reply-to:from:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=trP2r1LEnGqow0DAdQDLoJkXoTydnK7bQl1WskghPmo=; b=j2MOJOxZ6D4riMu2gsXRYaSIXNGnK81MgFVvsrOjtYe3vBJZ6Brr4iz5QucgHzaVyy hi2PgmmNVnKjPOm+NW7JbKcioQ6CI9VbfomhoK++zPs+lUSJLpWNXwWSxgqC2d2ixPo+ zkEINwtksyoWMjHkZmgkgkvaF6W7TtTozH7B98p3aC6aBaICVplvWrkICHc3852SQ4S6 nRfpWdvYQolN1GfRn1v8yBCikQjSzK4G37Se2yYY2auYsVrzWHASTBP7Lu2RjMZ2wvN+ zNTQ/UQintVEjKBbv5gJ8X+EeiZS6ux6WhSExR0vbbBviaPPjAviHJYK/Ve6WiFZOojC /xYQ== X-Gm-Message-State: AOJu0Yw6kFtzcres+VyScDrqFW8TpWnaIQAgxlD4nIJRw83yazbzrFKx KBKyjg8jen49XObnhewWyWdZtOlH0ehj6RLc47ZhS/C9PM0= X-Google-Smtp-Source: AGHT+IFc0TSDNGkstH2+qIOQEkOQwY032rywAwNqJ+KwJxAEEPLcf6eEFnIIj16r6i1aTW2GfvznpbFFh3SR0WUBUf4= X-Received: by 2002:a50:99d0:0:b0:554:2905:a51d with SMTP id n16-20020a5099d0000000b005542905a51dmr3556400edb.23.1703425969330; Sun, 24 Dec 2023 05:52:49 -0800 (PST) Original-Received: from 753933720722 named unknown by gmailapi.google.com with HTTPREST; Sun, 24 Dec 2023 05:52:48 -0800 In-Reply-To: <83frzufo9x.fsf@gnu.org> Received-SPF: pass client-ip=2a00:1450:4864:20::532; envelope-from=stefankangas@gmail.com; helo=mail-ed1-x532.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:314124 Archived-At: Eli Zaretskii writes: >> From: Stefan Kangas >> Date: Fri, 22 Dec 2023 02:00:38 -0800 >> >> Karl Fogel writes: >> >> > What do people think of the attached behavior change? >> > >> > Summary: after the user is prompted about whether to accept a >> > remote cert, the buffer(s) with information about the cert should >> > stay around, instead of being killed like they currently are. >> >> It would be useful, yes. I'm not bit by this often, but it happened to >> me this week, and it's pretty frustrating. The only workaround I know >> of is to manually type in the information into some other program. > > I agree that it could be useful in some cases. Andreas suggested a > special command to show this information -- do you think this would be > a good solution for this situation? My use case is that I want to make sure that a certificate is valid before accepting it. This inevitably means some manual inspection. If we have a command that shows the certificate after the fact, IIUC, I would have to abort the current operation, run the command to display the details, and after examination manually retry whatever it is that I was doing. I suppose that's fine, but it could perhaps be more streamlined. Personally, I'd probably prefer entering a recursive edit, inspect it, and hit =C2=B4C-M-c' to go back. But to be honest, I only realized that `recursive-edit' works there from reading this thread. If I didn't realize that, maybe other people won't find it either. Perhaps we could simply do more to make `recursive-edit' discoverable here? For example, we could bind a new key to `recursive-edit' and advertize it. Or we could perhaps even bind `C-x o' to `recursive-edit'. Or something else entirely: we could announce the key binding in the buffer showing the certificate.