unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Ian Grant <ian.a.n.grant-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
To: Richard Stallman <rms-mXXj517/zsQ@public.gmane.org>,
	guile-devel-mXXj517/zsQ@public.gmane.org,
	lightning <lightning-mXXj517/zsQ@public.gmane.org>,
	 Markus Kuhn
	<Markus.Kuhn-kDbDZe0LBGWFxr2TtlUqVg@public.gmane.org>,
	Theo deRaadt <deraadt-T7FYYhErWq4AvxtiuMwx3w@public.gmane.org>,
	Linus Torvalds <torvalds-3NddpPZAyC0@public.gmane.org>
Subject: The Free Semantics Foundation
Date: Wed, 3 Sep 2014 21:57:17 -0400	[thread overview]
Message-ID: <CAKFjmdwKWQw5=k3Ph9fNS58=+xO3F6eCR9D7Qzbw=oJP3FBgGA@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 4133 bytes --]

> That hack recognized specific syntax.  Any change in the wrong
> place would break it.

Which hack was that? The one Thompson is reported to have actually
implemented in Unix? You are assuming what you are trying to prove: you are
assuming there has only ever been one instance of this class of attack, and
you are trying to prove that this class of attack is unlikely. That used to
be called "Begging the Question" but nowadays the general level of
understanding of logic is so poor that most uses of that phrase are not in
this sense.

It may *seem* unlikely, but to anyone who has given serious thought to the
possibilities of such an attack it seems more than wildly probable.

I suppose everyone know that Roger Schell spent several years in the office
of deputy director of the NSA's National Computer Security Centre?  If he
did not alert the NSA to the possibility of this sort of attack then he was
not doing his job properly. Having read some of the Computer Security
History Project interview with him, I do not think Roger Schell is the sort
of person who doesn't do his job properly.

Thompson wrote that paper in 1984, and I don't think that was a
coincidence. What he shows is that if you control the semantics of a
language, that is if you control the meaning of what people say, then you
control what they *see,* and so you also control what they think. And that
was a theme in Orwell's book "1984." By controlling the meaning of what
people say, Big Brother controlled their thought.

In programming terms, if you control the semantics of the compiler, then
you can control what people see. For example, you can insert code into
libc.so and ld.so that looks for certain signatures and then changes the
data that system calls like read and stat return to certain programs, such
as sha256sum and objdump for example, according to some predicate. You can
also monitor the behaviour of other programs. If you see that there is a
program that reads mainly C source and writes mainly a.out executables,
then you know those executables should contain a certain signature, and if
they don't then you know you have a C compiler on the system which is not
bugged, at least, one which has not got *your* bug (it may have any number
of other such bugs however, because this semantics generalises.) So you can
call for help, or you can even insert code to call for help into
the binaries that program creates. Basically, your power over the system
appears to be total. Of course it's not, because there are any number of
other such bugs in there with you. In the end the only person who is
guaranteed not to have control over what the system does is the program
source code.

Now it may seem unlikely to some that this has been done. But it is surely
obvious to *everyone* that this is *possible,* and since the advantage an
attacker accrues if he can pull this off effectively is incalculable, it
should also be obvious to *everyone* that if this has not yet been done,
then it will soon be done. Perhaps as a direct result of people reading
what I am writing right now.

So I hope people will focus on this problem, in spite of what Richard says.
He will change his mind in due course, quite shortly I think :-)

Focussing on free source code is pointless, we need to focus on free
semantics. Of course this negates certain fairly fundamental principles of
the Free Software Foundation. One of these is the idea of "Copyleft." By
taking concrete representation of algorithms as the stock-in-trade of
computer programmers, it is able to use the copyright laws to effect a kind
of viral copyright status which automatically infects any program which
uses that particular source code representation. The problem is that once
one concentrates on free semantics rather than free source code, there is
no longer any recourse to the copyright laws: the copyright laws protect
only one particular concrete representation of an idea. The only legal
protection sematics have is through patent law. So the Free Software
Foundation, if it's to 'own' anything at all anymore, will have to register
and defend its assets as patents.

Ian

[-- Attachment #1.2: Type: text/html, Size: 4317 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Lightning mailing list
Lightning-mXXj517/zsQ@public.gmane.org
https://lists.gnu.org/mailman/listinfo/lightning

             reply	other threads:[~2014-09-04  1:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-04  1:57 Ian Grant [this message]
2014-09-04  2:21 ` The Free Semantics Foundation William ML Leslie
     [not found]   ` <CAHgd1hHsXaa83Ga7q6K9qOQ0pM_rYsfM--noMwegy9Lt=UJgBg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-04 23:59     ` Ian Grant
2014-09-05  1:39       ` Stefan Monnier
2014-09-04 13:34 ` Stefan Monnier

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='CAKFjmdwKWQw5=k3Ph9fNS58=+xO3F6eCR9D7Qzbw=oJP3FBgGA@mail.gmail.com' \
    --to=ian.a.n.grant-gm/ye1e23mwn+bqq9rbeug@public.gmane.org \
    --cc=Markus.Kuhn-kDbDZe0LBGWFxr2TtlUqVg@public.gmane.org \
    --cc=deraadt-T7FYYhErWq4AvxtiuMwx3w@public.gmane.org \
    --cc=guile-devel-mXXj517/zsQ@public.gmane.org \
    --cc=lightning-mXXj517/zsQ@public.gmane.org \
    --cc=rms-mXXj517/zsQ@public.gmane.org \
    --cc=torvalds-3NddpPZAyC0@public.gmane.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).