Re: [PATCH] Keep network security info buffers after use

[Stefan Kangas <stefankangas@gmail.com>]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Stefan Kangas <stefankangas@gmail.com>
>> Date: Fri, 22 Dec 2023 02:00:38 -0800
>>
>> Karl Fogel <kfogel@red-bean.com> 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 ´C-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.