From: Rich Salz rsalz@osf.org
Subject: /sys/src/libc/port/crypt.c
Date: Sat, 11 Nov 1995 13:33:08 -0500 [thread overview]
Message-ID: <19951111183308.70tgxVEWfrU1X4LE4onN81tM6PNA39TwCQhW2Qn0gd4@z> (raw)
>An added bonus is general purpose encryption in libc.a. This
>provides functionality to enable fast encrypted data streams. My idea
>is to encrypt all data on the wire. Am I being unreasonable?
Probably. What's the encryption algorithm, how often are the keys changed,
how are sessions keys negotiated, how many bits in each key, etc.
/r$
next reply other threads:[~1995-11-11 18:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-11-11 18:33 Rich [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-11-12 4:32 /sys/src/libc/port/crypt.c G.David
1995-11-11 15:44 /sys/src/libc/port/crypt.c G.David
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=19951111183308.70tgxVEWfrU1X4LE4onN81tM6PNA39TwCQhW2Qn0gd4@z \
--to=9fans@9fans.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).