unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alexandre Garreau <galex-713@galex-713.eu>
To: Tim Cross <theophilusx@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	Emacs developers <emacs-devel@gnu.org>,
	rms@gnu.org, rpluim@gmail.com
Subject: Re: Does service lookup by name work on Windows now?
Date: Sun, 27 Jan 2019 22:08:11 +0100	[thread overview]
Message-ID: <871s4xn70k.fsf@portable.galex-713.eu> (raw)
In-Reply-To: <CAC=50j86A8i53dNnhpQ9xszBRPHV-3DPX8ci334HPH+7c2_ZAQ@mail.gmail.com> (Tim Cross's message of "Sun, 27 Jan 2019 16:11:17 +1100")

[-- Attachment #1: Type: text/plain, Size: 3875 bytes --]

On 2019-01-27 at 16:11, Tim Cross wrote:
> The only problem with continuing to support any OS which is no longer
> maintained is that, in many cases, we are implicitly supporting users on
> platforms with significant and well known exploits. This is especially true
> with Windows XP, which has numerous, well documented and easy to exploit
> vulnerabilities.

If so it’d mean emacs would be supporting Windows at all, so it should
stop supporting it at all, which complies with what previously said.

However emacs is present on Windows to give a (imho, very good) taste of
what free software can be (in one of the best way of showing it), so to
advertise for other operating systems, so it’s not supporting anything
at all but freedom.

> While I would agree that the decision to use a vulnerable OS is up to the
> individual user, in practice, many users don't understand the risks and
> consequences. To make it worse, exploited systems can also be a threat (or
> inconvenience) to other users (for example, by being the source of botnets
> or DDoS attacks).

When a computer is under Windows XP it is often because it’s simply
impossible to switch.  It is then way better to allow most of (free)
software(s) to keep being updated on these, as otherwise it’s simply
that the old versions of these are going to be used instead, increasing
the attack surface.  So this is an argument supporting much more the
reverse: it would harm to make emacs stop supporting XP.

Also a lot of XP computers are ran on special hardware that allegedly
can’t be changed at all without more problem (I’ve heard “nuclear
plants” once, meanwhile I effectively observed XP being consistently
used in nuclear installations, though not active nuclear plants), and
that is consequently kept offline (yes there are offline attacks such as
worms, stuxnet, etc. but that’s also a question of policy).

Also while I regularely see Vista being used by many unaware uncaring
users, I didn’t see XP since a very long time ago except on computers of
more expecienced peoples that *had* the technical knowledge allowing
them to know there is indeed more crap in Vista than XP.  So I believe
the technical level of awareness is better for XP users than Vista users
in the end.

> There is an argument that it would be more responsible to not support any
> OS once it is no longer maintained and receiving patches for security
> vulnerabilities to discourage continued use of vulnerable systems and
> encourage users to update to a current and more secure OS (which of course
> could be GNU Linux!).  This may also make maintenance of Emacs easier as it
> would reduce the need for exceptions and work arounds for older systems
> which don';t support more modern OS practices.

Quirks are to be excepted from everywhere.  Especially from old
not-that-used UNIXes: Windows is much more a case of something
consistent with itself (since it’s completely opaque), and used by many
many many people (so it’s less work to make it compatible with more
environments).

It’s not only the fault of old systems but much more from diversity.
That is something you mostly find in more “open” (lots of commercial
UNIXes), free (all the free distributions), and imho is going to
increase in the future, albeit some other proprietary, highly insecure,
and widely as well as increasingly used non-GNU/Linux systems, such as
Android (which imho is going to be with time way worse than anything XP
could have been).

Btw it’s GNU/Linux, GNU–Linux, GNU-Linux, etc… maybe even “GNU” alone in
some cases …but not “GNU Linux”, since we are talking of the whole
operating system, not some “Linux” (which is a kernel), which would be
from GNU (and there is none, or you are confusing with GNU Linux-libre
maybe).

[-- Attachment #2.1: Type: text/html, Size: 4357 bytes --]

  reply	other threads:[~2019-01-27 21:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-26 11:00 Does service lookup by name work on Windows now? Robert Pluim
2019-01-26 11:56 ` Eli Zaretskii
2019-01-26 12:05   ` Robert Pluim
2019-01-26 12:23     ` Eli Zaretskii
2019-01-26 12:34       ` Robert Pluim
2019-01-26 12:55         ` Eli Zaretskii
2019-01-26 22:46           ` Richard Stallman
2019-01-27  5:11             ` Tim Cross
2019-01-27 21:08               ` Alexandre Garreau [this message]
2019-01-27 23:34               ` Richard Stallman
2019-01-28  3:31                 ` Eli Zaretskii
2019-01-28 11:03                 ` Alexandre Garreau
2019-01-30  3:31                   ` Richard Stallman
2019-01-28 10:12           ` Robert Pluim
2019-01-28 15:44             ` Eli Zaretskii
2019-02-04 13:02               ` Robert Pluim
2019-02-04 16:14                 ` Eli Zaretskii
2019-02-04 16:53                   ` Robert Pluim

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871s4xn70k.fsf@portable.galex-713.eu \
    --to=galex-713@galex-713.eu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    --cc=rpluim@gmail.com \
    --cc=theophilusx@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).