The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Tom Perrine <tom.perrine+tuhs@gmail.com>
To: Clem Cole <clemc@ccc.com>,
	The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Documentation for Sys-V basic interpreter
Date: Sat, 20 May 2023 16:39:16 -0700	[thread overview]
Message-ID: <CAJq=PCWn+=E9qnJc+Ur8tMdZge2WhjCYaPEGLLtkXD9LDWgrbw@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2MtnzD2DLJsNVecqsWosOdDaVvu+VAQtFr+DZs+gR2LbQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2348 bytes --]

KSOS and related work was sponsored by several DoD activities, at least the
part that I worked on - after 1983.

We've wandered a bit afar for TUHS(?), but, the PWB and other software
wasn't pirated, it was supplied as "government furnished equipment" as part
of each contract.

PWB and other software we got via the NSA's Tycho site, etc. NRL (and then
others) funded later KSOS work, including the Advanced  Command and Control
Testbed (ACCAT) and various multi-level secure "Guard" systems, for the
Navy, Air Force, USAFE, etc.

All of which ran on PDP-11s, using the KSOS kernel and userspace, almost
all built by using PWB as the build platform.





On Sat, May 20, 2023 at 12:09 PM Clem Cole <clemc@ccc.com> wrote:

> I don't think it was pirated. I'm think it was a special license Ford Aero
> got due to the work with the USG. I sort of remember KSOS and if I'm
> correct that was a DoD funded effort for the Orange Book.  So it would make
> absolute sense that Ford Aero might have used the USG connections to
> convince AT&T to release it to them.  As I said, Al was very skittish about
> anything that might be misinterpreted by the Justice dept.  But if DoD was
> asking for it, Al could show the Jusitce -- "hey -- your people asked for
> it -- we were not selling it."
> ᐧ
>
> On Sat, May 20, 2023 at 3:03 PM Jon Forrest <nobozo@gmail.com> wrote:
>
>>
>>
>> On 5/20/2023 11:50 AM, Clem Cole wrote:
>> > Taking this off list.
>> >
>> > I've always wondered about that.  Thank you bad word choice -- but it
>> > was not officially released outside the Bell System.   Since Ford Aero
>> > had it, it must have been a very special license.
>>
>> It was already there when I arrived so I don't know how it got there.
>> I doubt it was pirated.
>>
>> > Was Ford Aero doing something on a Gvt bid when you were using it?
>>
>> Yes. It was creating KSOS which Tom Ferrine has also mentioned on the
>> TUHS list. This was a "provably" secure version of Unix.
>>
>> You might want to ask John Nagle. His email is probably
>> nagle@sitetruth.com, and his GitHub is https://github.com/John-Nagle.
>> He was there when I arrived and he was a key developer of KSOS.
>> If he doesn't know the answer then he might be able to refer you to
>> someone who does.
>>
>> Jon
>>
>>
>>
>>

[-- Attachment #2: Type: text/html, Size: 3655 bytes --]

      parent reply	other threads:[~2023-05-20 23:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-19 15:06 [TUHS] " KenUnix
2023-05-19 19:46 ` josh
2023-05-19 20:15 ` [TUHS] " Clem Cole
2023-05-19 20:17   ` Clem Cole
2023-05-19 20:19 ` segaloco via TUHS
2023-05-19 23:26   ` KenUnix
2023-05-20  0:31   ` Clem Cole
2023-05-20  4:28     ` segaloco via TUHS
2023-05-20 13:43       ` Clem Cole
2023-05-20 14:16         ` KenUnix
2023-05-20 16:05         ` Jon Forrest
2023-05-20 18:13           ` Tom Perrine
     [not found]           ` <CAC20D2M1whQwZBaDyd0EMiXrxBG6GarxD-6sNGZ_OosYxgkDcA@mail.gmail.com>
     [not found]             ` <89eeadc5-271a-c984-e55e-662cfeb23f6b@gmail.com>
     [not found]               ` <CAC20D2MtnzD2DLJsNVecqsWosOdDaVvu+VAQtFr+DZs+gR2LbQ@mail.gmail.com>
2023-05-20 23:39                 ` Tom Perrine [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

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

  git send-email \
    --in-reply-to='CAJq=PCWn+=E9qnJc+Ur8tMdZge2WhjCYaPEGLLtkXD9LDWgrbw@mail.gmail.com' \
    --to=tom.perrine+tuhs@gmail.com \
    --cc=clemc@ccc.com \
    --cc=tuhs@tuhs.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 NNTP newsgroup(s).