From: Grant Taylor via TUHS <tuhs@minnie.tuhs.org>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] TUHS web server has changed
Date: Wed, 4 May 2022 23:57:34 -0600 [thread overview]
Message-ID: <39dfe7a4-85b0-8d75-2d32-5ee433876743@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <CALMnNGjyALGMnH-R_Hj=6x0J-xCT5t17k3X3DnrAMY-RYt1V1Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 817 bytes --]
On 5/4/22 11:43 PM, Andy Kosela wrote:
> Binary and encryption protocols and standards, js crap that change
> in an increasing pace. The public information should be accessible
> by all, even with an old 486dx.
I believe there is a time and a place for some encryption. It's
probably more than you think, but definitely less than zealots want.
Yes, even the venerable 486 should be able to handle the level of
encryption that I'm referencing. -- At least it could do the math if
the software would run on it.
My main reasons for encryption are privacy and generating more noise for
others to hide their signal in that /need/ to do so.
Privacy also includes some security in that middle boxes can't inject
questionable (read: malicious) content.
--
Grant. . . .
unix || die
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4017 bytes --]
next prev parent reply other threads:[~2022-05-05 6:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 2:08 Warren Toomey via TUHS
2022-05-04 13:27 ` Clem Cole
2022-05-04 19:37 ` Mary Ann Horton
2022-05-05 0:52 ` Dave Horsfall
2022-05-05 5:43 ` Andy Kosela
2022-05-05 5:57 ` Grant Taylor via TUHS [this message]
2022-05-05 20:48 ` Dave Horsfall
2022-05-04 17:54 ` Grant Taylor via TUHS
2022-05-05 21:26 ` Warren Toomey via TUHS
2022-05-05 23:42 ` Gregg Levine
2022-05-06 2:38 ` Grant Taylor via TUHS
2022-05-06 2:52 ` Warner Losh
2022-05-06 4:32 ` Kenneth Goodwin
2022-05-07 16:13 ` Patrick Audley via TUHS
2022-05-09 16:12 ` Grant Taylor via TUHS
2022-05-09 17:55 ` Kenneth Goodwin
2022-05-09 19:22 ` Richard Salz
2022-05-09 19:57 ` Grant Taylor via TUHS
2022-05-09 18:37 ` Danil Smirnov
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=39dfe7a4-85b0-8d75-2d32-5ee433876743@spamtrap.tnetconsulting.net \
--to=tuhs@minnie.tuhs.org \
--cc=gtaylor@tnetconsulting.net \
/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).