unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Ian Grant <ian.a.n.grant@googlemail.com>
Cc: guile-devel@gnu.org, deraadt@theos.com, Markus.Kuhn@cl.cam.ac.uk,
	torvalds@osdl.org, lightning@gnu.org, schellr@ieee.org
Subject: Re: Reinterpreting the compiler source code
Date: Thu, 04 Sep 2014 21:51:28 -0400	[thread overview]
Message-ID: <E1XPigS-000528-41@fencepost.gnu.org> (raw)
In-Reply-To: <CAKFjmdx4Zm2_HVEUre-PYvcZrm41gKv-2z_EsGehjv6NbVxBAw@mail.gmail.com> (message from Ian Grant on Thu, 4 Sep 2014 13:33:38 -0400)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

I don't know prolog, and even if I did, reading so much code would
take a lot of time.  I don't see a point, because all that example can
prove is that some subtle of sabotage is _possible_.  I'd rather just
agree that it is possible.  (I already did.)

I think our community's distributed build practices would make it
difficult for such a sabotage to hit the whole community.  Many GCC
developers and redistributors have been bootstrapping for decades
using their old versions.

However, this suggests to me a way of investigating whether such
sabotage is present in our tools.  It would be much less work than
replacing the system with new "simple" software, but it would be
a substantial job.  I think it would need funding.  I don't know
how to get such funding, but maybe someone else does.

-- 
Dr Richard Stallman
President, Free Software Foundation
51 Franklin St
Boston MA 02110
USA
www.fsf.org  www.gnu.org
Skype: No way! That's nonfree (freedom-denying) software.
  Use Ekiga or an ordinary phone call.




  parent reply	other threads:[~2014-09-05  1:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-04 17:33 Reinterpreting the compiler source code Ian Grant
     [not found] ` <CAKFjmdx4Zm2_HVEUre-PYvcZrm41gKv-2z_EsGehjv6NbVxBAw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-04 20:57   ` Bruno Loff
     [not found]     ` <CAGOfsMgZE==zCC2OmEPtbH_ph1g1-AhWikioSdZJFep8crP3vQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-05  0:44       ` Ian Grant
2014-09-05  0:13   ` William ML Leslie
2014-09-05  1:51 ` Richard Stallman [this message]
     [not found]   ` <E1XPigS-000528-41-iW7gFb+/I3LZHJUXO5efmti2O/JbrIOy@public.gmane.org>
2014-09-05  2:23     ` Ian Grant
2014-09-06 22:16       ` Richard Stallman

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/guile/

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

  git send-email \
    --in-reply-to=E1XPigS-000528-41@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=Markus.Kuhn@cl.cam.ac.uk \
    --cc=deraadt@theos.com \
    --cc=guile-devel@gnu.org \
    --cc=ian.a.n.grant@googlemail.com \
    --cc=lightning@gnu.org \
    --cc=schellr@ieee.org \
    --cc=torvalds@osdl.org \
    /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.
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).