Re: Network security manager

[Ted Zlatanov]

On Wed, 19 Nov 2014 15:45:52 +0100 Lars Magne Ingebrigtsen <address@hidden> 
wrote: 

LMI> Ted Zlatanov <address@hidden> writes:
>> Would it work to use the logic of "the buffer that initiated the
>> connection is in the foreground"? In that case, we could store the
>> buffer name as an optional record in the process info structure--
>> `open-network-stream' could figure it out mostly automatically?

LMI> Hm...  so shr would tell `url-retrieve' that the buffer that the "user
LMI> buffer" for the request is "*eww*", and then if that's the buffer that's
LMI> active when url.el finally has decided which server to connect to, and
LMI> the NSM decides to query the user -- then NSM would only query the user
LMI> if the user's active buffer is the same buffer?

Yes!

LMI> If you `M-x eww RET http://google.com RET', then we don't create the
LMI> *eww* buffer until we have downloaded the HTML.  (Which will actually be
LMI> from https://www.google.com, since there's a redirect.)  Meanwhile the
LMI> user may well have left the buffer she typed `M-x eww' in, but that
LMI> (probably) shouldn't stop NSM from querying about whether the user
LMI> really wants to visit the version of https://www.google.com that seems
LMI> to be signed by an invalid Chinese CA for some strange reason or
LMI> other...

You could create the *eww* buffer immediately?  Or just look for that
buffer name (if you store just the name in the process)?

At medium or lower `nsm-security-level', I wouldn't expect to be queried
in the case you describe. But at high or above, I would.

Ted