From: G. David Butler gdb@dbSystems.com
Subject: /sys/src/libc/port/crypt.c
Date: Sat, 11 Nov 1995 10:44:56 -0500 [thread overview]
Message-ID: <19951111154456.NSQCAVAz5JS7ngKOi0yUnegTWLAimv9zi4GnZ99h3Bc@z> (raw)
Because of export restrictions, I assume, the source to the encrypt()
and decrypt() functions (/sys/src/libc/port/crypt.c) are not on the CD-ROM.
I have used the code base that Pace Willisson <pace@blitz.com> made
available for authenication on UNIX to recreate crypt.c.
Even though I was more careful using unsigned declarations throughout
the code, I am concerned about character size problems. From what I
can tell, the caller of encrypt/decrypt will handle the conversion of
whatever to blocks of bytes for encryption, but is this sufficient?
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?
For a sanity check, are there any restrictions for routines in libc.a?
One last question, is it possible to get the original code from Bell Labs
if you are a US citizen?
Thanks for your attention.
David Butler
gdb@dbSystems.com
next reply other threads:[~1995-11-11 15:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-11-11 15:44 G.David [this message]
1995-11-11 18:33 /sys/src/libc/port/crypt.c Rich
1995-11-12 4:32 /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=19951111154456.NSQCAVAz5JS7ngKOi0yUnegTWLAimv9zi4GnZ99h3Bc@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).