From: Stefan Monnier <monnier-CRDzTM1onBSWkKpYnGOUKg@public.gmane.org>
To: lightning-mXXj517/zsQ@public.gmane.org
Cc: guile-devel-mXXj517/zsQ@public.gmane.org
Subject: Re: The Free Semantics Foundation
Date: Thu, 04 Sep 2014 09:34:27 -0400 [thread overview]
Message-ID: <jwvlhpzwm34.fsf-monnier+gmane.lisp.guile.devel@gnu.org> (raw)
In-Reply-To: CAKFjmdwKWQw5=k3Ph9fNS58=+xO3F6eCR9D7Qzbw=oJP3FBgGA@mail.gmail.com
> Focussing on free source code is pointless, we need to focus on free
> semantics.
There I lost you. I'm quite aware of what "semantics" mean in the
context of computer science (and programming languages in particular),
but I really can't see what the above means.
Last I checked, all semantics is described "in some other language"
(whose own semantics is assumed to be known).
So there's still always the same loophole: the program's description is
"source code" and its interpretation is vulnerable because the semantics
of the language in which the description is written may be modified.
And of course, I agree with William that it's probably easier to get
that kind of control nowadays from SMM or one of the many "security"
hardware "features", some of which are even designed to be used remotely.
Stefan
prev parent reply other threads:[~2014-09-04 13:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 1:57 The Free Semantics Foundation Ian Grant
2014-09-04 2:21 ` 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 [this message]
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=jwvlhpzwm34.fsf-monnier+gmane.lisp.guile.devel@gnu.org \
--to=monnier-crdztm1onbswkkpyngoukg@public.gmane.org \
--cc=guile-devel-mXXj517/zsQ@public.gmane.org \
--cc=lightning-mXXj517/zsQ@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).