Re: The netsec thread

[Andy Moreton]

On Mon 23 Jul 2018, Jimmy Yuen Ho Wong wrote:

> On Mon, Jul 23, 2018 at 2:31 PM, Andy Moreton <address@hidden> wrote:
>> On Mon 23 Jul 2018, Lars Ingebrigtsen wrote:
>>
>>> Eli Zaretskii <address@hidden> writes:
>>>
>>>>> From: Jimmy Yuen Ho Wong <address@hidden>
>>>>> Date: Mon, 23 Jul 2018 02:52:23 +0100
>>>>> Cc: Eli Zaretskii <address@hidden>, Emacs-Devel devel <address@hidden>
>>>>>
>>>>> That sound great, but what is this select-safe-coding-system and how
>>>>> do I look at its UI?
>>>>
>>>> lisp/international/mule-cmds.el, look at
>>>> select-safe-coding-system-interactively, a subroutine of
>>>> select-safe-coding-system.  In a nutshell, it prepares and pops up a
>>>> buffer with special content, then prompts the user to select one of
>>>> several alternatives.
>>>
>>> Hm...  I ran:
>>>
>>> (select-safe-coding-system-interactively 1 3 (find-coding-systems-region 1 
>>> 3) nil)
>>>
>>> and it just popped up a buffer with some text and then called
>>> `read-coding-system', which is kinda close to what the NSM prompt is
>>> doing already.  Only the NSM prompt calls a y-or-n-p-equivalent, so that
>>> you can't enter any other keys then the required ones
>>
>> ... except if you do press a different key, NSM gets stuck and does not
>> accept new valid keys (other than ^G to quit).
>
> That sounds like a lot of trouble just to deal with ^G

You have not understood what I meant: the existing code is buggy. It is
supposed to allow the user to press a limited number of keys to decide
what to do with the presented certificate. however if you press any
other key, the NSM gets stuck and you have to quit with ^G to kill it.

    AndyM