From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Most complex instructions (was Re: IBM 9020 FAA/ATC Systems from 1960's)
Newsgroups: alt.folklore.computers
Date: Sat, 18 Aug 2001 17:59:48 GMT

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

YKYGOW...

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: YKYGOW...
Newsgroups: alt.folklore.computers
Date: Sat, 18 Aug 2001 20:00:38 GMT

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

YKYGOW...

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: YKYGOW...
Newsgroups: alt.folklore.computers
Date: Sun, 19 Aug 2001 15:21:49 GMT

misc. refs (from old usenet postings):

From: OLE@CSLI.STANFORD.EDU (Ole J. Jacobsen)
Newsgroups: comp.protocols.tcp-ip
Subject: INTEROP 88: 3rd TCP/IP Conference and Exhibition
Message-ID: <585858698.0.OLE@CSLI.Stanford.EDU>
Date: 25 Jul 88 18:31:38 GMT
Date-Received: 28 Jul 88 06:57:52 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet

INTEROP 88: The 3rd TCP/IP Interoperability Conference and Exhibition
will be held at the Santa Clara Convention Center and Doubletree Hotel
from September 26 through 30th, 1988.  The format is 2 days of tutorials
followed by 3 days of technical session (16 in all).  For the first time,
there will also be an Interoperability exhibition where vendors will show
TCP/IP systems on a "Show and Tel-Net" which additionally will be connected
to the Internet.

A number of vendors, known as the "Netman" group will be demonstrating
an experimental network management system based on the  ISO CMIP/CMIS
protocols.

For more information on the conference contact:

Advanced Computing Environments
480 San Antonio Road, Suite 100
Mountain View, CA 94040
(415) 941-3399
-------

YKYGOW...

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: YKYGOW...
Newsgroups: alt.folklore.computers
Date: Sun, 19 Aug 2001 16:34:39 GMT

From: dcrocker@AHWAHNEE.STANFORD.EDU (Dave Crocker)
Newsgroups: comp.protocols.tcp-ip
Subject: Re:  DoD --> CMOT and SNMP
Date: 2 Sep 89 04:40:26 GMT
Organization: The Internet

(Sorry.  I intended to send this to the entire list. DHC)

From dcrocker Fri Sep  1 21:28:53 1989
From: Dave Crocker <dcrocker>
Subject: Re:  DoD --> CMOT and SNMP
To: mcsun!cernvax!cgch!wasc@uunet.uu.net

The Internet Activities Board has declared SNMP and CMOT to be co-equal
standards.  If effect, this means that they both have a stamp of approval
from a significant "standards" body.  (For the TCP/IP technology, the
IAB fills the kind of role that ISO and CCITT and ECMA do in various
parts of international communities.

So much for the stamp of approval.

Your question is more to the point and asks about actual support by
vendors.  (A nicely practical point to have concern for.)

A number of companies are currently shipping products that use SNMP.
Further, the NSFNet is managed using it.  It is my impression that virtually
all TCP/IP vendors have announced intent to support SNMP, if they are not
already doing so.

SNMP is unique to the TCP/IP community, although it uses the OSI ASN.1
encoding standard, for specifying the format of objects.  CMOT is derived
from the OSI CMOT standards effort, although I am told there are some
differences.  It is not clear to me that these differences are in the
management protocol, itself, it does run over a modified stack of
support protocols.  Most significantly, is uses TCP or, perhaps, UDP,
instead of an OSI transport.  Hence, CMOT gets you closer to the future
of OSI network management protocol details.

However, there does not appear to be any vendor that currently ships
CMOT and, therefore, there is no field (production network) experience
using it.  While a number of vendors have announced plans to support
CMOT, I am not aware of any official, announced, delivery dates from
these vendors.

A further point about the recent decision to make SNMP and CMOT co-equal
standards is that their use of the Management Information Base (MIB) was
entirely de-coupled.  While one should expect them to continue to use the
original 100 variable, there having additional variable in common is
problematic.  At the least, such sharing should be expected to organic or
accidental, rather than formally enforced.  (That should be "expected to
be organic..."  I am on a thin wire with a poor editor.)

As always, I trust that others will elaborate on, as well as correct,
the above.  Dive in!

Dave Crocker
Digital Equipment Corp.

P.S.  On review, I note that I did not respond to your query about
federal requirements for CMOT support:  There is strong governmental
pressure for moving to OSI.  This is embodied in the GOSIP document.
In general, however, the requirements are careful to allow use of
alternatives.  Perhaps the most extreme way of viewing this is that a
vendor certainly cannot consider ignoring the OSI CMOT.  I am less clear
about their ability to dodge CMOT (but am sure that someone out there in
tcp-land will chime in to clarify, please?)  Enough vendors have stated
intent to support CMOT and enough are working on it, that I would expect it
to start showing up in the future.

P.P.S.  I should use this opportunity to suggest a personal bias.  It is NOT
about which protocol I prefer.  In fact, the brouhaha has, in my opinion,
distracted us from worrying about how to manage multi-administration
inter-networks.  The chosen protocol is not irrelevant to this, but my
suspicion is that we could start with a hopelessly incomplete one and
still not know how to use it to its fullest.

That is, our general understanding and pursuit of specifying and
developing management (application) SERVICES has been quite limited
and that we would do well to focus on MIB enhancement and specification
of standard applications for management.  (I.e., focus on the bottom
and top of the management architecture.)

D/

YKYGOW...

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: YKYGOW...
Newsgroups: alt.folklore.computers
Date: Mon, 20 Aug 2001 16:18:34 GMT

another folktale was of a reported presentation in the mid-80s to the corporate executive committee that if VNET wasn't converted to SNA, it would stop working (ignoring for the moment that if it had tried to have used SNA it would have never happened).

one of the brilliance of VNET was that from the start it divorced the link-level and much of the network-level from the higher levels and effectively had gateway function from the start (essentially late '60s). This didn't appear in the internet until the great cut-over in '83 (and was one of the reasons that the internal network was larger than the arpanet/internet from just about the beginning thru the mid-80s).

in the ibm batch world, one of the primary implementations was JES2 & NJE, which didn't share this characteristic and it was frequent that when two different releases of JES2/NJE attempted to diretly communicate it could result in a (total) system crash. As a result, on the internal network, JES2/NJE nodes were relegated to peripherial nodes with intermediate VNET nodes having line-drivers that handled the appropriate JES2/NJE header formating to minimize JES2 taking down the complete system (that it was running on).

the primary design and implementation effort was the work of one of the people at the cambridge scientific center (same center that virtual machines, a lot of ibm time-sharing, GML, etc came out of; pretty productive for a location that rarely had more than 40 people).

random refs:
https://www.garlic.com/~lynn/internet.htm
https://www.garlic.com/~lynn/subindex.html#network
https://www.garlic.com/~lynn/subindx2.html#network
https://www.garlic.com/~lynn/subpubkey.html#networking

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

YKYGOW...

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: YKYGOW...
Newsgroups: alt.folklore.computers
Date: Mon, 20 Aug 2001 16:25:12 GMT

the wind would then change to down-valley sometime late mid-morning. you would sometimes find san jose airport shutdown for 10 minutes or so around 11am for take-off/landings to reverse direction (majority of the time the pattern is south to north, but some mornings it would be the reverse and then have to change sometime mid-morning).

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

Net banking, is it safe???

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Net banking, is it safe???
Newsgroups: comp.security.misc
Date: Mon, 20 Aug 2001 17:15:07 GMT

For instance, in netscape ... hit the security button and it brings up a window of all the security related information. One of the entries on the left is "passwords". If you click "passwords", you set something that while all the words say "certificates" ... it really refers to your private key. There is also an entry "certifictes" on the left, with subentries "yours", "people", "web sites", & "signers". If you click "yours", it will show you any public key certificates that correspond to your private key(s).

IE supports something similar using MSCAPI.

It does get tricky if you want to have a single web application that works/looks the same for both netscape and IE tho.

such things have been doen, it is possible to do something using certificate-less PKI ... for instance see (AADS) nacha references at
https://www.garlic.com/~lynn/

It is also possible to upgrade radius to support public/private key authentication ... where a public key is stored in the radius database in lieu of a PIN/password (radius possibly handles 99.999% of the internet-related client-authentication events that go on in the world today ... although with PIN/passwords).

The administrative operation & business processes for managing the radius database stays the same (even with public key enhancement), the issue is that it eliminates the well-known problems with shared-secret authentication. It is also possible to do web-server "stubs" that interface to radius for client authentication; rather than the rather prevalent approach which is a local flat file with userid/passwords.

It is also possible to do an incremental transition, where a flat file userid/password is imported to radius, w/o changing the look & feel to the clients. Then on an account by account basis, conversion could be done to public key.

this approach can be done in a certificate-less PKI mode ... w/o resorting to the possibly better known certificate-based PKI (and all its problems).

random refs:
https://www.garlic.com/~lynn/subpubkey.html#radius
https://www.garlic.com/~lynn/subpubkey.html#sslcerts
https://www.garlic.com/~lynn/subpubkey.html#privacy
https://www.garlic.com/~lynn/subintegrity.html#fraud

in addition to some of bruce's comments ... also see
http://www.smu.edu/~jwinn/ Jane Winn's home page !! NOTE moved to !!
http://www.law.washington.edu/Faculty/Winn/Publications/The%20Emperor's%20New%20Clothes.htm
http://www.smu.edu/~jwinn/shocking-truth.htm shocking truth about !! NOTE moved to !!
http://www.law.washington.edu/Faculty/Winn/Publications/The%20Emperor's%20New%20Clothes.htm

digital signatures and internet commerce

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

Net banking, is it safe???

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Net banking, is it safe???
Newsgroups: comp.security.misc
Date: Mon, 20 Aug 2001 18:14:08 GMT

for common support (both netscape & IE) ... we eventually had to do some magic java that talked directly to a token/reader driver.

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

YKYGOW...

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: YKYGOW...
Newsgroups: alt.folklore.computers
Date: Mon, 20 Aug 2001 21:28:22 GMT

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

Question about the 'U'

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Question about the 'U'
Newsgroups: alt.folklore.computers
Date: Mon, 20 Aug 2001 21:33:07 GMT

& click on term (term->RFC#)

& then click on "URI" in Acronym fastpath.

that will get you to long list of RFCs related to uniform resource

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

GETMAIN R/RU (was: An IEABRC Adventure)

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: GETMAIN R/RU (was: An IEABRC Adventure)
Newsgroups: comp.lang.asm370
Date: Mon, 20 Aug 2001 21:53:44 GMT

3033 also introduced dual address space.

specific refs:
https://www.garlic.com/~lynn/2000e.html#57 Why not an IBM zSeries workstation?
https://www.garlic.com/~lynn/2000e.html#58 Why not an IBM zSeries workstation?

IBM 3033          80-06 81-10 16  Ext. Addr.=32MB REAL ADDR.;MP ONLY
IBM D.Addr.Sp.    80-06 81-06 12  Dual Address Space for 3033
IBM 3033XF        80-06 81-06 12  OPTIONAL HW/FW PERF. ENHANCE FOR MVS/SP
IBM 3033 24MB     80-11 81-11 12  24MB REAL MEM. FOR 3033UP, AP

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

IBM 9020 FAA/ATC Systems from 1960's

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: IBM 9020 FAA/ATC Systems from 1960's
Newsgroups: alt.folklore.computers
Date: Tue, 21 Aug 2001 14:07:27 GMT

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

IBM 9020 FAA/ATC Systems from 1960's

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: IBM 9020 FAA/ATC Systems from 1960's
Newsgroups: alt.folklore.computers
Date: Tue, 21 Aug 2001 14:10:30 GMT

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

Net banking, is it safe???

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Net banking, is it safe???
Newsgroups: comp.security.misc
Date: Tue, 21 Aug 2001 14:46:53 GMT

the AADS certificate-less scenerio (like what NACHA used in the ATM debit network trials)
https://www.garlic.com/~lynn/aadsm6.htm#aadsatm

&/or the enhancement to RADIUS
https://www.garlic.com/~lynn/subpubkey.html#radius

just continue to use all the existing business infrastructures with the benefit that the technology has been upgraded from shared-secret to public key.

The benefit is that all the short-comings of shared-secret technology has been removed w/o introducing any new business process exposures.

The standard PKI with TTPs introduce a whole lot of new business and technology processes that can fail in new and inexplicable ways.

It is one-thing to do simple technology upgrade of an existing business process infrastructure to address the shared-secret short-comings; it is quite a different thing to pay a lot of money to some brand new business entity over which there may no direct control of their business operations.

A case in point is the SSL domain server certificates.
https://www.garlic.com/~lynn/subpubkey.html#sslcerts

Quite a few people thing that they eliminate the domain name infrastructure vulnerabilities by some new magic mumbo-jumbo. Without SSL certificates, a client could depend on the domain name infrastructure to correctly resolve the domain name to ip-address, and then perform some other form of key-exchange to setup an encrypted session. With SSL certificates, the client "trusts" that the certificate corrects all domain name infrastructure short-comings and always correctly identifies the real domain name owner (as well as assists in the key-exchange for an excrypted session).

However, what is it that a TTP does in the case of domain name certificate? The authoritative agency for who actually owns what domain name is the domain name structure. The proccess that PKI TTPs use for a certificate ... is that they "certify" that they have verified the information in a certificate with the authoritative agency responsible for the information being certified. In the case of domain name information, that is the authoritative agency for domain name ownership; the domain name infrastructure (the very same agency that supposedly has integrity problems and gives rise to the whole SSL domain server certificates in the first place).

The issue for certificate TTP PKIs isn't that they don't "fix" the shared-secret problem, but that they are subject to all the security shortcomings that an in-house business operation is subject to (i.e. they aren't magic panecia).

Furthermore, a certificate TTP PKI doesn't eliminate requiring security for in-house business operations; all that continues to exist; so in effect a TTP PKI duplicates security and expense of the in-house business operations (and the more pieces, the more likelyhood there is a security failure point that happens someplace).

There have been a couple places that financial institutions have done certificate-based PKI ... but in almost everyone that I'm aware of, there were essentially relying-party-only certificates ... where a certificate may have been used at an initial portal and then the "real" verification occurred based on the banks account record.

In all of those scenerios, it is trivial to show that the actual certificate is extraneous, redundant, and superfluous and that the "real" public-key authentication can be done directly from the account record (where the real verification occurs anyway).

For an extended discussion of such scenerios
https://www.garlic.com/~lynn/ansiepay.htm#aadsnwi2

where either 1) the certificate is shown to be redundant and superfluous since the account record is always accessed or 2) the certificate can be compressed to zero-bytes (using compression philosiphy from x9.68).

public key radius (authentication) posts
https://www.garlic.com/~lynn/subpubkey.html#radius
SSL certificate posts
https://www.garlic.com/~lynn/subpubkey.html#sslcerts
privacy related poss
https://www.garlic.com/~lynn/subpubkey.html#privacy

other posts
https://www.garlic.com/~lynn/aadsm3.htm#cstech3 cardtech/securetech & CA PKI
https://www.garlic.com/~lynn/aadsm3.htm#kiss1 KISS for PKIX. (Was: RE: ASN.1 vs XML (used to be RE: I-D ACTION :draft-ietf-pkix-scvp- 00.txt))
https://www.garlic.com/~lynn/aadsm3.htm#kiss6 KISS for PKIX. (Was: RE: ASN.1 vs XML (used to be RE: I-D ACTION :draft-ietf-pkix-scvp- 00.txt))
https://www.garlic.com/~lynn/aadsm4.htm#6 Public Key Infrastructure: An Artifact...
https://www.garlic.com/~lynn/aadsm4.htm#9 Thin PKI won - You lost
https://www.garlic.com/~lynn/aadsm5.htm#x959 X9.59 Electronic Payment Standard
https://www.garlic.com/~lynn/aadsm5.htm#shock revised Shocking Truth about Digital Signatures
https://www.garlic.com/~lynn/aadsmore.htm#client4 Client-side revocation checking capability
https://www.garlic.com/~lynn/aepay3.htm#aadsrel2 AADS related information ... summary
https://www.garlic.com/~lynn/aepay3.htm#x959discus X9.59 discussions at X9A & X9F
https://www.garlic.com/~lynn/2000b.html#93 Question regarding authentication implementation
https://www.garlic.com/~lynn/2000e.html#41 Why trust root CAs ?
https://www.garlic.com/~lynn/2000f.html#3 Why trust root CAs ?
https://www.garlic.com/~lynn/2000f.html#15 Why trust root CAs ?
https://www.garlic.com/~lynn/2001c.html#57 PKI and Non-repudiation practicalities
https://www.garlic.com/~lynn/2001c.html#58 PKI and Non-repudiation practicalities
https://www.garlic.com/~lynn/2001e.html#35 Can I create my own SSL key?
https://www.garlic.com/~lynn/2001f.html#79 FREE X.509 Certificates
https://www.garlic.com/~lynn/2001g.html#65 PKI/Digital signature doesn't work

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

History of Microsoft Word (and wordprocessing in general)

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: History of Microsoft Word (and wordprocessing in general)
Newsgroups: alt.folklore.computers
Date: Tue, 21 Aug 2001 18:46:22 GMT

from prior posting (in this thread)
https://www.garlic.com/~lynn/2001i.html#1
stu at cambridge scientific center did "script" in the '60s ... which had a runoff like syntax. Then in the early '70s the people at CSC added "GML" markup syntax to script .... although "script" could still be used in either runoff like syntax or markup syntax.

when ibm pc came out ... somebody did a port of the script ... effectively same formating that could be done on the mainframe.

and of course "GML" ... which people think stands for generalized markup language ... were actually the first letter of the last names of the three people that worked on it.

script wasn't a word-processor itself ... it handled document formating. script/gml documents used some other editor ... typically non-WYSIWYG. CMS had a number of editors ... starting with the standard CMS editor in the mid-60s, and in the 70s the were a whole slew of 3720 full-screen editors, edgar, ned, red, xedit, etc.

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

History of Microsoft Word (and wordprocessing in general)

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: History of Microsoft Word (and wordprocessing in general)
Newsgroups: alt.folklore.computers
Date: Wed, 22 Aug 2001 02:06:40 GMT

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

Very CISC Instuctions (Was: why the machine word size ...)

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Very CISC Instuctions (Was: why the machine word size ...)
Newsgroups: alt.folklore.computers
Date: Wed, 22 Aug 2001 02:15:20 GMT

improvement later was the a74 with 4mbytes of memory.

random refs:
https://www.garlic.com/~lynn/94.html#46 Rethinking Virtual Memory
https://www.garlic.com/~lynn/96.html#23 Old IBM's
https://www.garlic.com/~lynn/99.html#120 atomic History
https://www.garlic.com/~lynn/2000.html#5 IBM XT/370 and AT/370 (was Re: Computer of the century)
https://www.garlic.com/~lynn/2000.html#29 Operating systems, guest and actual
https://www.garlic.com/~lynn/2000.html#75 Mainframe operating systems
https://www.garlic.com/~lynn/2000e.html#52 Why not an IBM zSeries workstation?
https://www.garlic.com/~lynn/2000e.html#55 Why not an IBM zSeries workstation?
https://www.garlic.com/~lynn/2000e.html#56 Why not an IBM zSeries workstation?
https://www.garlic.com/~lynn/2001c.html#89 database (or b-tree) page sizes
https://www.garlic.com/~lynn/2001d.html#43 Economic Factors on Automation
https://www.garlic.com/~lynn/2001f.html#28 IBM's "VM for the PC" c.1984??
https://www.garlic.com/~lynn/2001g.html#53 S/370 PC board

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

Very CISC Instuctions (Was: why the machine word size ...)

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Very CISC Instuctions (Was: why the machine word size ...)
Newsgroups: alt.folklore.computers
Date: Wed, 22 Aug 2001 02:34:33 GMT

.... something from a recent email (regards vs/repack product)
a similar ... but different project that i worked in the early '70s was the data capture part of something that was released as a product called "vs/repack".

basically it captured storage traces and attempted to do program re-organization for virtual memory efficiency.

part of the output was a storage use map plotted against instructions. for proper display, it required a special TN train that had some bar characters. A typical configuration was 2000 instructions per column of 132character print width with storage running down the page. Would typically try and configure storage so that it fit in about six foot length of printer paper. At various times, halls of 4th floor 545 tech. sq had walls nearly completed paper with such output. Take each six foot strip and hang it from the top of the wall ... and you could walk down the hall corresponding to the program executing and watch the program reference memory (storage use was both instruction fetch as well as data store/fetch).

It was used early on to rewrite the garbage collection of APL for virtual memory environment. It was also used by a number of IBM product groups for execution hot-spot detection ... independent of storage use/organization optimization.

D. Hatfield & J. Gerald, Program Restructuring for Virtual Memory, IBM Systems Journal, v10n3, 1971

random other refs:
https://www.garlic.com/~lynn/93.html#4 360/67, was Re: IBM's Project F/S ?
https://www.garlic.com/~lynn/93.html#5 360/67, was Re: IBM's Project F/S ?
https://www.garlic.com/~lynn/94.html#7 IBM 7090 (360s, 370s, apl, etc)
https://www.garlic.com/~lynn/97.html#4 Mythical beasts (was IBM... mainframe)
https://www.garlic.com/~lynn/99.html#20 APL/360.
https://www.garlic.com/~lynn/99.html#68 The Melissa Virus or War on Microsoft?
https://www.garlic.com/~lynn/2000g.html#30 Could CDR-coding be on the way back?
https://www.garlic.com/~lynn/2001b.html#83 Z/90, S/390, 370/ESA (slightly off topic)
https://www.garlic.com/~lynn/2001c.html#10 Memory management - Page replacement
https://www.garlic.com/~lynn/2001c.html#31 database (or b-tree) page sizes
https://www.garlic.com/~lynn/2001c.html#33 database (or b-tree) page sizes
https://www.garlic.com/~lynn/2001d.html#18 Drawing entities

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

3745 and SNI

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: 3745 and SNI
Newsgroups: bit.listserv.ibm-main
Date: Wed, 22 Aug 2001 11:52:32 GMT

and might also be credited with prompting the original VTAM/NCP design

parts of presentation I gave in Raleigh at an SNA architecture review board meeting (in the mid-80s):
https://www.garlic.com/~lynn/99.html#67

small extract:
System verses 3725NCP System:

Higher availability More reliable More function Improved Useability Non-IBM Host Support Much better connectivity Much better performance Fewer components Easier to tune Easier to tailor Easier to manage Less expensive

also:
https://www.garlic.com/~lynn/99.html#70

First 360 PCM/OEM Controller
https://www.garlic.com/~lynn/submain.html#360pcm

misc. random refs:
https://www.garlic.com/~lynn/99.html#63 System/1 ?
https://www.garlic.com/~lynn/99.html#64 Old naked woman ASCII art
https://www.garlic.com/~lynn/99.html#66 System/1 ?
https://www.garlic.com/~lynn/99.html#67 System/1 ?
https://www.garlic.com/~lynn/99.html#70 Series/1 as NCP (was: Re: System/1 ?)
https://www.garlic.com/~lynn/99.html#106 IBM Mainframe Model Numbers--then and now?
https://www.garlic.com/~lynn/99.html#239 IBM UC info
https://www.garlic.com/~lynn/2000.html#64 distributed locking patents
https://www.garlic.com/~lynn/2000.html#72 Difference between NCP and TCP/IP protocols
https://www.garlic.com/~lynn/2000b.html#29 20th March 2000
https://www.garlic.com/~lynn/2000b.html#66 oddly portable machines
https://www.garlic.com/~lynn/2000b.html#79 "Database" term ok for plain files?
https://www.garlic.com/~lynn/2000b.html#87 Motorola/Intel Wars
https://www.garlic.com/~lynn/2000c.html#43 Any Series/1 fans?
https://www.garlic.com/~lynn/2000c.html#53 Any Series/1 fans?
https://www.garlic.com/~lynn/2000c.html#54 WHAT IS A MAINFRAME???
https://www.garlic.com/~lynn/2001.html#4 Sv: First video terminal?
https://www.garlic.com/~lynn/2001.html#62 California DMV
https://www.garlic.com/~lynn/2001.html#65 California DMV
https://www.garlic.com/~lynn/2001.html#68 California DMV
https://www.garlic.com/~lynn/2001.html#72 California DMV
https://www.garlic.com/~lynn/2001b.html#75 Z/90, S/390, 370/ESA (slightly off topic)
https://www.garlic.com/~lynn/2001e.html#8 Blame it all on Microsoft
https://www.garlic.com/~lynn/2001e.html#55 Pre ARPAnet email?
https://www.garlic.com/~lynn/2001f.html#22 Early AIX including AIX/370
https://www.garlic.com/~lynn/2001f.html#30 IBM's "VM for the PC" c.1984??
https://www.garlic.com/~lynn/2001f.html#33 IBM's "VM for the PC" c.1984??
https://www.garlic.com/~lynn/2001f.html#42 Golden Era of Compilers
https://www.garlic.com/~lynn/2001f.html#44 Golden Era of Compilers

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

History of Microsoft Word (and wordprocessing in general)

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: History of Microsoft Word (and wordprocessing in general)
Newsgroups: alt.folklore.computers
Date: Wed, 22 Aug 2001 15:43:45 GMT

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

Very CISC Instuctions (Was: why the machine word size ...)

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Very CISC Instuctions (Was: why the machine word size ...)
Newsgroups: alt.folklore.computers
Date: Wed, 22 Aug 2001 15:47:21 GMT

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

Proper ISA lifespan?

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Proper ISA lifespan?
Newsgroups: comp.arch
Date: Wed, 22 Aug 2001 15:53:55 GMT

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

Net banking, is it safe???

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Net banking, is it safe???
Newsgroups: comp.security.misc
Date: Wed, 22 Aug 2001 16:25:25 GMT

other fraud possibilities would still exist ... but having much lower return per cost; most of these are attacks on individual machines. Whole class of these are addressed by the european union finread directive; namely an independent secure device that supports both secure pin-entry and secure transaction display.

typical hardware tokens require PIN/passwords of various sorts. While these PIN/passwords are physically similar to PIN/passwords used to access system services ... they have a significantly different threat model not being shared-secrets and potential subject to mass harvestings aka the PIN/password is only known by the owner of the hardware token. This can be extended to biometrics where instead of using biometrics as a shared-secret (i.e. transmitting to an institution for comparison with something on file) it is only used between the owner and their hardware token.

the european union finread has secure pin entry to avoid the exploit of keystroke evesdropping ... i.e. pin-entry thru standard keyboard and PC (there has been a lot recently about keystroke capture programs, by employers monitoring employees, by parents monitoring children and by viruses automatically transmitting capture keystrokes to select sites).

The other part of the finread is secure display of the transaction being signed (i.e. virus can display one thing on the screen and send something totally different to the token to be signed).

Tokens w/o PINs/passwords can have arbritrary messages sent to them for signing with no ability on the owner's part to securely validate what is being signed and/or if something is being signed.

Tokens used in insecure PIN/passwords evironment can have messages signed w/o the owner's knowledge by capture the PIN/password and transmitting it w/o the token owner's participation.

Tokens used in secure PIN/password environment may require owner's knowledge of something that is being signed, but what is displayed as being signed is different that what is actually signed.

The european union finread work has both 1) secure PIN/password entry environment so there is high probability that only the token owner is entering the PIN/password and 2) secure message display so there is high probability that the token owner has the token sign what they believe should be signed.

And of course, all of this can operate in either a CADS (certification authority digital signature) environment or a AADS (account authority digital signature, or certificate-less) environment.

misc. references on finread &/or certificate-less
https://www.garlic.com/~lynn/aadsm3.htm#cstech3 cardtech/securetech & CA PKI
https://www.garlic.com/~lynn/aadsm3.htm#kiss1 KISS for PKIX. (Was: RE: ASN.1 vs XML (used to be RE: I-D ACTION :draft-ietf-pkix-scvp- 00.txt))
https://www.garlic.com/~lynn/aadsm3.htm#kiss2 Common misconceptions, was Re: KISS for PKIX. (Was: RE: ASN.1 vs XML (used to be RE: I-D ACTION :draft-ietf-pkix-scvp-00.txt))
https://www.garlic.com/~lynn/aadsm5.htm#spki Simple PKI
https://www.garlic.com/~lynn/aadsm5.htm#spki2 Simple PKI
https://www.garlic.com/~lynn/aadsm6.htm#aadsatm (certificate-less) digital signatures can secure ATM card payments on the internet
https://www.garlic.com/~lynn/aadsmore.htm#hcrl1 Huge CRLs
https://www.garlic.com/~lynn/2001g.html#57 Q: Internet banking
https://www.garlic.com/~lynn/2001g.html#60 PKI/Digital signature doesn't work
https://www.garlic.com/~lynn/2001g.html#61 PKI/Digital signature doesn't work
https://www.garlic.com/~lynn/2001g.html#62 PKI/Digital signature doesn't work
https://www.garlic.com/~lynn/2001g.html#64 PKI/Digital signature doesn't work
https://www.garlic.com/~lynn/2001h.html#53 Net banking, is it safe???
https://www.garlic.com/~lynn/2001i.html#9 Net banking, is it safe???
https://www.garlic.com/~lynn/2001i.html#16 Net banking, is it safe???

public key radius (authentication) posts
https://www.garlic.com/~lynn/subpubkey.html#radius
domain name public key SSL certificate posts
https://www.garlic.com/~lynn/subpubkey.html#sslcerts
privacy relaced posts
https://www.garlic.com/~lynn/subpubkey.html#privacy
risk, fraud, exploits posts
https://www.garlic.com/~lynn/subintegrity.html#fraud

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

No Trusted Viewer possible?

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: No Trusted Viewer possible?
Newsgroups: comp.security.misc,comp.security.pgp.discuss
Date: Wed, 22 Aug 2001 16:48:55 GMT

the european union finread program attempts to address of the environment for secure digital signatures.

a hardware token can sign a message w/o the owner's knowledge a hardware token can sign a message different than what the owner thinks is being signed.

it is slightly more difficult in the paper signature case for a signature to be done w/o the owner's knowledge (but of course counterfeits can happen).

and of course there is always complicated language that results in a person signing something different than what they think they are signing.

however, lets say it is a trivial payment transaction which basically says the token owner is paying a specific person a specific amount.

without a secure signing environment (more than the use of a E4 high token), transactions could be signed w/o the token owner's knowledge and/or transactions could be signed that has different amounts than what the token owner believed were involved.

basically finread dictates a secure device that includes secure pin/password entry as well as secure display.

implicit is that the token owner has to do something for the signature to even take place in the first place (i.e. PC sending arbritrary number of messages to the token for signing w/o the token owner's knowledge).

then a secure pin/password entry avoids the keystroke capture problem, i.e. pin/password entered with standard pc keyboard (all the news about keystroke capture programs, employers monitoring employees, parents monitoring children, viruses sending catpured keystrokes to unknown internet addresses). A virus that has captured token pin/password keystrokes could send an abritrary large number of messages to the token for signing w/o the token owner's knowledge.

finally a secure display avoids the substituted message problem, i.e. a virus displays one transaction value on the screen while sending a totally different transaction value to be signed.

the basic problem is that there is a significantly larger disconnect between a hardware token performing some mathematical operation on a string of bits (i.e. digital signature) ... something that the token owner has no way of directly verifying ... compared to somebody executing a signature on a piece of paper.

misc finread postings
https://www.garlic.com/~lynn/2001g.html#57 Q: Internet banking
https://www.garlic.com/~lynn/2001g.html#60 PKI/Digital signature doesn't work
https://www.garlic.com/~lynn/2001g.html#61 PKI/Digital signature doesn't work
https://www.garlic.com/~lynn/2001g.html#62 PKI/Digital signature doesn't work
https://www.garlic.com/~lynn/2001g.html#64 PKI/Digital signature doesn't work

misc. other refs:
https://www.garlic.com/~lynn/subintegrity.html#fraud

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

History of Microsoft Word (and wordprocessing in general)

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: History of Microsoft Word (and wordprocessing in general)
Newsgroups: alt.folklore.computers
Date: Wed, 22 Aug 2001 18:28:06 GMT

some old postings
https://www.garlic.com/~lynn/94.html#26 Misc. more on bidirectional links
https://www.garlic.com/~lynn/2001c.html#67 What ever happened to WAIS?

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

Proper ISA lifespan?

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Proper ISA lifespan?
Newsgroups: comp.arch
Date: Wed, 22 Aug 2001 18:47:08 GMT

http://perso.club-internet.fr/febcm/english/power_pc_products.htm
Temporary conclusion

The PowerPC deal did not go as smoothly as contemplated at the beginning of 1992. Bull reduced its commitment in the PowerPC microprocessor, by taking only a token presence in Somerset design center in Austin, and by not buying derivative rights on the architecture. A second blow happened when IBM Rochester decided to make its own version of the PowerPC instead of model 620 as initially contemplated. Michael Armstrong, who have been the chief IBM instrumentor of the agreement leaved IBM for Hughes and eventually AT&T. Lou Gerstner decided to stop the centrifugal startegy of his predecessor and to recenter IBM on mainframes, significantly decreasing the Austin hopes of seeing the PowerPC as the IBM core architecture. The disappointing sales of Apple, close to be driven away from the hardware market until 1998 iMac, also hurted the future of the PowerPC.

The strategy changes inside IBM and the Motorola's withdrawal modified somewhat the Bull AIX offer that added in 1998 IBM servers using the Rochester processors (under AIX only).


http://www.zdnet.com/pcmag/issues/1418/pcm00071.htm
Scaling up the performance ladder from the PowerPC 604 is the PowerPC 620, the only 64-bit PowerPC CPU yet announced. With most of the PC world only now making the transition from 16-bit to 32-bit code, however, it's not clear that the ability to run 64-bit code will provide an immediate benefit to most users. The PowerPC 620 will remain backward-compatible with 32-bit PowerPC code.

The consortium has also hinted at a PowerPC 630 chip that will succeed the PowerPC 620, but will not yet disclose details about the chip's architecture except to indicate that it will roughly double the performance of the PowerPC 620. The PowerPC 630 is due in 1997.


http://www.mot.com/SPS/PowerPC/library/ppc_faq/ppc_faq.html
PowerPC 601

The very first PowerPC. It was designed as a bridge between the POWER architecture and the PowerPC architecture. For this reason, it incorporates the user-level POWER instructions which were eliminated from the PowerPC specification.

PowerPC 601v

This is a 601, implemented in a 0.5u CMOS 2.5V process. This effectively means that it runs faster and draws less power. (Originally called the "601+".)

PowerPC 602

A processor aimed at consumer electronics (set-top boxes, game consoles, etc.), PDAs, and embedded controller applications.

PowerPC 603

A low-power processor, intended for portable applications, e.g., notebook computers. Performance is roughly comparable to the 601 (see below for benchmarks).

PowerPC 603e

A higher-performance 603 with a faster clock and bigger caches. (Originally called the "603+".)

PowerPC 603ev

A lower-voltage, faster-clock version of the 603e.

PowerPC 604

A higher-performance processor, intended for high-end desktop systems.

PowerPC 604e

A 604 with larger caches.

PowerPC 620

An even higher-performance processor, aimed at high-end systems and multiprocessors. The 620 is the first 64-bit PowerPC implementation.

G3 Series

The "next generation" of PowerPC processors, expected to ship in 1997.

G4 Series

Expected in 1999.

The 601 is manufactured by IBM and sold by both IBM and Motorola. The 603 and 603e are manufactured by both IBM and Motorola.


http://historia.et.tudelft.nl/wggesch/geschiedenis/microprocessor/1991/
https://web.archive.org/web/20020613112019/http://historia.et.tudelft.nl/wggesch/geschiedenis/microprocessor/1991/
IBM and Motorola announce and introduce the prototype of the PowerPC 620 processor, operating at 133-MHz.


http://www.fh-augsburg.de/~mc68/Crions_PowerCompilation/ppc1.html
https://web.archive.org/web/20020309063235/http://www.fh-augsburg.de/~mc68/Crions_PowerCompilation/ppc1.html
The PowerPC 604(tm) and PowerPC 604e(tm) microprocessors are 32-bit implementations of the PowerPC architecture designed for use in high performance desktop, workstation, and symmetric multiprocessing computer systems. The PowerPC 604 and PowerPC 604e are software and bus compatible with the PowerPC 601, PowerPC 603, and PowerPC 603e microprocessors. The PowerPC 604 features separate 16-Kbyte, physically addressed instruction and data caches, while the 604e offers 32-Kbyte instruction and data caches.

The PowerPC 620(tm) microprocessor is a 64-bit implementation of the PowerPC architecture providing high levels of performance for technical and scientific workstations, application and LAN servers and symmetric multiprocessing computer systems.

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

History of Microsoft Word (and wordprocessing in general)

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: History of Microsoft Word (and wordprocessing in general)
Newsgroups: alt.folklore.computers
Date: Wed, 22 Aug 2001 18:52:52 GMT

you couldn't put it in the microwave since it destroyed whatever heat sensitive material was involved.

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

IBM OS Timeline?

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: IBM OS Timeline?
Newsgroups: bit.listserv.ibm-main,alt.folklore.computers
Date: Thu, 23 Aug 2001 17:05:57 GMT

TSS/360, TSO, VS/PC (online for vs1, was originally going to be PCO, but somebody checking international conflicts decided it needed changing) were all equally bad. TSO was frequently so bad that they campaigned for a long time that sub-second response wasn't a necessary goal of human factors.

Then there was the infamous TSO/VMCMS bake-off done by CERN in the early '70s (CERN ... the place that HTML came out of). The TSO numbers were so bad that internally within IBM the copy of the report was classified "Confidential, Restricted" (even tho it was a customer report and available at places like share, Confidential, Restricted is need to know only ... 2nd highest security classification after Registered Confidential).

As an undergraduate at the university, Starting with release 11, I developed a manual process for taking the output from stage1 (aka stage2) and re-organizing it into individual jobs so that it could be run in a production job stream. The sequencing of both the jobs and the major move/copy statements were organized so that datasets and members within PDS were optimally placed to minimize arm motion

A test job that might take 30 seconds elapsed time on a vanilla generated system could run three times faster on an "optimized" system. The problem was that normal PTF activity (over a six month period) doing member replacement in svclib & linklib could result in lengthing elapsed time to double that on a freshly generated system.

For a MVT18/HASP system, I tore out the 2780 RJE support in HASP (to obtain some addressability and reduce storage requirements) and replaced it with an implementation of a CMS editor syntax support 2741, tty, and 1052 terminals ... for an early CRJE/TSO like implementation.

This was also during the period when I discovered some of the limitations of the 2702 and the limitations with associating any line-scanner with any line (aka automatic terminal & speed recognition). This was the direct reason why we started our own terminal control unit project (building our own channel adapter board, etc) to support automatic terminal type and speed recognition. This turned out to be the genesis of the IBM PCM control unit business.
https://www.garlic.com/~lynn/submain.html#360pcm

random refs:
https://www.garlic.com/~lynn/93.html#0 360/67, was Re: IBM's Project F/S ?
https://www.garlic.com/~lynn/93.html#1 360/67, was Re: IBM's Project F/S ?
https://www.garlic.com/~lynn/93.html#2 360/67, was Re: IBM's Project F/S ?
https://www.garlic.com/~lynn/93.html#18 location 50
https://www.garlic.com/~lynn/93.html#23 MTS & LLMPS?
https://www.garlic.com/~lynn/93.html#25 MTS & LLMPS?
https://www.garlic.com/~lynn/94.html#00 Big I/O or Kicking the Mainframe out the Door
https://www.garlic.com/~lynn/94.html#0 Multitasking question
https://www.garlic.com/~lynn/94.html#1 Multitasking question
https://www.garlic.com/~lynn/94.html#2 Schedulers
https://www.garlic.com/~lynn/94.html#4 Schedulers
https://www.garlic.com/~lynn/94.html#12 360 "OS" & "TSS" assemblers
https://www.garlic.com/~lynn/94.html#18 CP/67 & OS MFT14
https://www.garlic.com/~lynn/94.html#20 CP/67 & OS MFT14
https://www.garlic.com/~lynn/94.html#33 short CICS story
https://www.garlic.com/~lynn/94.html#46 Rethinking Virtual Memory
https://www.garlic.com/~lynn/94.html#47 Rethinking Virtual Memory
https://www.garlic.com/~lynn/94.html#49 Rethinking Virtual Memory
https://www.garlic.com/~lynn/94.html#53 How Do the Old Mainframes
https://www.garlic.com/~lynn/94.html#54 How Do the Old Mainframes
https://www.garlic.com/~lynn/95.html#1 pathlengths
https://www.garlic.com/~lynn/95.html#2 Why is there only VM/370?
https://www.garlic.com/~lynn/96.html#4a John Hartmann's Birthday Party
https://www.garlic.com/~lynn/96.html#7 Why Do Mainframes Exist ???
https://www.garlic.com/~lynn/96.html#12 IBM song
https://www.garlic.com/~lynn/96.html#26 System/360 Model 30
https://www.garlic.com/~lynn/97.html#12 OSes commerical, history
https://www.garlic.com/~lynn/97.html#22 Pre S/360 IBM Operating Systems?
https://www.garlic.com/~lynn/97.html#28 IA64 Self Virtualizable?
https://www.garlic.com/~lynn/98.html#10 OS with no distinction between RAM a
https://www.garlic.com/~lynn/98.html#11 S/360 operating systems geneaology
https://www.garlic.com/~lynn/98.html#12 S/360 operating systems geneaology
https://www.garlic.com/~lynn/98.html#13 S/360 operating systems geneaology
https://www.garlic.com/~lynn/98.html#17 S/360 operating systems geneaology
https://www.garlic.com/~lynn/98.html#18 Reviving the OS/360 thread (Questions about OS/360)
https://www.garlic.com/~lynn/98.html#21 Reviving the OS/360 thread (Questions about OS/360)
https://www.garlic.com/~lynn/98.html#28 Drive letters
https://www.garlic.com/~lynn/98.html#29 Drive letters
https://www.garlic.com/~lynn/98.html#33 ... cics ... from posting from another list
https://www.garlic.com/~lynn/98.html#47 Multics and the PC
https://www.garlic.com/~lynn/99.html#2 IBM S/360
https://www.garlic.com/~lynn/99.html#7 IBM S/360
https://www.garlic.com/~lynn/99.html#37 why is there an "@" key?
https://www.garlic.com/~lynn/99.html#39 Internet and/or ARPANET?
https://www.garlic.com/~lynn/99.html#41 A word processor from 1960
https://www.garlic.com/~lynn/99.html#58 When did IBM go object only
https://www.garlic.com/~lynn/99.html#63 System/1 ?
https://www.garlic.com/~lynn/99.html#64 Old naked woman ASCII art
https://www.garlic.com/~lynn/99.html#76 Mainframes at Universities
https://www.garlic.com/~lynn/99.html#77 Are mainframes relevant ??
https://www.garlic.com/~lynn/99.html#93 MVS vs HASP vs JES (was 2821)
https://www.garlic.com/~lynn/99.html#94 MVS vs HASP vs JES (was 2821)
https://www.garlic.com/~lynn/99.html#95 Early interupts on mainframes
https://www.garlic.com/~lynn/99.html#109 OS/360 names and error codes (was: Humorous and/or Interesting Opcodes)
https://www.garlic.com/~lynn/99.html#119 Computer, supercomputers & related
https://www.garlic.com/~lynn/99.html#126 Dispute about Internet's origins
https://www.garlic.com/~lynn/99.html#127 Dispute about Internet's origins
https://www.garlic.com/~lynn/99.html#131 early hardware
https://www.garlic.com/~lynn/99.html#142 OS/360 (and descendants) VM system?
https://www.garlic.com/~lynn/99.html#155 checks (was S/390 on PowerPC?)
https://www.garlic.com/~lynn/99.html#174 S/360 history
https://www.garlic.com/~lynn/99.html#209 Core (word usage) was anti-equipment etc.
https://www.garlic.com/~lynn/99.html#237 I can't believe this newsgroup still exists.
https://www.garlic.com/~lynn/2000.html#1 Computer of the century
https://www.garlic.com/~lynn/2000.html#64 distributed locking patents
https://www.garlic.com/~lynn/2000.html#68 Mainframe operating systems
https://www.garlic.com/~lynn/2000.html#71 Mainframe operating systems
https://www.garlic.com/~lynn/2000.html#76 Mainframe operating systems
https://www.garlic.com/~lynn/2000.html#91 Ux's good points.
https://www.garlic.com/~lynn/2000.html#92 Ux's good points.
https://www.garlic.com/~lynn/2000b.html#44 20th March 2000
https://www.garlic.com/~lynn/2000b.html#54 Multics dual-page-size scheme
https://www.garlic.com/~lynn/2000b.html#61 VM (not VMS or Virtual Machine, the IBM sort)
https://www.garlic.com/~lynn/2000b.html#87 Motorola/Intel Wars
https://www.garlic.com/~lynn/2000c.html#8 IBM Linux
https://www.garlic.com/~lynn/2000c.html#10 IBM 1460
https://www.garlic.com/~lynn/2000c.html#18 IBM 1460
https://www.garlic.com/~lynn/2000c.html#34 What level of computer is needed for a computer to Love?
https://www.garlic.com/~lynn/2000c.html#35 What level of computer is needed for a computer to Love?
https://www.garlic.com/~lynn/2000c.html#42 Domainatrix - the final word
https://www.garlic.com/~lynn/2000c.html#45 Does the word "mainframe" still have a meaning?
https://www.garlic.com/~lynn/2000c.html#50 Does the word "mainframe" still have a meaning?
https://www.garlic.com/~lynn/2000c.html#60 Disincentives for MVS & future of MVS systems programmers
https://www.garlic.com/~lynn/2000c.html#79 Unisys vs IBM mainframe comparisons
https://www.garlic.com/~lynn/2000d.html#4 Share - lodging (MTA)
https://www.garlic.com/~lynn/2000d.html#30 Secure Operating Systems
https://www.garlic.com/~lynn/2000d.html#36 Assembly language formatting on IBM systems
https://www.garlic.com/~lynn/2000d.html#44 Charging for time-share CPU time
https://www.garlic.com/~lynn/2000d.html#50 Navy orders supercomputer
https://www.garlic.com/~lynn/2000f.html#18 OT?
https://www.garlic.com/~lynn/2000f.html#52 TSS ancient history, was X86 ultimate CISC? designs)
https://www.garlic.com/~lynn/2000f.html#53 360 Architecture, Multics, ... was (Re: X86 ultimate CISC? No.)
https://www.garlic.com/~lynn/2000f.html#56 TSS ancient history, was X86 ultimate CISC? designs)
https://www.garlic.com/~lynn/2000f.html#63 TSS ancient history, was X86 ultimate CISC? designs)
https://www.garlic.com/~lynn/2000f.html#78 TSS ancient history, was X86 ultimate CISC? designs)
https://www.garlic.com/~lynn/2000g.html#0 TSS ancient history, was X86 ultimate CISC? designs)
https://www.garlic.com/~lynn/2000g.html#2 TSS ancient history, was X86 ultimate CISC? designs)
https://www.garlic.com/~lynn/2000g.html#3 virtualizable 360, was TSS ancient history
https://www.garlic.com/~lynn/2000g.html#4 virtualizable 360, was TSS ancient history
https://www.garlic.com/~lynn/2000g.html#6 virtualizable 360, was TSS ancient history
https://www.garlic.com/~lynn/2000g.html#11 360/370 instruction cycle time
https://www.garlic.com/~lynn/2000g.html#12 360 Architecture, Multics, ... was (Re: X86 ultimate CISC? No.)
https://www.garlic.com/~lynn/2000g.html#27 Could CDR-coding be on the way back?
https://www.garlic.com/~lynn/2001.html#26 Disk caching and file systems. Disk history...people forget
https://www.garlic.com/~lynn/2001.html#62 California DMV
https://www.garlic.com/~lynn/2001.html#63 Are the L1 and L2 caches flushed on a page fault ?
https://www.garlic.com/~lynn/2001b.html#0 Java as a first programming language for cs students
https://www.garlic.com/~lynn/2001b.html#18 Linux IA-64 interrupts [was Re: Itanium benchmarks ...]
https://www.garlic.com/~lynn/2001b.html#29 z900 and Virtual Machine Theory
https://www.garlic.com/~lynn/2001b.html#35 John Mashey's greatest hits
https://www.garlic.com/~lynn/2001b.html#42 John Mashey's greatest hits
https://www.garlic.com/~lynn/2001b.html#80 Disks size growing while disk count shrinking = bad performance
https://www.garlic.com/~lynn/2001c.html#68 IBM Glossary
https://www.garlic.com/~lynn/2001c.html#76 Unix hard links
https://www.garlic.com/~lynn/2001d.html#1 SSL question
https://www.garlic.com/~lynn/2001d.html#14 on-card key generation for smart card
https://www.garlic.com/~lynn/2001d.html#28 Very CISC Instuctions (Was: why the machine word size ...)
https://www.garlic.com/~lynn/2001d.html#48 VTOC position
https://www.garlic.com/~lynn/2001d.html#49 VTOC position
https://www.garlic.com/~lynn/2001d.html#54 VM & VSE news
https://www.garlic.com/~lynn/2001d.html#56 Pentium 4 Prefetch engine?
https://www.garlic.com/~lynn/2001d.html#77 Pentium 4 Prefetch engine?
https://www.garlic.com/~lynn/2001e.html#19 SIMTICS
https://www.garlic.com/~lynn/2001e.html#69 line length (was Re: Babble from "JD" <dyson@jdyson.com>)
https://www.garlic.com/~lynn/2001f.html#2 Mysterious Prefixes
https://www.garlic.com/~lynn/2001f.html#20 VM-CMS emulator
https://www.garlic.com/~lynn/2001f.html#22 Early AIX including AIX/370
https://www.garlic.com/~lynn/2001f.html#23 MERT Operating System & Microkernels
https://www.garlic.com/~lynn/2001f.html#26 Price of core memory
https://www.garlic.com/~lynn/2001f.html#30 IBM's "VM for the PC" c.1984??
https://www.garlic.com/~lynn/2001f.html#33 IBM's "VM for the PC" c.1984??
https://www.garlic.com/~lynn/2001f.html#47 any 70's era supercomputers that ran as slow as today's supercomputers?
https://www.garlic.com/~lynn/2001f.html#48 any 70's era supercomputers that ran as slow as today's supercomputers?
https://www.garlic.com/~lynn/2001f.html#49 any 70's era supercomputers that ran as slow as today's supercompu
https://www.garlic.com/~lynn/2001f.html#68 Q: Merced a flop or not?
https://www.garlic.com/~lynn/2001g.html#22 Golden Era of Compilers
https://www.garlic.com/~lynn/2001g.html#24 XML: No More CICS?
https://www.garlic.com/~lynn/2001g.html#29 any 70's era supercomputers that ran as slow as today's supercomputers?
https://www.garlic.com/~lynn/2001g.html#33 Did AT&T offer Unix to Digital Equipment in the 70s?
https://www.garlic.com/~lynn/2001g.html#35 Did AT&T offer Unix to Digital Equipment in the 70s?
https://www.garlic.com/~lynn/2001g.html#45 Did AT&T offer Unix to Digital Equipment in the 70s?
https://www.garlic.com/~lynn/2001g.html#48 The Alpha/IA64 Hybrid
https://www.garlic.com/~lynn/2001h.html#9 VM: checking some myths.
https://www.garlic.com/~lynn/2001h.html#10 VM: checking some myths.
https://www.garlic.com/~lynn/2001h.html#11 checking some myths.
https://www.garlic.com/~lynn/2001h.html#12 checking some myths.
https://www.garlic.com/~lynn/2001h.html#14 Installing Fortran
https://www.garlic.com/~lynn/2001h.html#17 IBM 9020 FAA/ATC Systems from 1960's
https://www.garlic.com/~lynn/2001h.html#26 TECO Critique
https://www.garlic.com/~lynn/2001h.html#34 D
https://www.garlic.com/~lynn/2001h.html#46 Whom Do Programmers Admire Now???
https://www.garlic.com/~lynn/2001h.html#59 Blinkenlights
https://www.garlic.com/~lynn/2001h.html#76 Other oddball IBM System 360's ?
https://www.garlic.com/~lynn/2001i.html#2 Most complex instructions (was Re: IBM 9020 FAA/ATC Systems from 1960's)
https://www.garlic.com/~lynn/2001i.html#3 Most complex instructions (was Re: IBM 9020 FAA/ATC Systems from 1960's)
https://www.garlic.com/~lynn/2001i.html#13 GETMAIN R/RU (was: An IEABRC Adventure)

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

3745 and SNI

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: 3745 and SNI
Newsgroups: bit.listserv.ibm-main,alt.folklore.computers
Date: Thu, 23 Aug 2001 19:16:11 GMT

the above reference talk was about a fully-redundant peer-to-peer robust packet infrastructure (initially on S/1 ... but with migration to RIOS) which then flowed encapsulated RUs and dropped back to SNA reduced function emulation at the required boundary interfaces. All of the VTAM SSCPs were told that the resources were cross-domain with a different SSCP owner ... when in fact, resource "ownership" was actually fully distributed with no single point of failure.

random refs:
https://www.garlic.com/~lynn/94.html#33a High Speed Data Transport (HSDT)
https://www.garlic.com/~lynn/99.html#70 Series/1 as NCP (was: Re: System/1 ?)
https://www.garlic.com/~lynn/2000.html#3 Computer of the century
https://www.garlic.com/~lynn/2000.html#50 APPC vs TCP/IP
https://www.garlic.com/~lynn/2000.html#51 APPC vs TCP/IP
https://www.garlic.com/~lynn/2000.html#53 APPC vs TCP/IP
https://www.garlic.com/~lynn/2000.html#90 Ux's good points.
https://www.garlic.com/~lynn/2000b.html#78 "Database" term ok for plain files?
https://www.garlic.com/~lynn/2000b.html#79 "Database" term ok for plain files?
https://www.garlic.com/~lynn/2000b.html#89 "Database" term ok for plain files?
https://www.garlic.com/~lynn/2000c.html#45 Does the word "mainframe" still have a meaning?
https://www.garlic.com/~lynn/2000c.html#54 WHAT IS A MAINFRAME???
https://www.garlic.com/~lynn/2000d.html#32 S/360 development burnout?
https://www.garlic.com/~lynn/2000d.html#78 When the Internet went private
https://www.garlic.com/~lynn/2000e.html#56 Why not an IBM zSeries workstation?
https://www.garlic.com/~lynn/2001b.html#49 PC Keyboard Relics
https://www.garlic.com/~lynn/2001e.html#8 Blame it all on Microsoft
https://www.garlic.com/~lynn/2001f.html#49 any 70's era supercomputers that ran as slow as today's supercompu
https://www.garlic.com/~lynn/2001g.html#32 Did AT&T offer Unix to Digital Equipment in the 70s?
https://www.garlic.com/~lynn/2001g.html#49 Did AT&T offer Unix to Digital Equipment in the 70s?
https://www.garlic.com/~lynn/2001i.html#7 YKYGOW...

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

IBM OS Timeline?

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: IBM OS Timeline?
Newsgroups: bit.listserv.ibm-main,alt.folklore.computers
Date: Thu, 23 Aug 2001 21:37:38 GMT

http://www.llnl.gov/vcm/interviews/norman_hardy_1.html
https://web.archive.org/web/20021221044432/http://www.llnl.gov/vcm/interviews/norman_hardy_1.html
http://ftp.arl.mil/~mike/comphist/
http://os390-mvs.hypermart.net/mvshist.htm
http://www.brouhaha.com/~eric/retrocomputing/ibm/stretch/
http://www.nfrpartners.com/comphistory/
https://people.computing.clemson.edu/~mark/acs.html
http://wvnvm.wvnet.edu/EVENTS.HTML
https://people.computing.clemson.edu/~mark/acs_technical.html
https://www.leeandmelindavarian.com/Melinda#VMHist
http://wb4huc.home.texas.net/pds2pds/ibm_370.htm
http://vzone.virgin.net/chris.houghton/comp/index.html
http://homepages.kcbbs.gen.nz/nbree/saga.html
http://www.clock.org/~jss/work/mts/30years.html
http://www.clock.org/~jss/work/mts/index.html
http://www.computerhistory.org/
https://web.archive.org/web/20010218005108/http://www.isham-research.freeserve.co.uk/chrono.txt
http://www.computerhistory.org/timeline/topics/components.page
https://web.archive.org/web/20030813223021/www.cs.ncl.ac.uk/events/anniversaries/40th/images/ibm360_67/index.html
http://www.mcjones.org/System_R/
https://www.multicians.org/thvv/360-67.html
https://web.archive.org/web/20030813224124/www.cs.ncl.ac.uk/events/anniversaries/40th/images/ibm360_672/index.html
https://web.archive.org/web/20030419023518/www.cs.ncl.ac.uk/events/anniversaries/40th/images/unclassified2/print03.html
https://web.archive.org/web/20031121232747/www.cs.ncl.ac.uk/events/anniversaries/40th/webbook/photos/index.html
http://accl.grc.nasa.gov/archives/index.html
http://www.cs.utk.edu/~shuford/terminal/ibm.html
http://www.cs.uiowa.edu/~jones/cards/codes.html
http://homes.cs.washington.edu/~lazowska/frontiers/progress/
http://www.212.net/business/jargon.htm
https://web.archive.org/web/20020601123619/http://www.212.net/business/jargon.htm

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

Waterloo Interpreters (was Re: RAX (was RE: IBM OS Timeline?))

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Waterloo Interpreters (was Re: RAX (was RE: IBM OS Timeline?))
Newsgroups: bit.listserv.ibm-main,alt.folklore.computers
Date: Fri, 24 Aug 2001 03:01:24 GMT

Lots of places wrote various kinds on one step monitors that would handle things like fortran g, link edit & go as one step ... which resulted in student jobs being 10-15 seconds per ... still slower than the 709. we had ibm working on a one step monitor for handling multiple student jobs. One weekend (summer after my sophomore year i got a programming job ... they would let me have the whole machine room from 8am sat. until 8am monday), I duplicated and "interpreted" (aka standard punch didn't print so had to have it run thru something that "printed" the characters on the cards) his deck ... and then spent part of the weekend fixing it. I left both decks for the ibm guy. IBM made a big fuss for a while ... until I showed them all the bugs that i had fixed.

we got watfor sometime in 1967 ... which would batch compile & execute multiple student jobs in single step. Typical runs would wait until there was about a tray of student jobs checked in ... say 2500 or so cards (possibly 40-50 student jobs) ... slap watfor jcl on front and run it as one job step. I believe that watfor did something like 20,000 cards/min compile on 360m65/m67 (which typically was all that student jobs were).

With both hasp and watfor ... we had student jobs finally being processed faster than they had been on the 709.

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

IBM OS Timeline?

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: IBM OS Timeline?
Newsgroups: bit.listserv.ibm-main,alt.folklore.computers
Date: Fri, 24 Aug 2001 03:35:54 GMT

Around '68 or so, somebody at Union Carbide (north? south? carolina) did something called online/os. It basically was PCP with an "interactive" application that talked to the operator's 1052-7 (and specifically targeted for running under CP/67). This was an attempt to CMS'ize PCP (as opposed to morph'ing PCP into CMS).

CMS did run most of the standard OS/360 compilers (fortg, forth, apl, pli), etc. To do this, the cambridge/CMS group wrote something like a 30kbyte OS SVC simulator i.e. they wrote sufficient OS/360 SVC simulation code so that most OS/360 compilers and applications programs would execute under CMS (this was about 30kbytes or so of code necessary to emulate OS/360).

Note, also in the above regarding early MVT, there is mention 360m65 MP in 1968. The 360m67 multiprocessor was at least a year earlier (originally for tss/360). The OS/MP support on the 360m65 was global kernel/supervisor lock. The 360m67 had channel director, independent paths to memory for I/O and the processors and other features that weren't seen until possibly the 3084. Charlie's work (at Cambridge) on fine-grain locking for CP/67 resulted in the compare and swap instruction (mnemonic that are charlie's initials CAS).

random mp, compare&swap, etc
https://www.garlic.com/~lynn/subtopic.html#smp

random CTSS references:
https://www.garlic.com/~lynn/93.html#0 360/67, was Re: IBM's Project F/S ?
https://www.garlic.com/~lynn/93.html#23 MTS & LLMPS?
https://www.garlic.com/~lynn/93.html#25 MTS & LLMPS?
https://www.garlic.com/~lynn/94.html#0 Multitasking question
https://www.garlic.com/~lynn/94.html#1 Multitasking question
https://www.garlic.com/~lynn/94.html#2 Schedulers
https://www.garlic.com/~lynn/94.html#54 How Do the Old Mainframes
https://www.garlic.com/~lynn/97.html#12 OSes commerical, history
https://www.garlic.com/~lynn/97.html#22 Pre S/360 IBM Operating Systems?
https://www.garlic.com/~lynn/98.html#10 OS with no distinction between RAM a
https://www.garlic.com/~lynn/98.html#13 S/360 operating systems geneaology
https://www.garlic.com/~lynn/98.html#17 S/360 operating systems geneaology
https://www.garlic.com/~lynn/98.html#47 Multics and the PC
https://www.garlic.com/~lynn/99.html#37 why is there an "@" key?
https://www.garlic.com/~lynn/99.html#39 Internet and/or ARPANET?
https://www.garlic.com/~lynn/99.html#41 A word processor from 1960
https://www.garlic.com/~lynn/99.html#76 Mainframes at Universities
https://www.garlic.com/~lynn/99.html#119 Computer, supercomputers & related
https://www.garlic.com/~lynn/99.html#126 Dispute about Internet's origins
https://www.garlic.com/~lynn/99.html#127 Dispute about Internet's origins
https://www.garlic.com/~lynn/99.html#130 early hardware
https://www.garlic.com/~lynn/99.html#142 OS/360 (and descendants) VM system?
https://www.garlic.com/~lynn/2000.html#81 Ux's good points.
https://www.garlic.com/~lynn/2000c.html#30 internal corporate network, misc.
https://www.garlic.com/~lynn/2000d.html#30 Secure Operating Systems
https://www.garlic.com/~lynn/2000e.html#0 What good and old text formatter are there ?
https://www.garlic.com/~lynn/2000e.html#16 First OS with 'User' concept?
https://www.garlic.com/~lynn/2000f.html#30 OT?
https://www.garlic.com/~lynn/2000f.html#58 360 Architecture, Multics, ... was (Re: X86 ultimate CISC? No.)
https://www.garlic.com/~lynn/2000f.html#66 360 Architecture, Multics, ... was (Re: X86 ultimate CISC? No.)
https://www.garlic.com/~lynn/2000f.html#78 TSS ancient history, was X86 ultimate CISC? designs)
https://www.garlic.com/~lynn/2000g.html#12 360 Architecture, Multics, ... was (Re: X86 ultimate CISC? No.)
https://www.garlic.com/~lynn/2001e.html#69 line length (was Re: Babble from "JD" <dyson@jdyson.com>)
https://www.garlic.com/~lynn/2001h.html#9 VM: checking some myths.
https://www.garlic.com/~lynn/2001h.html#10 VM: checking some myths.
https://www.garlic.com/~lynn/2001h.html#26 TECO Critique
https://www.garlic.com/~lynn/2001h.html#34 D
https://www.garlic.com/~lynn/2001h.html#46 Whom Do Programmers Admire Now???

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

Net banking, is it safe???

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Net banking, is it safe???
Newsgroups: comp.security.misc
Date: Fri, 24 Aug 2001 04:04:35 GMT

the issue in the current (real) ATM world is that the magstripe & (shared-secret) PIN works in a secure financial network. Translation to an insecure network requires elimination of the shared-secret (possible with public key and the PIN just is known by the hardware token/card).

You obviously wouldn't want to supply this to people that find real ATMs incomprehensible. However, for the population that are able to deal with ATMs ... a PC with hardware token that had an ATM look&feel wouldn't be difficult (i.e. it is possible to also have all kinds of stories about people that are unable to deal with real ATMs).

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

Net banking, is it safe???

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Net banking, is it safe???
Newsgroups: comp.security.misc
Date: Fri, 24 Aug 2001 04:20:09 GMT

This is further aggravated that anybody with any online presence at all has multiple online relationships each with their own unique (shared-secret) password ... which becomes a personal nightmare (as well as an infrastructure nightmare).

one of the issues with regards to RADIUS that on an account by account basis, the account authentication by be selected ... userid/password where appropriate and public key (possibly implemented with hardware token) where appropriate.

Being able to have a single (non-shared-secret) PIN for a hardware token ... and the same hardware token used to authenticated all online relationships is significantly easier than unique userid/passwords for each.

So the issue is user friendly software that hides all the public key gorp from the person. Very straight-forward is to hide all the browswer public key stuff inside some applet (whether software or hardware token). Some of the customer support costs that I've seen associated with passwords problems easily support such an applet, and in some cases support both an applet as well as the cost of a hardware token.

following is from postings
https://www.garlic.com/~lynn/aepay3.htm#passwords
Password problems account for 20-50% of all calls to help desks, costing about a million dollars per year for a typical mid-sized company. About time we start taking the human factors of security seriously.

Passwords don't work: except for certain circus performers, nobody can remember a large number of random strings. And yet, how many security groups include a usability expert? (New York Times article: access requires free registration.). (August 5)

random password refs:
https://www.garlic.com/~lynn/aadsm2.htm#inetpki A PKI for the Internet (was RE: Scale (and the SRV
https://www.garlic.com/~lynn/aadsm2.htm#account A different architecture? (was Re: certificate path
https://www.garlic.com/~lynn/aadsm2.htm#straw AADS Strawman
https://www.garlic.com/~lynn/aadsm2.htm#keyl4 On leaving the 56-bit key length limitation
https://www.garlic.com/~lynn/aadsm2.htm#pkikrb PKI/KRB
https://www.garlic.com/~lynn/aadsm3.htm#cstech cardtech/securetech & CA PKI
https://www.garlic.com/~lynn/aadsm3.htm#cstech2 cardtech/securetech & CA PKI
https://www.garlic.com/~lynn/aadsm3.htm#cstech4 cardtech/securetech & CA PKI
https://www.garlic.com/~lynn/aadsm3.htm#cstech5 cardtech/securetech & CA PKI
https://www.garlic.com/~lynn/aadsm3.htm#cstech6 cardtech/securetech & CA PKI
https://www.garlic.com/~lynn/aadsm3.htm#cstech8 cardtech/securetech & CA PKI
https://www.garlic.com/~lynn/aadsm3.htm#cstech10 cardtech/securetech & CA PKI
https://www.garlic.com/~lynn/aadsm3.htm#cstech13 cardtech/securetech & CA PKI
https://www.garlic.com/~lynn/aadsm3.htm#kiss1 KISS for PKIX. (Was: RE: ASN.1 vs XML (used to be RE: I-D ACTION :draft-ietf-pkix-scvp- 00.txt))
https://www.garlic.com/~lynn/aadsm3.htm#kiss2 Common misconceptions, was Re: KISS for PKIX. (Was: RE: ASN.1 vs XML (used to be RE: I-D ACTION :draft-ietf-pkix-scvp-00.txt))
https://www.garlic.com/~lynn/aadsm3.htm#kiss3 KISS for PKIX. (Was: RE: ASN.1 vs XML (used to be RE: I-D ACTION :draft-ietf-pkix-scvp- 00.txt))
https://www.garlic.com/~lynn/aadsm3.htm#kiss8 KISS for PKIX
https://www.garlic.com/~lynn/aadsm3.htm#kiss9 KISS for PKIX .... password/digital signature
https://www.garlic.com/~lynn/aadsm4.htm#00 Is The Public Key Infrastructure Outdated?
https://www.garlic.com/~lynn/aadsm5.htm#shock2 revised Shocking Truth about Digital Signatures
https://www.garlic.com/~lynn/aadsm5.htm#spki Simple PKI
https://www.garlic.com/~lynn/aadsm5.htm#spki4 Simple PKI
https://www.garlic.com/~lynn/aadsmore.htm#keytext proposed key usage text
https://www.garlic.com/~lynn/aadsmore.htm#killer1 Killer PKI Applications
https://www.garlic.com/~lynn/aadsmore.htm#biosigs biometrics and electronic signatures
https://www.garlic.com/~lynn/aadsmore.htm#client4 Client-side revocation checking capability
https://www.garlic.com/~lynn/aepay2.htm#privrule3 U.S. firms gird for privacy rules
https://www.garlic.com/~lynn/aepay3.htm#passwords Passwords don't work
https://www.garlic.com/~lynn/aepay4.htm#dnsinteg1 Domain Name integrity problem
https://www.garlic.com/~lynn/aepay6.htm#ecml Electronic Commerce Modeling Language
https://www.garlic.com/~lynn/aepay7.htm#ssexploit Shared-Secret exploit
https://www.garlic.com/~lynn/ansiepay.htm#privacy more on privacy
https://www.garlic.com/~lynn/ansiepay.htm#ifraud Internet Fraud
https://www.garlic.com/~lynn/99.html#52 Enter fonts (was Re: Unix case-sensitivity: how did it originate?
https://www.garlic.com/~lynn/99.html#172 checks (was S/390 on PowerPC?)
https://www.garlic.com/~lynn/99.html#173 checks (was S/390 on PowerPC?)
https://www.garlic.com/~lynn/99.html#235 Attacks on a PKI
https://www.garlic.com/~lynn/2000.html#33 SmartCard with ECC crypto
https://www.garlic.com/~lynn/2000.html#47 TLS: What is the purpose of the client certificate request?
https://www.garlic.com/~lynn/2000.html#57 RealNames hacked. Firewall issues.
https://www.garlic.com/~lynn/2000b.html#14 Will Radius be obsolute if implement 2-token authentications?
https://www.garlic.com/~lynn/2000b.html#29 20th March 2000
https://www.garlic.com/~lynn/2000b.html#46 Simple authentication protocol: any good?
https://www.garlic.com/~lynn/2000b.html#53 Digital Certificates-Healthcare Setting
https://www.garlic.com/~lynn/2000b.html#90 Question regarding authentication implementation
https://www.garlic.com/~lynn/2000b.html#92 Question regarding authentication implementation
https://www.garlic.com/~lynn/2000c.html#32 Request for review of "secure" storage scheme
https://www.garlic.com/~lynn/2000d.html#70 When the Internet went private
https://www.garlic.com/~lynn/2000f.html#1 Why trust root CAs ?
https://www.garlic.com/~lynn/2000f.html#4 Why trust root CAs ?
https://www.garlic.com/~lynn/2001c.html#8 Server authentication
https://www.garlic.com/~lynn/2001c.html#9 Server authentication
https://www.garlic.com/~lynn/2001c.html#30 PKI and Non-repudiation practicalities
https://www.garlic.com/~lynn/2001c.html#39 PKI and Non-repudiation practicalities
https://www.garlic.com/~lynn/2001c.html#42 PKI and Non-repudiation practicalities
https://www.garlic.com/~lynn/2001c.html#45 PKI and Non-repudiation practicalities
https://www.garlic.com/~lynn/2001c.html#65 Key Recovery System/Product
https://www.garlic.com/~lynn/2001d.html#20 What is PKI?
https://www.garlic.com/~lynn/2001d.html#21 What is PKI?
https://www.garlic.com/~lynn/2001d.html#51 OT Re: A beautiful morning in AFM.
https://www.garlic.com/~lynn/2001d.html#52 OT Re: A beautiful morning in AFM.
https://www.garlic.com/~lynn/2001d.html#53 April Fools Day
https://www.garlic.com/~lynn/2001d.html#62 OT Re: A beautiful morning in AFM.
https://www.garlic.com/~lynn/2001d.html#73 Rational basis for password policy?
https://www.garlic.com/~lynn/2001e.html#32 Blame it all on Microsoft
https://www.garlic.com/~lynn/2001e.html#52 Pre ARPAnet email?
https://www.garlic.com/~lynn/2001e.html#81 Passwords
https://www.garlic.com/~lynn/2001g.html#1 distributed authentication
https://www.garlic.com/~lynn/2001g.html#11 FREE X.509 Certificates
https://www.garlic.com/~lynn/2001g.html#38 distributed authentication
https://www.garlic.com/~lynn/2001g.html#40 Self-Signed Certificate
https://www.garlic.com/~lynn/2001h.html#7 PKI/Digital signature doesn't work
https://www.garlic.com/~lynn/2001h.html#75 Net banking, is it safe???
https://www.garlic.com/~lynn/2001i.html#9 Net banking, is it safe???
https://www.garlic.com/~lynn/2001i.html#25 Net banking, is it safe???
https://www.garlic.com/~lynn/2001i.html#26 No Trusted Viewer possible?

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

IBM OS Timeline?

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: IBM OS Timeline?
Newsgroups: bit.listserv.ibm-main,alt.folklore.computers
Date: Fri, 24 Aug 2001 15:41:34 GMT

One bug I remember having to shoot & fix was OPEN failure on BDAM file ... the BDAM options were just slightly different than anything that they had previously used.

later after I joined ibm, i remember being in pok (705?) machine room 3rd shift with don ludlow testing initial work on SVS. He had cobbled together an MVT system with a version of CCWTRANS from CP/67 (CCWTRANS was the CP/67 module that handled the virtual->real CCW translation, page fixing for I/O transfers, etc ... aka a lot of the work involved in adding virtual memory support to OS/MVT involved copying and/or integrating code from CP/67).

random refs;
https://www.garlic.com/~lynn/94.html#21 370 ECPS VM microcode assist
https://www.garlic.com/~lynn/94.html#33 short CICS story
https://www.garlic.com/~lynn/94.html#35 mainframe CKD disks & PDS files (looong... warning)
https://www.garlic.com/~lynn/96.html#9 cics
https://www.garlic.com/~lynn/97.html#6 IBM Hursley?
https://www.garlic.com/~lynn/97.html#8 Ancient DASD
https://www.garlic.com/~lynn/97.html#30 How is CICS pronounced?
https://www.garlic.com/~lynn/98.html#33 ... cics ... from posting from another list
https://www.garlic.com/~lynn/98.html#34 ... cics ... from posting from another list
https://www.garlic.com/~lynn/99.html#58 When did IBM go object only
https://www.garlic.com/~lynn/99.html#130 early hardware
https://www.garlic.com/~lynn/99.html#218 Mainframe acronyms: how do you pronounce them?
https://www.garlic.com/~lynn/2000.html#68 Mainframe operating systems
https://www.garlic.com/~lynn/2000b.html#41 How to learn assembler language for OS/390 ?
https://www.garlic.com/~lynn/2000c.html#34 What level of computer is needed for a computer to Love?
https://www.garlic.com/~lynn/2000c.html#35 What level of computer is needed for a computer to Love?
https://www.garlic.com/~lynn/2000c.html#45 Does the word "mainframe" still have a meaning?
https://www.garlic.com/~lynn/2000c.html#52 Does the word "mainframe" still have a meaning?
https://www.garlic.com/~lynn/2000c.html#54 WHAT IS A MAINFRAME???
https://www.garlic.com/~lynn/2000f.html#69 TSS ancient history, was X86 ultimate CISC? designs)
https://www.garlic.com/~lynn/2001.html#51 Competitors to SABRE?
https://www.garlic.com/~lynn/2001.html#62 California DMV
https://www.garlic.com/~lynn/2001b.html#18 Linux IA-64 interrupts [was Re: Itanium benchmarks ...]
https://www.garlic.com/~lynn/2001d.html#56 Pentium 4 Prefetch engine?
https://www.garlic.com/~lynn/2001d.html#69 Block oriented I/O over IP
https://www.garlic.com/~lynn/2001f.html#2 Mysterious Prefixes
https://www.garlic.com/~lynn/2001g.html#24 XML: No More CICS?

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

IBM OS Timeline?

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: IBM OS Timeline?
Newsgroups: bit.listserv.ibm-main,alt.folklore.computers
Date: Fri, 24 Aug 2001 15:41:34 GMT

One bug I remember having to shoot & fix was OPEN failure on BDAM file ... the BDAM options were just slightly different than anything that they had previously used.

later after I joined ibm, i remember being in pok (705?) machine room 3rd shift with don ludlow testing initial work on SVS. He had cobbled together an MVT system with a version of CCWTRANS from CP/67 (CCWTRANS was the CP/67 module that handled the virtual->real CCW translation, page fixing for I/O transfers, etc ... aka a lot of the work involved in adding virtual memory support to OS/MVT involved copying and/or integrating code from CP/67).

random refs;
https://www.garlic.com/~lynn/94.html#21 370 ECPS VM microcode assist
https://www.garlic.com/~lynn/94.html#33 short CICS story
https://www.garlic.com/~lynn/94.html#35 mainframe CKD disks & PDS files (looong... warning)
https://www.garlic.com/~lynn/96.html#9 cics
https://www.garlic.com/~lynn/97.html#6 IBM Hursley?
https://www.garlic.com/~lynn/97.html#8 Ancient DASD
https://www.garlic.com/~lynn/97.html#30 How is CICS pronounced?
https://www.garlic.com/~lynn/98.html#33 ... cics ... from posting from another list
https://www.garlic.com/~lynn/98.html#34 ... cics ... from posting from another list
https://www.garlic.com/~lynn/99.html#58 When did IBM go object only
https://www.garlic.com/~lynn/99.html#130 early hardware
https://www.garlic.com/~lynn/99.html#218 Mainframe acronyms: how do you pronounce them?
https://www.garlic.com/~lynn/2000.html#68 Mainframe operating systems
https://www.garlic.com/~lynn/2000b.html#41 How to learn assembler language for OS/390 ?
https://www.garlic.com/~lynn/2000c.html#34 What level of computer is needed for a computer to Love?
https://www.garlic.com/~lynn/2000c.html#35 What level of computer is needed for a computer to Love?
https://www.garlic.com/~lynn/2000c.html#45 Does the word "mainframe" still have a meaning?
https://www.garlic.com/~lynn/2000c.html#52 Does the word "mainframe" still have a meaning?
https://www.garlic.com/~lynn/2000c.html#54 WHAT IS A MAINFRAME???
https://www.garlic.com/~lynn/2000f.html#69 TSS ancient history, was X86 ultimate CISC? designs)
https://www.garlic.com/~lynn/2001.html#51 Competitors to SABRE?
https://www.garlic.com/~lynn/2001.html#62 California DMV
https://www.garlic.com/~lynn/2001b.html#18 Linux IA-64 interrupts [was Re: Itanium benchmarks ...]
https://www.garlic.com/~lynn/2001d.html#56 Pentium 4 Prefetch engine?
https://www.garlic.com/~lynn/2001d.html#69 Block oriented I/O over IP
https://www.garlic.com/~lynn/2001f.html#2 Mysterious Prefixes
https://www.garlic.com/~lynn/2001g.html#24 XML: No More CICS?

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

IBM OS Timeline?

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: IBM OS Timeline?
Newsgroups: bit.listserv.ibm-main,alt.folklore.computers
Date: Fri, 24 Aug 2001 21:17:09 GMT

remember, for most of its lifetime, cambridge was about 35 people, during the cp/40, cp/67 days maybe only 20.

they did cp/40, cms, cp/67, the stuff that was the internal network (largest network in the world until internet started to overtake it in the middle to late '80s), script, gml (which morphed into sgml, and then at cern, html, and now xml), editors, word processing, timesharing, multiprocessing support, the compare&swap instruction, apl ported to virtual memory environment (including rewrite of apl storage mechanism for virtual memory), early performance tuning work, some of the earliest work on transition of performance tuning into capacity planning, the performance perdictor (tool on HONE, that field used that profiled customer configuration, application, operationgs, & workload, and was able to do what-if questions regarding changes, new hardware, etc).

by comparison, both tss/360 and various flavors of OS/360 numbered in the thousands (I think i once heard that tss/360 at mohansic and other places may have totaled 1200).

random refs:
https://www.leeandmelindavarian.com/Melinda#VMHist
https://www.garlic.com/~lynn/subtopic.html#wsclock
https://www.garlic.com/~lynn/subtopic.html#fairshare
https://www.garlic.com/~lynn/subtopic.html#smp
https://www.garlic.com/~lynn/subtopic.html#hone
https://www.garlic.com/~lynn/submain.html#mmap
https://www.garlic.com/~lynn/submain.html#360pcm
https://www.garlic.com/~lynn/submain.html#360mcode
https://www.garlic.com/~lynn/subtopic.html#disk
https://www.garlic.com/~lynn/subnetwork.html#internet
https://www.garlic.com/~lynn/internet.htm

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

IBM OS Timeline?

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: IBM OS Timeline?
Newsgroups: bit.listserv.ibm-main,alt.folklore.computers
Date: Sat, 25 Aug 2001 04:00:21 GMT

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

Withdrawal Announcement 901-218 - No More 'small machines'

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Withdrawal Announcement 901-218 - No More 'small machines'
Newsgroups: bit.listserv.ibm-main,alt.folklore.computers
Date: Sat, 25 Aug 2001 13:32:35 GMT

later we ran skunk works responsible for HSDT and HA/CMP ... we also coined the term disaster survivability (as opposed to disaster recovery) and geographic survivability for geographic clusters (all pre-dating the other unix clusters). During this period we got to co-author part of the corporate continuous availability strategy document ... but both rochester and POK non-concurred on the section we wrote.

during our early days of working on ha/cmp ... various of current prime proponets of clusters were some of our staunchest adversaries.

random refs:
https://www.garlic.com/~lynn/95.html#13
https://www.garlic.com/~lynn/99.html#71
https://www.garlic.com/~lynn/2001.html#33
https://www.garlic.com/~lynn/2001g.html#46

https://www.garlic.com/~lynn/subtopic.html#hacmp
https://www.garlic.com/~lynn/subtopic.html#hone
https://www.garlic.com/~lynn/subnetwork.html#hsdt
https://www.garlic.com/~lynn/subtopic.html#fairshare

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

Question re: Size of Swap File

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Question re: Size of Swap File
Newsgroups: alt.security.pgp,alt.computer.security
Date: Sat, 25 Aug 2001 13:59:17 GMT

one of the issues is dup or no-dup algorithm. many algorithms effectively duplicate pages in memory and on disk. on large number of big memory systems, a no-dup algorithm can be useful; whenever a page is brought in, it is removed from disk allocation. The downside of a no-dup algorithm is whenever a page is selected for replacement ... it always is written to (a new) disk location. A "dup" algorithm, when a page has been selected for replacement and it hasn't been changed since it was last read from disk ... it doesn't have to be written back to disk.

Say you have 1gbyte of real storage and 1.5gbyte of allocated virtual memory in various running applications. In a "dup" strategy, you need at least 1.5gbyte of disk space to hold total virtual memory of all your concurrently active applications. In a no-dup strategy, you would only need enuf disk space to hold the virtual pages that weren't currently resident in memory aka 1.5gbyte total minus (about) 1gbyte of virtual pages resident in storage ... or about 500mbytes.

basically, some of the guidelines assume some rule about the number of concurrently active applications might be proportional to the amount of real storage (and a "duplicate" allocation algorithm). However, real environments can vary from total amount of virtual storage is less than real storage (in which case a no-dup strategy wouldn't require any allocated space on disk) to ten times or more the amount of real storage. In actual fact, the total amount of virtual storage in concurrently active applications can have little correlation to the amount of real storage.

and of course ... application/system storage cancers in operations that stay up for long periods of time w/o rebooting can result in constantly increasing amount of disk storage requirements for virtual memory

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

Withdrawal Announcement 901-218 - No More 'small machines'

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Withdrawal Announcement 901-218 - No More 'small machines'
Newsgroups: bit.listserv.ibm-main,alt.folklore.computers
Date: Sat, 25 Aug 2001 14:30:11 GMT

I think starting with the 370m115 & 370m125, machines couldn't be ordered w/o first being run thru a HONE "configurator".

HONE was a massive, world-wide VM/370 infrastructure with the majority of the applications starting out cms\apl and then ported to apl\cms.

The first HONE environment was CP/67 running on 360m67s for all US field people. In addition to various apl and fortran applications, it also provided various flavors of the "H" system ... specifically modified version of CP/67 that provided both non-relocate and relocate virtual machines (i.e. CP/67 modified to simulate new 370 instructions and architecture).

There were several (US) HONE locations, but in 1977 they were all consolidated in Palo Alto (largest single-system operation in the world, effectively an early "sysplex" type operation with advanced workload & recovery management across the complex). Then starting around 1979, the Palo Alto complex was replicated in Dallas and Boulder for disaster survivability.

When EMEA hdqtrs moved to La Defense in the early '70s, I hand-carried a copy of HONE and installed it. I also hand-carried & installed initial HONE operation in Tokyo and some number of other locations.

as above URL refs
https://www.garlic.com/~lynn/subtopic.html#hone

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

Withdrawal Announcement 901-218 - No More 'small machines'

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Withdrawal Announcement 901-218 - No More 'small machines'
Newsgroups: bit.listserv.ibm-main,alt.folklore.computers
Date: Sat, 25 Aug 2001 14:56:52 GMT

For cms\apl, cambridge also added a bunch of system call operators. This violated the purity of APL and there was big arguments about cms\apl (but you could write applications that munged real-world data). Possibly, one of the biggest changes going to apl\cms was the "shared variables" which was able to encapsulate all system infrastructure characteristics ... but in an APL pure way.

The CSC CP/67 time-sharing service (as opposed to the CSC system research & development, word/document processing research & development, etc ... especially since this was still all included in the 20-35 total headcount at CSC) became an interesting operation with a user community that spanned MIT students, researchers, and corporate planners. The forecasting and planning data for the corporate financial models was possibly among the highest guarded data in the company. Being able to provide that level of security and still allow relative free use by MIT students and researchers was an interesting challenge.

random refs:
https://www.garlic.com/~lynn/2001i.html#30 IBM OS Timeline?
https://www.garlic.com/~lynn/2001i.html#32 IBM OS Timeline?
https://www.garlic.com/~lynn/2001i.html#34 IBM OS Timeline?
https://www.garlic.com/~lynn/2001i.html#37 IBM OS Timeline?
https://www.garlic.com/~lynn/2001i.html#38 IBM OS Timeline?
https://www.garlic.com/~lynn/2001i.html#39 IBM OS Timeline?
https://www.garlic.com/~lynn/2001i.html#40 IBM OS Timeline?

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

Withdrawal Announcement 901-218 - No More 'small machines'

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Withdrawal Announcement 901-218 - No More 'small machines'
Newsgroups: alt.folklore.computers
Date: Sat, 25 Aug 2001 15:54:57 GMT

intro to apl\360 user's manaul, 1968 (I found in one of my boxes)
https://www.garlic.com/~lynn/2001.html#2 A new "Remember when?" period happening right now

:-)

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

Withdrawal Announcement 901-218 - No More 'small machines'

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Withdrawal Announcement 901-218 - No More 'small machines'
Newsgroups: bit.listserv.ibm-main,alt.folklore.computers
Date: Sat, 25 Aug 2001 16:43:28 GMT

The single-system image workload manager for palo alto had to worry about the large disk farm as well as cpu resources. One of the big issues in workload manager across a large number of processors was disk arm contention ... with disk intensive applications.

All requests for a specific disk arm within the same CEC (processors sharing the same real memory) could have the ordering optimize to maximize disk thruput. However with a large number of CECs all sharing the same disk farm, disk arm optimization could degenerate to random ... because of large number of interleaving disk requests from a large number of different CECs (i.e. disk arm queuing was performed at the CEC level not at the controller or disk level).

Even tho APL applications tended to be serverly CPU constrained (for various implementation efficiency reasons as well as the nature of many of the applications) ... there were still a quite a bit of heavy disk intensive operations in a HONE complex.

As a result, the workload manager had to trade-off clustering majority of users that tended to have clustered disk access to the similar set of disk arms (to maximize disk arm optimization) against CPU utilization workload distribution across different CECs. This was further aggravated by the time-zone working effect i.e. all of the US was sharing the same complex, however there tended to be very distinct daytime workload peaks by timezone. The sales, branch and field people in the same region might have similar disk arm clustering access patterns but would also peak their cpu utilization at similar times of the day ... so the workload manager was faced with trade-off between load-balancing cpu utilization against the downside of non-optimal disk arm thruputs.

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

Withdrawal Announcement 901-218 - No More 'small machines'

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Withdrawal Announcement 901-218 - No More 'small machines'
Newsgroups: alt.folklore.computers
Date: Sat, 25 Aug 2001 16:45:45 GMT

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

Withdrawal Announcement 901-218 - No More 'small machines'

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Withdrawal Announcement 901-218 - No More 'small machines'
Newsgroups: bit.listserv.ibm-main,alt.folklore.computers
Date: Sat, 25 Aug 2001 18:31:19 GMT

we also slightly tweaked the system/88 (i.e. logo'ed stratus) folks .. since they were also single site availability ... and at the time non-clustered and the operating system was non-hot-servicable; aka the 1-800 system had guideline of 5 minutes of downtime per year (around five nines) and had been s/88 (or status) ... but any operating system service required minimum of 30 minute outage.

the SS7 already had fully redundant hardware and replicated T1s coming out of the back to the 1-800 service (along with logic that would drive a request down the alternate T1 to mask things like T1/communications failures). Putting a replicated clustered configuration on the back of the SS7 T1s ... would rely on the SS7 T1-fault masking logic to also mask backend fault ... and it would allow operating system, database & application "hot" serviceability. At the time, system/88 would have needed replicated boxes on the back of the T1s to support hot operating system maintenance ... but there was little total system availability difference between a pair of replicated ha/cmp boxes and a pair of system/88 boxes (in the 1-800 scenerio) .... aka taking advantage of the fault-masking logic in the SS7 effectively made much of the s/88 redundancy superfluous.

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

Withdrawal Announcement 901-218 - No More 'small machines'

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Withdrawal Announcement 901-218 - No More 'small machines'
Newsgroups: bit.listserv.ibm-main,alt.folklore.computers
Date: Sat, 25 Aug 2001 19:06:56 GMT

HAWMS Status report - October 18, 1991

The HAWMS Study team met at 9am EDT on October 18, 1991
to review the status of the project.

Attending:    Stu Vwx
Abc Def (by phone from LaGaude)
Ghi Jkl (by phone from LaGaude)
Mno Pqr

Vwx covered the results of Xyz-san's meeting with the RS/6000 product
owner in Japan.  (See text of Vwx's note at the bottom of this note.)
The main point to come out of the meeting is the that HA/6000 is not
seen as a viable solution for the OLTP marketplace without CICS/AIX.

Vwx also asked the other members of the team to assess the new version
of the AP Continuous Availability Major Comparisons chart which has
been expanded to include the HA/6000 in addition to the ES/9000, S/88,
and Tandem.

Def met with Bgo earlier this week and Bgo's comments were similar to
those of the RS/6000 product owner in Japan.  He stated that the Fault
Tolerant marketplace is mainly an OLTP market and that the HA/6000
must have a transaction manager such as CICS/AIX in order to compete.

The meeting with Lynn Wheeler will be held in Gaithersburg the week
of November 11.  Lynn will be in Hong Kong the week of October 28, and
in Australia the week of November 4.  The exact date and location of
this meeting will be included in next week's report.

The next checkpoint will be taken on October 25 at 9am EDT.

I hate Compaq

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: I hate Compaq
Newsgroups: comp.arch
Date: Sun, 26 Aug 2001 20:04:53 GMT

however, as far as contracts ... most states have aligned themselves with UCC (uniform commercial code).

http://www.law.cornell.edu/ucc/ucc.table.html
ARTICLE 1. GENERAL PROVISIONS

ARTICLE 2. SALES

ARTICLE 2A. LEASES

ARTICLE 3. NEGOTIABLE INSTRUMENTS

ARTICLE 4. BANK DEPOSITS AND COLLECTIONS

ARTICLE 4A. FUNDS TRANSFERS

ARTICLE 5. LETTERS OF CREDIT

ARTICLE 6. BULK TRANSFERS and [REVISED] - BULK SALES

ARTICLE 7. WAREHOUSE RECEIPTS, BILLS OF LADING AND OTHER DOCUMENTS OF TITLE

ARTICLE 8. INVESTMENT SECURITIES

ARTICLE 9. SECURED TRANSACTIONS; SALES OF ACCOUNTS AND CHATTEL PAPER


http://www.law.cornell.edu/ucc/3/3-303
§ 3-303. VALUE AND CONSIDERATION.

(a) An instrument is issued or transferred for value if: (1) the instrument is issued or transferred for a promise of performance, to the extent the promise has been performed; (2) the transferee acquires a security interest or other lien in the instrument other than a lien obtained by judicial proceeding; (3) the instrument is issued or transferred as payment of, or as security for, an antecedent claim against any person, whether or not the claim is due; (4) the instrument is issued or transferred in exchange for a negotiable instrument; or (5) the instrument is issued or transferred in exchange for the incurring of an irrevocable obligation to a third party by the person taking the instrument.

(b) "Consideration" means any consideration sufficient to support a simple contract. The drawer or maker of an instrument has a defense if the instrument is issued without consideration. If an instrument is issued for a promise of performance, the issuer has a defense to the extent performance of the promise is due and the promise has not been performed. If an instrument is issued for value as stated in subsection (a), the instrument is also issued for consideration.

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

DARPA was: Short Watson Biography

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: DARPA was: Short Watson Biography
Newsgroups: alt.folklore.computers
Date: Mon, 27 Aug 2001 03:14:29 GMT

past ref from this newsgroup:
https://www.garlic.com/~lynn/2000e.html#32 Tektronic Storage Tube Terminal

it was produced in POK by the same guy responsible for the A74
https://www.garlic.com/~lynn/2000e.html#55 Why not an IBM zSeries workstation?
https://www.garlic.com/~lynn/2000e.html#56 Why not an IBM zSeries workstation?
https://www.garlic.com/~lynn/2001i.html#19 Very CISC Instuctions (Was: why the machine word size ...)

--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/

misc loosely-coupled, sysplex, cluster, supercomputer, & electronic commerce

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: misc loosely-coupled, sysplex, cluster, supercomputer, & electronic commerce
Newsgroups: bit.listserv.ibm-main,alt.folklore.computers
Date: Mon, 27 Aug 2001 23:54:03 GMT

loosely-coupled & sysplex
https://www.garlic.com/~lynn/98.html#30 Drive letters
https://www.garlic.com/~lynn/98.html#35a Drive letters
https://www.garlic.com/~lynn/98.html#37 What is MVS/ESA?
https://www.garlic.com/~lynn/98.html#40 Comparison Cluster vs SMP?
https://www.garlic.com/~lynn/99.html#71 High Availabilty on S/390
https://www.garlic.com/~lynn/99.html#100 Why won't the AS/400 die? Or, It's 1999 why do I have to learn how to use
https://www.garlic.com/~lynn/99.html#128 Examples of non-relational databases
https://www.garlic.com/~lynn/2000.html#13 Computer of the century
https://www.garlic.com/~lynn/2000f.html#30 OT?
https://www.garlic.com/~lynn/2000f.html#37 OT?
https://www.garlic.com/~lynn/2001b.html#73 7090 vs. 7094 etc.
https://www.garlic.com/~lynn/2001c.html#69 Wheeler and Wheeler
https://www.garlic.com/~lynn/2001d.html#71 Pentium 4 Prefetch engine?
https://www.garlic.com/~lynn/2001e.html#2 Block oriented I/O over IP
https://www.garlic.com/~lynn/2001g.html#44 The Alpha/IA64 Hybrid
https://www.garlic.com/~lynn/2001g.html#46 The Alpha/IA64 Hybrid
https://www.garlic.com/~lynn/2001h.html#76 Other oddball IBM System 360's ?

loosely-coupled, cluster & supercomputer
https://www.garlic.com/~lynn/95.html#13 SSA
https://www.garlic.com/~lynn/96.html#15 tcp/ip

loosely-coupled, cluster & electronic commerce
https://www.garlic.com/~lynn/aadsm5.htm#asrn2 assurance, e-commerce, and some x9.59 ... fyi
https://www.garlic.com/~lynn/aadsmore.htm#dctriv digital commerce trivia question
https://www.garlic.com/~lynn/95.html#13 SSA
https://www.garlic.com/~lynn/aadsm5.htm#asrn3 assurance, e-commerce, and some x9.59 ... fyi

misc posts wife doing stint in POK responsible for (mainframe) loosely-coupled (cluster) architecture
https://www.garlic.com/~lynn/submain.html#shareddata

misc posts related to ha/cmp product
https://www.garlic.com/~lynn/subtopic.html#hacmp

misc. old email on cluster scale-up
https://www.garlic.com/~lynn/lhwemail.html#medusa

misc. posts availability, disaster survivability, geographic survivability, continuous availability
https://www.garlic.com/~lynn/submain.html#available

misc. post assurance
https://www.garlic.com/~lynn/subintegrity.html#assurance

misc other, availability
https://www.garlic.com/~lynn/aadsm2.htm#availability A different architecture? (was Re: certificate path
https://www.garlic.com/~lynn/aadsm5.htm#asrn4 assurance, X9.59, etc
https://www.garlic.com/~lynn/aadsmail.htm#mfraud AADS, X9.59, security, flaws, privacy
https://www.garlic.com/~lynn/aepay2.htm#cadis disaster recovery cross-posting
https://www.garlic.com/~lynn/93.html#28 Log Structured filesystems -- think twice
https://www.garlic.com/~lynn/94.html#16 Dual-ported disks?
https://www.garlic.com/~lynn/94.html#33a High Speed Data Transport (HSDT)
https://www.garlic.com/~lynn/95.html#13 SSA
https://www.garlic.com/~lynn/96.html#15 tcp/ip
https://www.garlic.com/~lynn/96.html#31 Mainframes & Unix
https://www.garlic.com/~lynn/96.html#33 Mainframes & Unix
https://www.garlic.com/~lynn/96.html#34 Mainframes & Unix
https://www.garlic.com/~lynn/96.html#36 Mainframes & Unix (and TPF)
https://www.garlic.com/~lynn/97.html#5 360/44 (was Re: IBM 1130 (was Re: IBM 7090--used for business or
https://www.garlic.com/~lynn/98.html#23 Fear of Multiprocessing?
https://www.garlic.com/~lynn/98.html#35a Drive letters
https://www.garlic.com/~lynn/98.html#37 What is MVS/ESA?
https://www.garlic.com/~lynn/98.html#40 Comparison Cluster vs SMP?
https://www.garlic.com/~lynn/98.html#49 Edsger Dijkstra: the blackest week of his professional life
https://www.garlic.com/~lynn/98.html#57 Reliability and SMPs
https://www.garlic.com/~lynn/99.html#54 Fault Tolerance
https://www.garlic.com/~lynn/99.html#67 System/1 ?
https://www.garlic.com/~lynn/99.html#145 Q: S/390 on PowerPC?
https://www.garlic.com/~lynn/99.html#184 Clustering systems
https://www.garlic.com/~lynn/99.html#219 Study says buffer overflow is most common security bug
https://www.garlic.com/~lynn/2000b.html#45 OSA-Express Gigabit Ethernet card planning
https://www.garlic.com/~lynn/2000b.html#85 Mainframe power failure (somehow morphed from Re: write rings)
https://www.garlic.com/~lynn/2000e.html#22 Is a VAX a mainframe?
https://www.garlic.com/~lynn/2000f.html#30 OT?
https://www.garlic.com/~lynn/2000f.html#31 OT?
https://www.garlic.com/~lynn/2000g.html#27 Could CDR-coding be on the way back?
https://www.garlic.com/~lynn/2001.html#33 Where do the filesystem and RAID system belong?
https://www.garlic.com/~lynn/2001.html#34 Competitors to SABRE?
https://www.garlic.com/~lynn/2001.html#41 Where do the filesystem and RAID system belong?
https://www.garlic.com/~lynn/2001c.html#66 KI-10 vs. IBM at Rutgers
https://www.garlic.com/~lynn/2001c.html#69 Wheeler and Wheeler
https://www.garlic.com/~lynn/2001d.html#71 Pentium 4 Prefetch engine?
https://www.garlic.com/~lynn/2001e.html#2 Block oriented I/O over IP
https://www.garlic.com/~lynn/2001e.html#4 Block oriented I/O over IP
https://www.garlic.com/~lynn/2001e.html#41 Where are IBM z390 SPECint2000 results?
https://www.garlic.com/~lynn/2001g.html#23 IA64 Rocks My World
https://www.garlic.com/~lynn/2001g.html#44 The Alpha/IA64 Hybrid
https://www.garlic.com/~lynn/2001g.html#46 The Alpha/IA64 Hybrid
https://www.garlic.com/~lynn/2001i.html#31 3745 and SNI
https://www.garlic.com/~lynn/2001i.html#41 Withdrawal Announcement 901-218 - No More 'small machines'
https://www.garlic.com/~lynn/2001i.html#43 Withdrawal Announcement 901-218 - No More 'small machines'
https://www.garlic.com/~lynn/2001i.html#46 Withdrawal Announcement 901-218 - No More 'small machines'
https://www.garlic.com/~lynn/2001i.html#48 Withdrawal Announcement 901-218 - No More 'small machines'
https://www.garlic.com/~lynn/2001i.html#49 Withdrawal Announcement 901-218 - No More 'small machines'

--
Anne & Lynn Wheeler | lynn@garlic.com, https://www.garlic.com/~lynn/

Credit Card # encryption

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Credit Card # encryption
Newsgroups: sci.crypt
Date: Wed, 29 Aug 2001 15:36:11 GMT

..... as per
It was never even a minor purpose of the SET specification work to eliminate credit card numbers from being known by the merchant.

The fact that the merchant does not see the account number on the way to the payment gateway was touted by some as a benefit of the system, but it was a side effect of the design. There was never a stated (or even implied) requirement to hide the account number from the merchant.

posted Fri, 7 May 1999, 14.59.11 -0700 to ansi-epay@lists.commerce.net by tlewis@xxxxxxxx

random refs
https://www.garlic.com/~lynn/aepay7.htm#nonrep5
http://lists.commerce.net/archives/ansi-epay/199905/msg00009.html
https://web.archive.org/web/20020225023945/http://lists.commerce.net/archives/ansi-epay/199905/msg00009.html
https://www.garlic.com/~lynn/2001h.html#38
https://www.garlic.com/~lynn/2001h.html#61 security proportional to risk
https://www.garlic.com/~lynn/subpubkey.html#publickey

--
Anne & Lynn Wheeler | lynn@garlic.com, https://www.garlic.com/~lynn/

Computer security: The Future

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Computer security: The Future
Newsgroups: sci.crypt
Date: Thu, 30 Aug 2001 18:36:15 GMT

past issues from long ago and far way are network scripting exploits (i.e. like various current browser and email vulnerabilities) that I believe we identified/tracked-down sometime in the early to mid-70s.

prior to the current flurry of scripting exploits (and continuing) are the buffer overrun exploits which we claimed has been severely exhaserbated (possibly by two orders of magnitude) by the string length handling conventions in the C lanugage (compared to similar environments with better string length handling conventions).

Risk, Fraud, Exploit posts
https://www.garlic.com/~lynn/subintegrity.html#fraud

random aside ... various (security, payment, financial) glossaries
https://www.garlic.com/~lynn/index.html#glossary

--
Anne & Lynn Wheeler | lynn@garlic.com, https://www.garlic.com/~lynn/

Computer security: The Future

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: Computer security: The Future
Newsgroups: sci.crypt,comp.security.misc
Date: Sat, 01 Sep 2001 16:05:35 GMT

another was cp/67 & vm/370. random 545 comments
https://www.garlic.com/~lynn/subtopic.html#545tech

the C-somethings have now been replaced with protection profiles and common criteria

security glossary merged from (including rainbow books)
Terms merged from: AFSEC, AJP, CC1, CC2, FCv1, FIPS140, IATF IEEE610, ITSEC, Intel, JTC1/SC27/N734, KeyAll, MSC, NCSC/TG004, NIAP, RFC1983, RFC2504, RFC2828, TCSEC, TDI, TNI, and misc. Updated 20010729 with glossary from IATF V3.


https://www.garlic.com/~lynn/secure.htm

misc refs:
http://www.software.org/quagmire/frampapr/frampapr.html Framework quagmire
https://web.archive.org/web/20020220162911/http://www.software.org/pub/darpa/erd/erdpv010004.html
http://www.software.org/pub/darpa/erd/erdpv010004.html
http://www.ncca.navy.mil/software/mil-std.htm MIL-STD-498 versus DOD-STD-2167A ISSUE PAPER
http://www.radium.ncsc.mil/tpep/
http://www.radium.ncsc.mil/tpep/library/ccitse/index.html
http://www.radium.ncsc.mil/tpep/library/rainbow/
http://www.radium.ncsc.mil/tpep/library/rainbow/5200.28-STD.html
http://www.radium.ncsc.mil/tpep/whatsnew.html

random other ref:
https://www.garlic.com/~lynn/subintegrity.html#fraud

--
Anne & Lynn Wheeler | lynn@garlic.com, https://www.garlic.com/~lynn/

E-commerce security????

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: E-commerce security????
Newsgroups: comp.security,comp.security.pgp,alt.computer.security,alt.security,comp.security.unix,comp.security.linux
Date: Sun, 02 Sep 2001 02:16:17 GMT

digital commerce trivia question
https://www.garlic.com/~lynn/aadsmore.htm#dctriv digital commerce trivia question

misc connections
https://www.garlic.com/~lynn/2001i.html#52 misc. connections

random refs:
https://www.garlic.com/~lynn/subintegrity.html#fraud

--
Anne & Lynn Wheeler | lynn@garlic.com, https://www.garlic.com/~lynn/

E-commerce security????

From: Anne & Lynn Wheeler <lynn@garlic.com>
Subject: Re: E-commerce security????
Newsgroups: comp.security,comp.security.pgp,alt.computer.security,alt.security,comp.security.unix,comp.security.linux
Date: 02 Sep 2001 09:27:17 -0600

https://www.garlic.com/~lynn/

for some ancillary discussion about harvesting of credit card account number files:
https://www.garlic.com/~lynn/2001h.html#61 security proportional to risk

misc. discussions about account number harvesting:
https://www.garlic.com/~lynn/aadsm5.htm#asrn4 assurance, X9.59, etc
https://www.garlic.com/~lynn/aadsm6.htm#websecure merchant web server security
https://www.garlic.com/~lynn/aepay6.htm#harvest harvesting of credit card numbers
https://www.garlic.com/~lynn/aepay6.htm#harvest2 shared-secrets, CC#, & harvesting CC#
https://www.garlic.com/~lynn/aepay6.htm#erictalk Announce: Eric Hughes giving Stanford EE380 talk this
https://www.garlic.com/~lynn/aepay7.htm#nonrep0 non-repudiation, was Re: crypto flaw in secure mail standards
https://www.garlic.com/~lynn/aepay7.htm#nonrep1 non-repudiation, was Re: crypto flaw in secure mail standards
https://www.garlic.com/~lynn/aepay7.htm#nonrep3 non-repudiation, was Re: crypto flaw in secure mail standards
https://www.garlic.com/~lynn/aepay7.htm#nonrep4 non-repudiation, was Re: crypto flaw in secure mail standards
https://www.garlic.com/~lynn/aepay7.htm#nonrep5 non-repudiation, was Re: crypto flaw in secure mail standards
https://www.garlic.com/~lynn/aepay7.htm#nonrep6 non-repudiation, was Re: crypto flaw in secure mail standards
https://www.garlic.com/~lynn/aepay7.htm#ssexploit Shared-Secret exploit
https://www.garlic.com/~lynn/aepay7.htm#netbank net banking, is it safe?? ... power to the consumer
https://www.garlic.com/~lynn/2001c.html#42 PKI and Non-repudiation practicalities
https://www.garlic.com/~lynn/2001c.html#54 PKI and Non-repudiation practicalities
https://www.garlic.com/~lynn/2001c.html#59 PKI and Non-repudiation practicalities
https://www.garlic.com/~lynn/2001c.html#73 PKI and Non-repudiation practicalities
https://www.garlic.com/~lynn/2001d.html#19 [Newbie] Authentication vs. Authorisation?
https://www.garlic.com/~lynn/2001f.html#24 Question about credit card number
https://www.garlic.com/~lynn/2001f.html#25 Question about credit card number
https://www.garlic.com/~lynn/2001f.html#31 Remove the name from credit cards!
https://www.garlic.com/~lynn/2001f.html#52 any 70's era supercomputers that ran as slow as today's supercomputers?
https://www.garlic.com/~lynn/2001f.html#54 any 70's era supercomputers that ran as slow as today's supercomputers?
https://www.garlic.com/~lynn/2001f.html#55 any 70's era supercomputers that ran as slow as today's supercomputers?
https://www.garlic.com/~lynn/2001f.html#57 any 70's era supercomputers that ran as slow as today's supercomputers?
https://www.garlic.com/~lynn/2001g.html#0 FREE X.509 Certificates
https://www.garlic.com/~lynn/2001g.html#11 FREE X.509 Certificates
https://www.garlic.com/~lynn/2001g.html#63 PKI/Digital signature doesn't work
https://www.garlic.com/~lynn/2001h.html#5 PKI/Digital signature doesn't work
https://www.garlic.com/~lynn/2001h.html#7 PKI/Digital signature doesn't work
https://www.garlic.com/~lynn/2001h.html#37 Credit Card # encryption
https://www.garlic.com/~lynn/2001h.html#53 Net banking, is it safe???
https://www.garlic.com/~lynn/2001h.html#58 Net banking, is it safe???
https://www.garlic.com/~lynn/2001h.html#68 Net banking, is it safe???
https://www.garlic.com/~lynn/2001h.html#70 Net banking, is it safe???
https://www.garlic.com/~lynn/2001i.html#25 Net banking, is it safe???
https://www.garlic.com/~lynn/subpubkey.html#privacy X9.59, Identity, Authentication, and Privacy
https://www.garlic.com/~lynn/subintegrity.html#fraud Risk, Fraud, Exploits

--
Anne & Lynn Wheeler | lynn@garlic.com, https://www.garlic.com/~lynn/

next, previous, index - home