From: Stefan Israelsson Tampe <stefan.itampe@gmail.com>
To: guile-devel <guile-devel@gnu.org>, Guile User <guile-user@gnu.org>
Subject: Safe computing paradigm
Date: Wed, 6 Dec 2023 22:41:59 +0100 [thread overview]
Message-ID: <CAGua6m23yUSYZhV3TCzjvHMjkkY8aWci9Lbo_Vo7syvX30S8OA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 482 bytes --]
All the details on how to do a good and efficient security design for
computing is already discovered and covered by a patent but no one states
how this works and although we have CHERI, they seem to miss the point.
This or similar is the absolute best approach that, with a sane political
will, will make sure that we can both catch thieves and have privacy.
https://www.linkedin.com/pulse/safe-smart-computing-stefan-israelsson-xl4wf/
http://isenwriter.com/safe-computing.html
[-- Attachment #2: Type: text/html, Size: 740 bytes --]
next reply other threads:[~2023-12-06 21:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 21:41 Stefan Israelsson Tampe [this message]
2023-12-06 21:54 ` Safe computing paradigm Lassi Kortela
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=CAGua6m23yUSYZhV3TCzjvHMjkkY8aWci9Lbo_Vo7syvX30S8OA@mail.gmail.com \
--to=stefan.itampe@gmail.com \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.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).