From: segaloco via TUHS <tuhs@tuhs.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] DOD KSOS Secure UNIX Operating System Manual and Final Report
Date: Tue, 06 Jun 2023 03:16:17 +0000 [thread overview]
Message-ID: <SjPo5vJ0B48ZAmAEeLfEu2D5ypWXOWs3DqWg_uOJuSKVsRdDa-mDNzQ9Fq_oOSwb2VVx259w5rDzBDntHckoAxJySLk7jS3_ibxBld1TMpI=@protonmail.com> (raw)
As promised in the other email, I had one other tidbit worth sharing some detail on but that is very different from WECo promo and informational material. What I've got here are two documents pertaining to the "Department of Defence Kernelized Secure Operating System" project as undertaken by Ford's Western Development Laboratories Division.
The documents in question are https://apps.dtic.mil/sti/pdfs/ADA111577.pdf and https://apps.dtic.mil/sti/pdfs/ADA111566.pdf and represent the User's Manuals and Final Report respectively on this KSOS system. These appear to be from the same microfiche as the documents linked based on splotches on the last page's date frame, although the copies I have here have the full frame, the PDFs linked seem to have the last panel cropped to a small square in the middle. Not super significant, but sometimes it's the little details.
Anywho, unfortunately I don't have much to report, I got a bit excited while looking for these at first because I was having a hard time turning up PDFs, thought I had stumbled upon something unseen for some time, but in the gulf between last email and this I found them. Silver lining is one less set of documents to scan, but nothing to really expose that isn't already a click away.
- Matt G.
next reply other threads:[~2023-06-06 3:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 3:16 segaloco via TUHS [this message]
2023-06-06 3:34 ` [TUHS] " Tom Perrine
2023-06-06 3:46 ` segaloco via TUHS
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='SjPo5vJ0B48ZAmAEeLfEu2D5ypWXOWs3DqWg_uOJuSKVsRdDa-mDNzQ9Fq_oOSwb2VVx259w5rDzBDntHckoAxJySLk7jS3_ibxBld1TMpI=@protonmail.com' \
--to=tuhs@tuhs.org \
--cc=segaloco@protonmail.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;
as well as URLs for NNTP newsgroup(s).