From: Robert Pluim <rpluim@gmail.com>
To: Jimmy Yuen Ho Wong <wyuenho@gmail.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
Emacs-Devel devel <emacs-devel@gnu.org>
Subject: Re: The netsec thread
Date: Mon, 23 Jul 2018 10:17:52 +0200 [thread overview]
Message-ID: <8736wamklr.fsf@gmail.com> (raw)
In-Reply-To: <CAKDRQS4Yhk+Lna7biynUfE3tOpEAinROvpRi=8Q_j4Ja+hrLow@mail.gmail.com> (Jimmy Yuen Ho Wong's message of "Mon, 23 Jul 2018 01:12:15 +0100")
Jimmy Yuen Ho Wong <wyuenho@gmail.com> writes:
>> And, as I've said before,
>> `paranoid' should stay.
>>
>
> Eli's use case has already been taken cared of by
> `nsm-trust-local-network`. `paranoid has been aliased to `high for
> backward compatibility.
>
> Robert do you still object to removing the `paranoid level? I've
> removed that prompt that askes for permission on every TLS connection
> due to crying-wolf effect.
As Iʼve said before: I donʼt think many people need to be prompted
every time a TLS connection is set up from emacs to a host thatʼs
never been seen before, but I do, as I need to inspect the connection
parameters. Yes itʼs annoying, but I can live with self-imposed
annoyance.
> If there isn't an objection from people who've found use for it, I'd
> really like to try without 'paranoid on master later before declaring
> it insufficient.
I guess I could always add my own function into 'high, but Iʼd prefer
it if it was available by default.
>>> +(defun nsm-should-check (host)
>>> + "Determines whether NSM should check for TLS problems for HOST.
>>> +
>>> +If `nsm-trust-local-network' is or returns non-nil, and if the
>>> +host address is a localhost address, a machine address, a direct
>>> +link or a private network address, this function returns
>>> +nil. Non-nil otherwise."
>>
>> What do you mean by "machine address"? The MAC address? If you mean
>> IP address, it's perfectly valid to have TLS on a non-named IP
>> address. 1.0.0.1 does that for DNS over HTTPS last I heard, and
>> that's definitely a service you should verify, well, everything on.
>>
Iʼm a bit dubious about the whole 'nsm-trust-local-network' stuff. nsm
already stores per-host settings, so why the need to check for RFC
1918 addresses? Besides, I can easily set things up so that Iʼm using
RFC1918 addresses, but the packets would definitely not be going over
what you'd think of as a 'local' or 'private' network.
Iʼd thought this was going to be something like 'trust this subnet',
which I can see people wanting, although Iʼd recommend against them
using. That would require that nsm-should-check pass the host to the
user-specified nsm-trust-local-network function (or you define a
'nsm-trusted-by-default-networks' variable).
> I mean 0.0.0.0/8. I'm not sure what the proper name is or if I even
> need to deal with it. What do you think?
If you mean localhost, then you have:
(or
;; (0.x.x.x) this machine
(eq (aref address 0) 0)
;; (127.x.x.x) localhost
(eq (aref address 0) 0))
where that second eq should check against 127, I think. I can think of
no situation in which 0.0.0.0/8 would be something you need to check
against (nor can I see how you'd ever see such a value).
Robert
next prev parent reply other threads:[~2018-07-23 8:17 UTC|newest]
Thread overview: 104+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 11:33 The netsec thread Lars Ingebrigtsen
2018-07-20 12:24 ` Eli Zaretskii
2018-07-20 12:33 ` Lars Ingebrigtsen
2018-07-20 12:36 ` Lars Ingebrigtsen
2018-07-20 12:41 ` Eli Zaretskii
2018-07-20 12:45 ` Lars Ingebrigtsen
2018-07-23 1:52 ` Jimmy Yuen Ho Wong
2018-07-23 1:55 ` Brett Gilio
2018-07-23 2:32 ` Eli Zaretskii
2018-07-23 12:46 ` Lars Ingebrigtsen
2018-07-23 13:31 ` Andy Moreton
2018-07-23 14:43 ` Jimmy Yuen Ho Wong
2018-07-23 14:46 ` Andy Moreton
2018-07-23 15:48 ` Lars Ingebrigtsen
2018-07-23 16:54 ` Andy Moreton
2018-07-23 19:34 ` Andy Moreton
2018-07-24 8:24 ` Lars Ingebrigtsen
2018-07-24 9:34 ` Andy Moreton
2018-07-24 11:54 ` Andy Moreton
2018-07-24 12:09 ` Noam Postavsky
2018-07-24 13:59 ` Jimmy Yuen Ho Wong
2018-07-24 14:11 ` Lars Ingebrigtsen
2018-07-24 18:21 ` Andy Moreton
2019-07-28 18:18 ` Lars Ingebrigtsen
2019-07-28 18:27 ` Eli Zaretskii
2019-07-28 18:33 ` Lars Ingebrigtsen
2019-07-28 18:34 ` Lars Ingebrigtsen
2019-07-28 19:08 ` Lars Ingebrigtsen
2019-07-28 19:12 ` Eli Zaretskii
2019-07-29 11:12 ` Lars Ingebrigtsen
2019-07-29 7:50 ` Robert Pluim
2019-07-29 8:11 ` Robert Pluim
2019-07-29 11:18 ` Lars Ingebrigtsen
2019-07-29 11:14 ` Lars Ingebrigtsen
2019-07-29 14:02 ` Robert Pluim
2019-07-30 11:30 ` Lars Ingebrigtsen
2019-07-30 13:12 ` Robert Pluim
2019-07-30 13:32 ` Lars Ingebrigtsen
2019-07-30 15:05 ` Robert Pluim
2019-08-07 12:27 ` Robert Pluim
2019-08-07 18:41 ` Lars Ingebrigtsen
2019-08-23 2:58 ` Lars Ingebrigtsen
2019-08-23 8:19 ` Paul Eggert
2019-08-23 8:52 ` Lars Ingebrigtsen
2019-08-23 9:01 ` Lars Ingebrigtsen
2019-08-23 19:03 ` Paul Eggert
2019-08-25 5:33 ` Lars Ingebrigtsen
2019-09-03 9:49 ` Robert Pluim
2019-09-03 13:30 ` Paul Eggert
2019-09-03 15:37 ` Robert Pluim
2019-09-03 19:20 ` Paul Eggert
2019-09-03 20:02 ` Robert Pluim
2019-09-04 13:12 ` Lars Ingebrigtsen
2019-09-04 19:34 ` Robert Pluim
2019-09-04 21:35 ` Paul Eggert
2019-09-04 21:54 ` Robert Pluim
2019-09-05 12:12 ` Robert Pluim
2019-09-05 18:50 ` Paul Eggert
2019-09-05 19:34 ` Robert Pluim
2019-09-04 13:10 ` Lars Ingebrigtsen
2019-08-23 9:09 ` Eli Zaretskii
2019-08-23 9:40 ` Robert Pluim
2019-08-23 12:18 ` Eli Zaretskii
2019-08-23 12:39 ` Robert Pluim
2019-08-23 13:03 ` Eli Zaretskii
2019-08-23 13:20 ` Robert Pluim
2019-08-23 14:15 ` Eli Zaretskii
2019-08-23 14:27 ` Robert Pluim
2019-08-23 14:40 ` Eli Zaretskii
2019-08-23 14:58 ` Robert Pluim
2019-08-23 15:04 ` Eli Zaretskii
2019-08-23 9:58 ` Lars Ingebrigtsen
2019-08-23 12:43 ` Eli Zaretskii
2019-08-25 5:32 ` Lars Ingebrigtsen
2019-08-25 22:29 ` Richard Stallman
2019-08-26 4:16 ` Lars Ingebrigtsen
2018-07-23 15:22 ` Eli Zaretskii
2018-07-22 14:48 ` Lars Ingebrigtsen
2018-07-23 0:12 ` Jimmy Yuen Ho Wong
2018-07-23 8:17 ` Robert Pluim [this message]
2018-07-23 14:58 ` Jimmy Yuen Ho Wong
2018-07-23 15:06 ` Robert Pluim
2018-07-23 15:37 ` Lars Ingebrigtsen
2018-07-23 15:51 ` Jimmy Yuen Ho Wong
2018-07-23 16:06 ` Noam Postavsky
2018-07-23 16:11 ` Lars Ingebrigtsen
2018-07-23 15:04 ` Eli Zaretskii
2018-07-23 15:24 ` Jimmy Yuen Ho Wong
2018-07-23 15:34 ` Robert Pluim
2018-07-23 16:38 ` Jimmy Yuen Ho Wong
2018-07-23 17:25 ` Robert Pluim
2018-07-23 17:54 ` Eli Zaretskii
2018-07-23 20:51 ` Robert Pluim
2018-07-23 9:55 ` Lars Ingebrigtsen
2018-07-23 15:22 ` Jimmy Yuen Ho Wong
2018-07-23 15:46 ` Lars Ingebrigtsen
2018-07-23 15:48 ` Jimmy Yuen Ho Wong
2018-07-23 15:49 ` Noam Postavsky
2018-07-23 16:13 ` Lars Ingebrigtsen
2018-07-23 10:23 ` Andreas Schwab
2018-07-20 12:55 ` Jimmy Yuen Ho Wong
2018-07-20 12:59 ` Jimmy Yuen Ho Wong
2018-07-20 13:00 ` Lars Ingebrigtsen
2018-07-20 13:11 ` Jimmy Yuen Ho Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8736wamklr.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=wyuenho@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.