| From: |
| Eli Zaretskii <eliz-AT-gnu.org> |
| To: |
| Paul Eggert <eggert-AT-cs.ucla.edu> |
| Subject: |
| Re: A couple of questions and concerns about Emacs network security |
| Date: |
| Fri, 06 Jul 2018 20:36:04 +0300 |
| Message-ID: |
| <837em8l117.fsf@gnu.org> |
| Cc: |
| larsi-AT-gnus.org, emacs-devel-AT-gnu.org, wyuenho-AT-gmail.com, rms-AT-gnu.org, perry-AT-piermont.com |
| Archive-link: |
| Article |
> Cc: perry@piermont.com, larsi@gnus.org, wyuenho@gmail.com, rms@gnu.org,
> emacs-devel@gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Fri, 6 Jul 2018 10:03:27 -0700
>
> Eli Zaretskii wrote:
> >> From: Paul Eggert <eggert@cs.ucla.edu>
>
> > Web browsing is a niche application in Emacs, while
> > NSM is about all kinds of network connections, not just those created
> > on behalf of EWW.
>
> Absolutely. Emacs has a more-general security problem than Firefox does.
>
> However, when Emacs is used to browse the web, Firefox is a good model for what
> Emacs's default security should be.
Once again, this discussion is about the NSM, not about EWW. NSM is
used for every net connection, not just those on behalf of EWW. If
you are arguing that NSM should apply different settings to EWW
connections and to the other kind, then this is a separate issue.
