In the following, CJNTEL was an online corporate directory that I had
initially put up on SJRLVM1 that could be queried by anybody on the
internal network.
The following has a suggestion for registering a person's public key
with CJNTEL and making (effecitvely publishing) it available for
retrieval by anybody with access to the internal network.
following is some 15 years or so before being brought in to do some
consulting with a small client/server startup that wanted to do
payment transactions on their server
http://www.garlic.com/~lynn/aadsm5.htm#asrn2
http://www.garlic.com/~lynn/aadsm5.htm#asrn3
To: wheeler
Date: 05/15/81 13:41:12
re: more secure communication over the network
One of the obvious concerns that will surely surface from the CJN work
will be the problem of confidential information being exchanged over
the network.
I have a package from ****** called CRYPT that may be a solution. The
package implements a public key encryption system proposed by Diffie
and Hellman (see recent vm newsletter). The problem we have with
using CIPHER is that we must know an agreed upon key and we have to
exchange the key in a secure manner prior to communication.
The public key system works as follows: I publish a key which anyone
can look up. They use that key to CRYPT the file. That key can only
"lock the safe". In order to DECRYPT the file ("unlock the safe") I
have a private key which no-one knows. Only the private key can unlock
the safe.
As an implementation I suggest we update out CJNTEL entry to include a
public key for each of us. The package includes a procedure for
generating keys. In this way I can look up your key in CJNTEL and send
you ENCRYPTED confidential data.
Cheap and simple.
... snip ...
effectively certificateless public key operation ... misc. past posts
mentioning certicateless public key operation
http://www.garlic.com/~lynn/subpubkey.html#certless
and somewhat similar to the discussion about publishing public keys in
the domain name infrastructure ... a few posts this year discussing
the subject:
http://www.garlic.com/~lynn/2006b.html#37 X.509 and ssh
http://www.garlic.com/~lynn/2006c.html#10 X.509 and ssh
http://www.garlic.com/~lynn/2006c.html#34 X.509 and ssh
http://www.garlic.com/~lynn/2006c.html#35 X.509 and ssh
http://www.garlic.com/~lynn/2006c.html#38 X.509 and ssh
http://www.garlic.com/~lynn/2006d.html#29 Caller ID "spoofing"
http://www.garlic.com/~lynn/2006f.html#16 trusted repositories and trusted
transactions
http://www.garlic.com/~lynn/2006f.html#32 X.509 and ssh
http://www.garlic.com/~lynn/2006f.html#33 X.509 and ssh
http://www.garlic.com/~lynn/2006f.html#34 X.509 and ssh
http://www.garlic.com/~lynn/2006h.html#27 confidence in CA
http://www.garlic.com/~lynn/2006p.html#7 SSL, Apache 2 and RSA key sizes
http://www.garlic.com/~lynn/2006t.html#8 Root CA CRLs
http://www.garlic.com/~lynn/2006v.html#49 Patent buster for a method that
increases password security
as well as the whole account authority digital signature stuff
http://www.garlic.com/~lynn/x959.html#aads
... CJNTEL is different that the internal "online telephone book"
recently mentioned here
http://www.garlic.com/~lynn/2006v.html#32 Effi[ci]ency of branch table vs
individual compare & branch
the internal online telephone book capture the original source from
various corporate locations (that were used to generate the printed
copy), converted the source to desired format and made them available
for distribution. this normally was loaded on local systems that
allowed users to do online lookups on their local machine.
CJNTEL could be accessed remotely over the internal network using
"special message" ... misc. past posts about the internal network
... which was larger than the arpanet/internet from just about the
beginning until sometime mid-85.
http://www.garlic.com/~lynn/subnetwork.html#internalnet
note that the above reference is in addition to the requirement that
all links leaving corporate facilities required link encryptors ...
at one point there was the claim that the internal network had
move than half of all link encryptors in the world.
misc. recent posts mentioning special message
http://www.garlic.com/~lynn/2006k.html#51 other cp/cms history
http://www.garlic.com/~lynn/2006t.html#47 To RISC or not to RISC
http://www.garlic.com/~lynn/2006w.html#8 Why these original FORTRAN quirks?
We did do a modification to CJNTEL so that in addition to doing
various operations on its corporate directory, it was also possible
(for remote network user) to request CJNTEL to execute the telephone
directory command on SJRLVM1 ... returning the results over the
network.
for some topic drift ... some references to the hsdt (high speed data transport)
project
http://www.garlic.com/~lynn/subnetwork.html#hsdt
and some recent posts about various interactions with NSF:
http://www.garlic.com/~lynn/2006s.html#50 Ranking of non-IBM mainframe builders?
http://www.garlic.com/~lynn/2006t.html#6 Ranking of non-IBM mainframe builders?
http://www.garlic.com/~lynn/2006u.html#56 Ranking of non-IBM mainframe builders?
