Linux Security Modules development
 help / color / mirror / Atom feed
From: "Dr. Greg" <greg@enjellic.com>
To: Paul Moore <paul@paul-moore.com>
Cc: linux-security-module@vger.kernel.org
Subject: Re: TSEM feedback.
Date: Tue, 1 Aug 2023 05:54:21 -0500	[thread overview]
Message-ID: <20230801105421.GA23193@wind.enjellic.com> (raw)
In-Reply-To: <CAHC9VhT_6yv=hgCLUMYf154=-ARY5+V+FMi_0O+_t2rsb341Eg@mail.gmail.com>

On Mon, Jul 31, 2023 at 10:57:08AM -0400, Paul Moore wrote:

Good morning, I hope the day is starting well.

> On Mon, Jul 31, 2023 at 6:39???AM Dr. Greg <greg@enjellic.com> wrote:
> >
> > Good morning Paul, I hope this note finds your week starting well.
> >
> > We submitted the patches for the V2 release of TSEM three weeks ago.
> >
> > We received some feedback from Randy Dunlap on some documentations
> > issues that we went on to address.
> >
> > Haven't heard any reflections from you.  Was just wondering if you
> > were swamped or had possibly missed the submission?  We didn't include
> > you as a copy on the notion that you didn't need two sets of patches
> > landing in your inbox.

> If your mail hits the mail archive on lore.kernel.org, it is almost
> a full guarantee that it has hit my inbox and/or the patchwork
> instance I use to ensure nothing is missed.

So noted.

> As one would expect, it takes a good deal of time to review a patch
> submission as large as TSEM, and the rather ornate language used in
> the documentation only slows the process.

For whatever it is worth, as a group, we invested a considerable
amount of time, over a period of now 8+ years, in refining the
terminology and nomenclature embodied in that document.

I guess the only defense at hand is a variant on the alleged response
by Austrian Emperor Joseph II to Mozart's "Die Entfuhrung aus dem
Serail":

"It contains as many words, with appropriate ornateness, as was deemed
necessary."

I believe the case can be made that Quixote/TSEM approaches the
challenge of security from a significantly different conceptual basis
than a significant body of current art in the field.

Legend has it that Dyson and Feynman spent two years talking before
they were able to conclude that they were understanding one another,
despite the fact they were working toward a common goal.

> Rest assured it is firmly on my todo list, but please understand it
> will take some time to properly review.  In the meantime I would
> encourage others to review/play/etc. with TSEM; nothing builds
> maintainer comfort quite like seeing reviews from other trusted
> members of the community.

We respect any time you can afford to this.

With respect to the notion of getting others to play with a new
technology concept.

Security, from an innovation perspective, is an interesting challenge,
probably a candidate for a book with my long time trusted consigliere.
Who, at the risk of excessive ornateness, would delve deeply into the
notion of how structural inherencies act to preclude innovation.

> paul-moore.com

Thanks for the update, best wishes for a productive remainder of the
week.

As always,
Dr. Greg

The Quixote Project - Flailing at the Travails of Cybersecurity

  reply	other threads:[~2023-08-01 11:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-31 10:38 TSEM feedback Dr. Greg
2023-07-31 11:20 ` Bagas Sanjaya
2023-07-31 14:57 ` Paul Moore
2023-08-01 10:54   ` Dr. Greg [this message]
2023-08-01 12:55     ` Serge E. Hallyn
2023-08-01 18:49       ` Paul Moore

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

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

  git send-email \
    --in-reply-to=20230801105421.GA23193@wind.enjellic.com \
    --to=greg@enjellic.com \
    --cc=linux-security-module@vger.kernel.org \
    --cc=paul@paul-moore.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox