From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: HONE was .. Hercules and System/390 - do we need it? Newsgroups: bit.listserv.ibm-main,alt.folklore.computers Date: Thu, 11 Jul 2002 15:43:05 GMTjcmorris@mitre.org (Joe Morris) writes:
Hands-On Networking Environment ^ ^ ^ ^>Another nagging question: why APL, both in the sense of "why at all"
Some applications were written in APL and I believe the group doing
some of the applications had chosen APL and they just grew. It
eventually became a whole "padded-cell" environment (sequoia). This
then drove a lot of the applications ... included some "foreign"
applications that were recoded in fortran because of extreme
performance issues. I believe that as the body of APL applications
grew, it just built up a sort of legacy momentum. One of the extensive
uses of APL at the time were the various what-if things that you see
done in spreadsheets today.
>And some customer shops were given access to the configurator programs,
>although (obviously) not to the ordering tools. I recall using them,
>for example, to develop a viable configuration for our 3725, a task
>made more difficult than it should have been because we got no
>documentation at all except for the online help -- and this over a
>2400 bps (+/-) dialup circuit.
I also used 3725 configurator to validate numbers used in comparing
large configuration implemented using the S/1 SSCP/NCP emulator:
https://www.garlic.com/~lynn/99.html#67 System/1 ?
https://www.garlic.com/~lynn/2001.html#4 Sv: First video terminal?
https://www.garlic.com/~lynn/2001i.html#21 3745 and SNI
https://www.garlic.com/~lynn/2001k.html#21 OT: almost lost LBJ tapes; Dictabelt
https://www.garlic.com/~lynn/2001n.html#9 NCP
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: HONE was .. Hercules and System/390 - do we need it? Newsgroups: bit.listserv.ibm-main,alt.folklore.computers Date: Thu, 11 Jul 2002 15:49:51 GMT"Russell P. Holsclaw" writes:
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: HONE was .. Hercules and System/390 - do we need it? Newsgroups: bit.listserv.ibm-main,alt.folklore.computers Date: Thu, 11 Jul 2002 16:32:27 GMTjcmorris@mitre.org (Joe Morris) writes:
this was when cms\apl was first created (port from phili's apl\360 to
cms environment and making available up to 16mbyte workspaces instead
of just 16k or 32k workspaces). there was an enhanced sense of
security when all the most valuable corporate data was loaded onto the
cambridge system so these guys could run their financial & business
analysis applications. eventually these guys got their own cp/67
systems down and new york. random past ref:
https://www.garlic.com/~lynn/2002h.html#34 Computers in Science Fiction
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: HONE, Aid, misc. Newsgroups: bit.listserv.ibm-main,alt.folklore.computers Date: Thu, 11 Jul 2002 19:37:00 GMTok, didn't found a HONE reference card (yet) ... but digging thru some old stuff did find an Aids Reference card.
also, somebody pointed out that my prior use of Myers Corner as an exmaple was a poor choice ... it was the intersection not a post office.
Note in the attached, consolidation of the (US) regional HONE systems to California didn't occur until 1977. At this time in 1973 there HONE regional centers in Los Angeles, Chicago, Washington DC, and New York.
This is also before Sequoia and the automatic "padded-cell" (aka people logging in found themselves automatically placed in the Sequoia padded-cell (didn't have to "IPL CMS", start APL, etc).
Other stuff, not exhaustive but
VMSHARE Users Guide card (dated January 1980)
... online reference now at
http://vm.marist.edu/~vmshare
sometimes(?) "404" ... but also at wayback machine
http://vm.marist.edu/~vmshare/
REX Reference Summary First Edition (Nov. 1980) - for REX version 2.08 (before product release and name changed to REXX)
Several System/360 Model 67 Reference Data (one of them stamped Edward J. Mosher, aka the "M" in GML, SGML, HTML, XML, etc).
Orange cover The SHARE Songbook
Several copies of the (reprinted) 1931 IBM Songbook
===============================================
(small part of the card transcribed)
IBM Aids Reference Summary, ZZ20-2341-4 Fifth Edition (January 15, 1973) The reference summary supersedes the previous edition and will be updated from time to time. Copies of this publication are distributed to IBM Marketing Representatives and System Engineers. Additional copies are available from the IBM Distribution Center, Mechanicsburg, Pa. Comments about this publication may be sent to the address below. All comments and suggestions become the property of IBM. IBM Aids Usage Guidelines New IBM Aids Configurators available via - APL Library 810 - SECOM TOOLS - PID Design Aids available via - APL Library 820 - SECOM TOOLS - PID - HONE The MINIPERT System in APL Library 835 - MINIPERT User Aids - MINIPERT Processing Programs - MINIPERT Standard Networks Management/Financial Aids available via - APL Library 850 Installation Aids from PID Performance Aids from PID Other SECOM Applications Special Aid - System/7 IBM Aid Publications Instructions for accessing or ordering IBM Aids available via - HONE - SECOM - PID - IBM Distribution Center (Mechanicsburg) IBM Aids Announcement Procedures NOTE: New IBM Aids have been made available since September 1, 1972 are listed on pages 2 and 3.----
Instructions for accessing or ordering IBM Aids Accessing from HONE Systems All IBM Aid APL Libraries are available on your regional HONE system via APL (CMS). Other non-APL IBM Aid Programs implemented on HONE are accessed via CMS. Obtain the phone number of your regional HONE system, your location's ID and current password from your HONE coordinator. On a 2471 terminal proceed as follows: 1. Dial your regional HONE system. 2. Press ATTN, when the keyboard unlocks. HONE will type CP/67 on-line 3. Press ATTN 4. Type LOGIN xxxx (your user ID) HONE will type ENTER PASSWORD: 5. Type: xxx (your password) HONE will type: enter: mannumber, last name, initial, position, purpose, facility 6. Type (the requested information including a position code 0 to 9; purpose code, m; facility code, 5) Note: See HONE log-in procedure card for position code selection HONE will respond with a LOGON message. Your are now under control of CP/67. 7. Type: IPL CMS CMS will respond and you will be under control of CMS. To access an APL IBM Aid 8. Type: APL (Use APL type element) APL (CMS) will respond with the status of your P-disk. You are now under control of APL (CMS) and may load any of the IBM Aid APL workspaces. For example: 9. Type: )LOAD 820 TPNET To access a non-APL IBM Aid Program 8. Type xxxxxx (The CMS name for the program) For example: Type: AIDEX--
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: HONE, , misc. Newsgroups: bit.listserv.ibm-main,alt.folklore.computers Date: Fri, 12 Jul 2002 01:28:37 GMTwell the previous post got subject to all sorts of delays and other things ... apparently because of the four letters that appeared frequently in the post.
i've just about run out of places to look for the HONE reference card.
Did find
a reference card for VS/APL applications that customers could order dated 1979.
a 3270 fullscreen editor user's guide printed 5/18/77 at HONE1 on the backside of greenbar paper. There were a number of 3270 editors developed internally around the company for CMS during the '70s ... this particular one was RED (for raleigh editor).
a printout done at HONE1 on 4/15/77 of the internal network ... also
on the backside of greenbar paper. This is in two parts, 1)
"graphical", little boxes with the node name and lines connecting to
other little boxes and 2)actual node list giving nodid, "index" (in
the graphical ... majority of nodes didn't show in the graphical),
location, (machine) model, type of system, and operator/contact phone
number. Slightly different format to one used later:
https://www.garlic.com/~lynn/99.html#112
The (US) HONE consolidation process had just started at this point and would grow extremely rapidly over the next two years.
There were the DEMO centers in the list ... which had slipped my mind.
In addition to HONE operation for things like configurators and ****,
there were also education center machines and "DEMO" machines in each
of the regions (for use by people in the respective regional and
branch offices). HONE had started trying to shutdown all general use
of CMS and just restrict things to the padded-cell environment. The
"DEMO" machines provided more of a native CMS time-sharing capability
to the people in the branch offices.
DEMO1 Boston
DEMO2 New York
DEMO3 New York
DEMO4 Philadelphia
DEMO5 Washington, DC
DEMO6 Atlanta
DEMO7 Cincinnati
DEMO8 Detroit
DEMO9 Chicago
DEMO10 Minneapolis
DEMO11 St. Louis
DEMO12 Dallas
DEMO13 San Francisco
DEMO14 Los Angeles
and
DEMOPKG Wash DC (g'burg)
John Godwin supported all the DEMO systems from DEMOPKG in g'burg. At
the time of the listing, all of the DEMO machines were 370/145s except
for Boston which was a 370/148. The DEMO machines might be considered
the leading edge of the 4341 "departmental computer" wave ...
https://www.garlic.com/~lynn/2001m.html#15 departmental servers
https://www.garlic.com/~lynn/2002.html#7 The demise of compaq
https://www.garlic.com/~lynn/2002i.html#30 CDC6600 - just how powerful a machine was it?
Somewhat aside, Peterlee (science center) was also on the network list. One of the people at Peterlee had written an email client called VMSG. At about internal development release 0.6, somebody in the PROFS group had co-opted the (limited function) source to use as the core of PROFS implementation. After that, the VMSG source distribution was limited to John, one other person and me.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: HONE, xxx#, misc. Newsgroups: bit.listserv.ibm-main,alt.folklore.computers Date: Fri, 12 Jul 2002 14:27:01 GMTMike Hammock writes:
palo alto science center then did apl\cms and the 145 apl microcode (145 w/apl m'code had apl thruput comparable to 168). The system call violation was removed and replaced with the "shared variable" construct (that was used to implement access to system functions). Since Sequoia was becoming a system unto itself .... Sequoia was getting a lot of performance optimization.
My memory is hazy here, i was at some of the sequoia optimization meetings ... and there were things like adding custom assembler sequences to the APL supervisor specific for enhancing sequoia thruput ... which would have perturbed the ability for using the apl m'code. HONE was running clusters of 168s upgraded to clusters of 168SMP and tweaking wasn't done with thot of 145 apl m'code compatibility (although HONE looked at if there was any way of leveraging farms of 145s for any of their workload).
I'm pretty sure the Sequoia/configurator group stayed in LA when the HONE consolidation took place. In any case there were meetings between the Sequoia group and the guy at PASC that was responsible for 145 apl m'code (he later was also responsible for much of the high performance fortran hx work).
There was a separate significant m'code assist for 138/148 called ECPS
that dropped a lot of the cp kernel (pathlength) into m'code ... but
that would have had little effect on CPU utilization that was nearly
all APL (and a majority of that was the apl Sequoia application). ecps
reference:
https://www.garlic.com/~lynn/94.html#21 ECPS VM microcode aasist
in the above, there were two methods used for identifying kernel hotspots, the kernel call trace and special microcode 145 load that did instruction address sampling. The person that was responsible for the apl m'code also implemented the m'code address sampler.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: HONE was .. Hercules and System/390 - do we need it? Newsgroups: bit.listserv.ibm-main,alt.folklore.computers Date: Fri, 12 Jul 2002 17:35:05 GMTjcmorris@mitre.org (Joe Morris) writes:
old 101, monterey highway ... just north of the bailey T (i.e. bailey
runs west from old 101 crosses santa teresa, past STL lab and up into
the hills to the calero reservoir).
http://claraweb.co.santa-clara.ca.us/parks/prkpages/calero.htm
random refs:
https://www.garlic.com/~lynn/2000b.html#56 South San Jose (was Tysons Corner, Virginia)
https://www.garlic.com/~lynn/2001g.html#34 Did AT&T offer Unix to Digital Equipment in the 70s?
https://www.garlic.com/~lynn/2001g.html#37 Thread drift: Coyote Union (or Coyote Ugly?)
https://www.garlic.com/~lynn/2001i.html#11 YKYGOW...
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: HONE, , misc. Newsgroups: bit.listserv.ibm-main,alt.folklore.computers Date: Fri, 12 Jul 2002 19:04:58 GMTAnne & Lynn Wheeler writes:
Finally after nearly 15 years, some executive in DPD (HONE was part of the sales & marketing division, aka Data Processing Division - DPD) figured it out. The reaction sort of was:
1) he hasn't had management direction to do this
2) HONE doesn't have an MOU (memorandum of understanding) from his management commiting his time for this purpose
3) what happens if he gets hit by a bus
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: "Clean" CISC (was Re: McKinley Cometh...) Newsgroups: comp.arch Date: Sat, 13 Jul 2002 14:25:55 GMT"Stephen Fuld" writes:
associated with activities for the low/mid range 370s also had projects looking at JIT-like activities for 370 code. this was 20+ years ago. I got contacted, in part because I had done a PLI program that analyzed and attempted translation/restructure of 360/370 code nearly 10 years earlier.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: "Clean" CISC (was Re: McKinley Cometh...) Newsgroups: comp.os.vms,comp.arch Date: Sat, 13 Jul 2002 14:48:16 GMT"Stephen Fuld" writes:
tr/translate has a 256-byte table and takes an operand length up to 256
bytes ... it does a byte-by-byte replacement ... taking the byte
from the operand, using that value to index the table and replacing
the operand byte with the byte indexed in the table.
http://publibz.boulder.ibm.com:80/cgi-bin/bookmgr_OS390/BOOKS/DZ9AR004/7.5.96?DT=19970613131822
translate&test has 256-byte table and an operand length up to 256
bytes ... it tkaes an operand byte and indexes the table and stops
if the table entry is non-zero. to search for just a zero has a 256-byte
table that is all zeros except for the first byte.
http://publibz.boulder.ibm.com:80/cgi-bin/bookmgr_OS390/BOOKS/DZ9AR004/7.5.97?DT=19970613131822
neither did copies.
now for newer string instructions
move string
http://publibz.boulder.ibm.com:80/cgi-bin/bookmgr_OS390/BOOKS/DZ9AR004/7.5.60?DT=19970613131822
http://publibz.boulder.ibm.com:80/cgi-bin/bookmgr_OS390/BOOKS/DZ9AR004/A.3.28?SHELF=&DT=19970613131822
search string
http://publibz.boulder.ibm.com:80/cgi-bin/bookmgr_OS390/BOOKS/DZ9AR004/7.5.70?DT=19970613131822
http://publibz.boulder.ibm.com:80/cgi-bin/bookmgr_OS390/BOOKS/DZ9AR004/A.3.35.1?SHELF=&DT=19970613131822
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: "Clean" CISC (was Re: McKinley Cometh...) Newsgroups: comp.arch Date: Sat, 13 Jul 2002 15:03:01 GMTAnne & Lynn Wheeler writes:
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: "Clean" CISC (was Re: McKinley Cometh...) Newsgroups: comp.arch Date: Sat, 13 Jul 2002 15:36:37 GMT"Stephen Fuld" writes:
riscs moved into a market segment that had a large software portable technology base (unix & c) that was working hard on being hardware architecture agnostic.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: "Clean" CISC (was Re: McKinley Cometh...) Newsgroups: comp.os.vms,comp.arch Date: Sat, 13 Jul 2002 16:44:41 GMTJF Mezei writes:
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Unisys A11 worth keeping? Newsgroups: alt.folklore.computers Date: Sun, 14 Jul 2002 23:15:57 GMTCharles Richmond writes:
how 'bout the original GML ... circa 1970?
both got standardized in ISO ... i don't know about the ISO status of many of the others.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Symmetric-Key Credit Card Protocol on Web Site Newsgroups: sci.crypt Date: Mon, 15 Jul 2002 15:59:12 GMTjsavard@ecn.ab.ca () writes:
I also worked on x9.59
https://www.garlic.com/~lynn/subpubkey.html#x959
there were a couple requirements laid down in the x9a10 standards commitee for x9.59 ... 1) was preserve the integrity of the financial infrastructure for all electronic retail payment transactions (agnostic with respect to kind of payment and environment of payment) with only authentication and 2) perform the payment in a single round-trip.
One of the issues for end-to-end authentication is that the
information hiding techniques tending to only be applicable for very
transient periods during transmission while the data continues to
remain vulnerable the rest of the time (lots of stories about fraud as
the result of leakage of merchant transaction log files)
https://www.garlic.com/~lynn/subintegrity.html#fraud
basically x9.59 follows somewhat an existing iso8583 message .... except it adds a digital signature and a couple other fields ... and sends it off. The purchase could be traditional web browsing and sending off a request with an x9.59 payment message. The purchase could also be from a cdrom and sending off a order in a email with a x9.59 payment message attached. The puchase could also be at POS and a x9.59 message signed with a smartcard. There is no requirement for any real-time protocol chatter.
x9.59 defines a business rule that account numbers used in x9.59 authenticated transactions should not be valid in non-authenticated transactions. effectively in the non-authenticated payment transactions, the account number (& other data) exists in a large number of places and any leakage of that information can result in fraudulent transactions .... aka the information needs to be treated as shared-secret ... since just knowing the information can enable fraudulent transactions. Furthermore, any use of encryption for information hiding tends to be while data is in flight ... not typically while at rest (creating a large number of vulnerability opportunities ... both for outside attacks as well as for insiders).
The merchant is also taken out of the loop of having to protect the
consumer's account number and related information
https://www.garlic.com/~lynn/2001h.html#61 Net banking, is it safe???
(or security proportional to risk)
Rather than transient hiding of the vulnerable information while in transit, x9.59 defines end-to-end authenticated transaction where the party (financial institution) responsible for authorizing and executing the transaction .... is also performing the authentication (it also eliminates a lot of widely distributed data as fraud vulnerabilities).
Part of the x9.59 issue was that the current infrastructure using SSL for information hiding while data was in motion on the internet addressed only a small piece of the business vulnerabilities (and fraud opportunities) involved.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Unisys A11 worth keeping? Newsgroups: alt.folklore.computers,comp.sys.unisys Date: Mon, 15 Jul 2002 18:36:12 GMT"Stephen Fuld" writes:
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Ever inflicted revenge on hardware ? Newsgroups: alt.folklore.computers Date: Tue, 16 Jul 2002 13:26:07 GMT"Rupert Pigott" <dark.try-eating-this.b00ng@btinternet.com> writes:
one of the frustrating failure modes was that the end of the last sheet would feed past the paper sense finger ... but not far enuf so that it would completely feed out and you would realize it was out of paper. the only indication was that the it just stopped working. hitting it hard would sometimes joggle the paper enuf that it would slip further and then you would realize that it was out of paper.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: CDC6600 - just how powerful a machine was it? Newsgroups: alt.folklore.computers,comp.sys.cdc Date: Tue, 16 Jul 2002 13:36:12 GMTctill@nc.rr.com (Chuck Till) writes:
the boston programming center was responsible for cps (conversational programming system ... interpreted pl/i ran under os/360 ... and there was special microcode available for 360/50 that made it run faster). Jean Sammet, Nat Rochester, couple others had their offices in the boston programming center (so the vm/370 group sort of absorbed them also). When vm/370 group moved out to sbc bldg. in burlington mall they stayed in 545 tech. sq.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Symmetric-Key Credit Card Protocol on Web Site Newsgroups: sci.crypt Date: Tue, 16 Jul 2002 14:03:59 GMTjsavard@ecn.ab.ca () writes:
as an aside there is already support for mapping multiple different numbers to the same account ... even with multiple different tokens (magstripe or otherwise) ... aka spouse cards, etc. also from electronic perspective ... the typical magstripe carries room for five different account numbers (when you put a debit/atm card in an atm machine ... the selection of which account you want to use can be driven off the account number data on the magstripe).
x9.59 was to enable transition from a shared-secret paradigm to a public key end-to-end authenticated transaction paradigm (possibly deployed first in e-commerce with alternate account number) .... eliminating knowing the account number as a fraud vulnerability (and the necessity for information hiding).
In effect the current payment cards are two different devices ... the physical embossed plastic that can be used in paper transactions and the magnetic stripe for electronic transactions; these two different devices just happened to be carried on the same card. It is possible to package a chip for x9.59 public key operations on the smae or different plastic. If packaged in the same plastic ... you could treat it has three different logical devices (in the same physical housing). There is nothing that would mandate that the chip's account number be the same as the magstripe's account number or the plastic embossed account number. The "correct" account number could then be chosen based on what transaction paradigm is used ... and then apply appropriate risk & fraud rules.
It wouldn't be necessary for somebody to write the alternate account number on the plastic (assuming single physical housing) ... the chip just supplies the correct value (in much the same way the magstripe can supply up to five different account numbers w/o any of them having to be written on the card).
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: ITF on IBM 360 Newsgroups: alt.folklore.computers Date: Wed, 17 Jul 2002 12:37:31 GMTJonathan Griffitts writes:
quicky search engine on cps
https://web.archive.org/web/20021016192931/http://rivendell.uchicago.edu/cps.html
http://gopher.wvnet.edu/EVENTS.HTML
somewhat random ref:
https://www.garlic.com/~lynn/2002j.html#17 CDC6600 - just how powerful a machine was it?
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: MVS on Power (was Re: McKinley Cometh...) Newsgroups: comp.arch Date: Wed, 17 Jul 2002 13:06:10 GMTgah@ugcs.caltech.edu (glen herrmannsfeldt) writes:
Amdahl gave a talk at mit in the early '70s ('72?) about the business plan for clone mainframes .... saying that there were something like $100b worth of assembler software or executables that no longer had source ... that wouldn't get replaced at least before the end of the century (so there would be plenty of market for his mainframes, regardless of what ibm might do). also during the talk there were some very pointed questions about the amount of foreign investment he had taken.
i would expect that the amount/value of such software has grown many times since then ... with possibly only small effect by all the y2k work.
... however this has all been looked at several times before; during FS in general (<25 years ago) ... and during Fort Knox specifically with respect to 801 (20 or so years ago) ... and as already noted ... been accomplished for as/400.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: basic smart card PKI development questions Newsgroups: alt.technology.smartcards Date: Wed, 17 Jul 2002 13:23:12 GMTjohn.veldhuis writes:
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Computer Terminal Design Over the Years Newsgroups: alt.folklore.computers,comp.terminals Date: Thu, 18 Jul 2002 13:35:20 GMTjeffj@panix.com (Jeff Jonas) writes:
2250m1 had its own channel controller directly attached to 360 channel. I got to use one at the university. lincoln labs had done a fortran graphics library for cms that drove the 2250m1. I modified the cms editor to use the lincoln labs 2250 library for a simple full-screen editor (circa late '68).
boeing huntsville had large 360/67 duplex with some number of 2250m1 running version of mvt/r13 (aka running 360/67 in '65 mode). An issue with mvt and single flat, real, linear address space with multiple long running programs was storage fragmentation (i.e. space for single program needed to be contiguous ... a single 2250 program tended to run for long periods of time). they modified mvt/r13 to use the hardware relocation of the 360/67 to address storage fragmentation i.e. no paging or page faults were supported ... but they used the virtual storage mechanism to provide the appearance of contiguous program storage).
About the time BCS (boeing computing services/systems) was formed in late '68/early '69 ... the boeing huntsville machine was shipped to seattle.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Symmetric-Key Credit Card Protocol on Web Site Newsgroups: sci.crypt Date: Thu, 18 Jul 2002 13:50:47 GMTjsavard@ecn.ab.ca () writes:
contains pointer to the ANSI bookstore for getting copy of the x9.59 standard that describes the protocol(?). there is the small issue of standards being copyrighted and rules about ordering them from the standards organization.
it also contains a pointer to a detailed description of mapping x9.59 to iso8583 (8583 is the internal standard for payment network messages).
in effect, x9.59 basically describes a signed payment message. The mapping of x9.59 to iso8583 is from the standpoint of providing end-to-end message integrity and authentication.
a large percentage of other payment messages that have used encryption or other forms of digital signature ... have been implemented with the encryption and digital sigatnures being stripped off at "boundary nodes". this results in very simple violation of basic security principles, no end-to-end security, integrity and/or authentication.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Definition of Non-Repudiation ? Newsgroups: comp.security.misc Date: Thu, 18 Jul 2002 13:58:57 GMTIan Wade writes:
the tendency is towards services that validate a lot of this stuff.
some past discussions (especially ref the last; aadsm11.htm#14):
https://www.garlic.com/~lynn/aadsm11.htm#5 Meaning of Non-repudiation
https://www.garlic.com/~lynn/aadsm11.htm#6 Meaning of Non-repudiation
https://www.garlic.com/~lynn/aadsm11.htm#7 Meaning of Non-repudiation
https://www.garlic.com/~lynn/aadsm11.htm#11 Meaning of Non-repudiation
https://www.garlic.com/~lynn/aadsm11.htm#12 Meaning of Non-repudiation
https://www.garlic.com/~lynn/aadsm11.htm#13 Words, Books, and Key Usage
https://www.garlic.com/~lynn/aadsm11.htm#14 Meaning of Non-repudiation
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: MVS on Power (was Re: McKinley Cometh...) Newsgroups: comp.arch Date: Thu, 18 Jul 2002 16:23:45 GMTJ Ahlstrom writes:
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: LSM, YSE, & EVE Newsgroups: comp.arch Date: Thu, 18 Jul 2002 21:18:01 GMTcecchi@signa.rchland.ibm.com (Del Cecchi) writes:
I'm not sure how many YSE actually got built ... the machine after
the LSM was EVE (endicott verification engine).
https://www.garlic.com/~lynn/2002d.html#3 Chip Emulators - was How does a chip get designed?
https://www.garlic.com/~lynn/2002g.html#55 Multics hardware (was Re: "Soul of a New Machine" Computer?)
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Unisys A11 worth keeping? Newsgroups: alt.folklore.computers Date: Fri, 19 Jul 2002 19:51:02 GMT"Rupert Pigott" <dark.try-eating-this.b00ng@btinternet.com> writes:
i also have done a paged-mapped file system ... allowing the application to give hints ... and then the actual system looked at the hints vis-a-vis real time information and attempted to recouncile the hints with real time information. this is different than a system programmer trying to represent tuning parameters as real time information ... when the system could do real, real time information and tuning.
there are a lot of os/360 apps that did really good job with the asynchronous & direct mapped I/O facilities of maximizing thruput with lots of buffering and overlapped operation. this was a "real storage" and "real i/o" paradigms .... mapping that capability into a virtual memory & page-mapped filesystem offered some interesting challenges.
one of the original tss/360 operations was to try and implement one-level store with no hints .... just map the complete file to virtual memory and fetch a page as the page faults occurred. This is one of the things that gave tss/360 such poor thruput ... the page mapping of both data and executables and then let the pages be fetched synchronously a single (4k) page fault at a time.
At the simplest level ... remapping the os/360 compiler executable overlays into paged mapped ... you could get hints on approx. what all was going to be needed when ... and when it was no longer needed; hints about intelligent throwing away of pages no longer needed was almost as useful as hints about multi-page fetch and/or overlapped fetch hints.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: ibm history note from vmshare Newsgroups: alt.folklore.computers Date: Sat, 20 Jul 2002 15:28:48 GMTwas doing search on vmshare some model numbers and ran across old IBMHIST NOTE from '87 (taken from 85 computerworld article with misc. updates)
http://www.marist.edu/~vmshare/browse.cgi?fn=IBMHIST&ft=NOTE
vmshare currently online at:
http://vm.marist.edu/~vmshare/
in the IBMHIST NOTE file ...
SABRE ... morphed into ACP, TPF, etc ... although AA/AMR still refers to their service as SABRE.
little side-note on the 8100 ... was the uc.5 microprocessor ... same processor used in the 3705 and the service processor for 3081 (among other things). while it includes 8100 ... it doesn't say anything on the s/32, s/34, s/38 (as/400), etc.
308x project was originally referred to as "811" ... for nov. '78
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: mailing list history from vmshare Newsgroups: alt.folklore.computers Date: Sat, 20 Jul 2002 15:54:56 GMTattached from
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Weird... Newsgroups: alt.folklore.computers Date: Sun, 21 Jul 2002 13:47:59 GMTCharles Richmond writes:
the kingston engineering and science center (lots of FPS boxes and
vector pocessing) was I believe predominantly chemistry.
https://www.garlic.com/~lynn/2000c.html#5 TF-1
https://www.garlic.com/~lynn/2000c.html#61 TF-1
https://www.garlic.com/~lynn/2001m.html#25 ESCON Data Transfer Rate
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Unisys A11 worth keeping? Newsgroups: alt.folklore.computers Date: Mon, 22 Jul 2002 00:47:05 GMT"Rupert Pigott" <dark.try-eating-this.b00ng@btinternet.com> writes:
under various kinds of heavy & pathelogical loads ... straight LRU (and straight WSCLOCK) tends to degenerate to FIFO. I did a variation on 2-bit, 2-handed clock that instead of degenerating to FIFO would degenerate to RANDOM (if there otherwise wasn't useful information on which to make a reasonable decision ... making a random ... quick ... choice is better).
random refs:
https://www.garlic.com/~lynn/2000f.html#9 Optimal replacement Algorithm
https://www.garlic.com/~lynn/2000f.html#10 Optimal replacement Algorithm
https://www.garlic.com/~lynn/2000f.html#32 Optimal replacement Algorithm
https://www.garlic.com/~lynn/2000f.html#33 Optimal replacement Algorithm
https://www.garlic.com/~lynn/2000f.html#34 Optimal replacement Algorithm
https://www.garlic.com/~lynn/2000f.html#36 Optimal replacement Algorithm
https://www.garlic.com/~lynn/2001i.html#20 Very CISC Instuctions (Was: why the machine word size ...)
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Latency benchmark (was HP Itanium2 benchmarks) Newsgroups: comp.arch Date: Mon, 22 Jul 2002 14:05:30 GMT"Norbert Juffa" writes:
LRU ... least recently used ... is based on assumption that any data recently used by a program is likely to continue to be used by a program ... and that data that hasn't been used for a while, won't likely to be used for a while. That is just a general assumption. For one thing, LRU degenerates to FIFO under all sorts of situations.
long ago, and far away ... did a psuedo-LRU (variation on wsclock) that under situations where normal LRU degenerated to FIFO ... it would degenerate to RANDOM (and that in detailed simulations, normal psuedo LRU tended to get within 10-20 percent of the performance of true LRU while the random variation tended to beat true LRU by 10 percent).
thread on this yesterday in a.f.c.
https://www.garlic.com/~lynn/2002j.html#31
more general discussion from the past
https://www.garlic.com/~lynn/subtopic.html#wsclock
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: VT50, VT51, VT52, VT55, VT61, VT62 terminals (was Re: Weird...) Newsgroups: alt.folklore.computers Date: Mon, 22 Jul 2002 14:18:07 GMTjmfbahciv writes:
that was just about the same time that some middle management discovered that a number of corporate executives had started using email ... and in a number of cases a whole organization's year's quota for 3270s for engineers and programmers got rerouted to middle management so they could appear to be doing email also ... aka all of a sudden it became a status symbol.
later on, such things became more institutionalized ... aka nearly all the internal PS2m80s going to managers' offices even tho they never used it for anything but 3270 emulation reading email.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: ...killer PC's Newsgroups: bit.listserv.ibm-main,alt.folklore.computers Date: Mon, 22 Jul 2002 17:21:48 GMTibmbama@YAHOO.COM (Howard Rifkind) writes:
introduction of departmental and personal computing allowed some things to migrate off the mainframe ... that were much more of departmental or personal computing type of tasks.
there were problems that some number of enterprise level tasks also migrated to departmental or personal computing platforms ... in some cases putting the enterprise at risk. part of the reason for this migration was the difficulty and frequently long lead time of doing any change/enhancement at the enterprise level ... no matter how trivial.
Another contributing factor was the difficulty of implementing local-domain applications that would access corporate data at the mainframe. there was a legacy problem that initial PC success was greatly facilitated by being able to do 3270 emulation ... but later on when it came time to move on to more sophisticated operations ... there was something of battle with entrenced forces (business units that had significant revenue from 3270 emulation products didn't want to see replaced with peer-to-peer high-speed access products). The resistance to introducing peer-to-peer high-speed access products into the market place contributed significantly to migration of enterprise data off the mainframe.
we got our hand-slapped for coming up with 3-tier architecture ... when the whole SAA client/server effort was trying to significantly reverse trends of applications to the PC (Lotus 123 running on the mainframe?) ... and at the same time limiting things to effectively 3270 emulation products for access by the PC clients to mainframe data (aka single t/r lan was more than "sufficient" for 300-500 PCs).
random refs:
https://www.garlic.com/~lynn/96.html#16 middle layer
https://www.garlic.com/~lynn/96.html#17 middle layer
https://www.garlic.com/~lynn/98.html#50 Edsger Dijkstra: the blackest week of his professional life
https://www.garlic.com/~lynn/99.html#123 Speaking of USB ( was Re: ASR 33 Typing Element)
https://www.garlic.com/~lynn/99.html#124 Speaking of USB ( was Re: ASR 33 Typing Element)
https://www.garlic.com/~lynn/99.html#202 Middleware - where did that come from?
https://www.garlic.com/~lynn/2000e.html#42 IBM's Workplace OS (Was: .. Pink)
https://www.garlic.com/~lynn/2000e.html#45 IBM's Workplace OS (Was: .. Pink)
https://www.garlic.com/~lynn/2000e.html#56 Why not an IBM zSeries workstation?
https://www.garlic.com/~lynn/2001b.html#83 Z/90, S/390, 370/ESA (slightly off topic)
https://www.garlic.com/~lynn/2001d.html#69 Block oriented I/O over IP
https://www.garlic.com/~lynn/2001j.html#20 OT - Internet Explorer V6.0
https://www.garlic.com/~lynn/2001k.html#18 HP-UX will not be ported to Alpha (no surprise)exit
https://www.garlic.com/~lynn/2001k.html#19 HP Compaq merger, here we go again.
https://www.garlic.com/~lynn/2001k.html#46 3270 protocol
https://www.garlic.com/~lynn/2001m.html#15 departmental servers
https://www.garlic.com/~lynn/2001n.html#23 Alpha vs. Itanic: facts vs. FUD
https://www.garlic.com/~lynn/2001n.html#34 Hercules etc. IBM not just missing a great opportunity...
https://www.garlic.com/~lynn/2001n.html#55 9-track tapes (by the armful)
https://www.garlic.com/~lynn/2002.html#2 The demise of compaq
https://www.garlic.com/~lynn/2002.html#7 The demise of compaq
https://www.garlic.com/~lynn/2002.html#11 The demise of compaq
https://www.garlic.com/~lynn/2002b.html#4 Microcode? (& index searching)
https://www.garlic.com/~lynn/2002b.html#37 Poor Man's clustering idea
https://www.garlic.com/~lynn/2002d.html#4 IBM Mainframe at home
https://www.garlic.com/~lynn/2002d.html#14 Mainframers: Take back the light (spotlight, that is)
https://www.garlic.com/~lynn/2002e.html#2 IBM's "old" boss speaks (was "new")
https://www.garlic.com/~lynn/2002h.html#52 Bettman Archive in Trouble
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Latency benchmark (was HP Itanium2 benchmarks) Newsgroups: comp.arch Date: Mon, 22 Jul 2002 17:31:37 GMT... i used to have something posted to the effect (re LRU degenerating to FIFO) that when you can't make a good decision ... make a RANDOM one.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Difference between Unix and Linux? Newsgroups: alt.folklore.computers Date: Thu, 25 Jul 2002 22:04:18 GMT"Alan T. Bowler" writes:
they were supported in half-duplex mode by the (ibm) 2702 terminal controller which recognized certain line-end characters and generated interrupt to the processor when those characters were encountered.
at the university, we ran into some issues with the 2702 terminal
controller and a couple of us started a project where we built a
terminal controller starting with interdata/3 and reverse engineering
the ibm channel interface and building our own board to interface to
the ibm mainframe channel ... supposedly credited with originated the
ibm pcm controller business:
https://www.garlic.com/~lynn/submain.html#360pcm
the interdata/3 supported the tty terminals in full duplex and then played some games mapping that to half-duplex for the 2702 controller emulation. later, it was enhanced to be a combination of interdata/4 with interdata/3 dedicated to line-scanner function.
I believe the use of the interdata as termianl controller was then expanded to other mainframes (not just ibm). Also, perkin/elmer eventually bought it up ... and they were sold under the perkin/elmer brand. I ran into one 5-6 years ago in major transaction processing datacenter still handling heavy traffic load.
there was the "yale iup" for the series/1 in the '80s which also provided full-duplex ascii support for tty terminals to aix/370 (aka the port of ucla locus to 370 and ps/2 and released as ibm product).
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: HONE was .. Hercules and System/390 - do we need it? Newsgroups: bit.listserv.ibm-main,alt.folklore.computers Date: Thu, 25 Jul 2002 23:12:06 GMTAnne & Lynn Wheeler writes:
about every two years some executive in the HONE chain of command or somewhere else in DPD would make some statement about HONE being hosted on MVS platform. Possibly 20-30 percent of the HONE staff would be sent off to port HONE to MVS platform. After 4-6 months it was be deemed an utter and total failure ... and the porting effort would quietly fade away. The problem being that it wasn't politically correct to point out that it was a utter and total failure to try and get something working on MVS. Since it wasn't politically correct to document it ... the whole issue would crop up in another 18 months or so and the exercise would get repeated.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: MITM solved by AES/CFB - am I missing something?! Newsgroups: sci.crypt Date: Fri, 26 Jul 2002 13:03:08 GMTSam Simpson writes:
If the situation assumes that keys have been securely exchanged ... and that given a secure, encrypted channel using AES CFB ... then can a MITM modify data in the transmission that goes undetected?
In a public key exchange ,,, can a MITM substitute their own public key undetected?
In the case of a public key exchange with certificates ... can a MITM create a situation where a valid certificate is substituted aka there has been lots of discussion regarding how a MITM would go about getting a valid, acceptable certificate ... say a SSL domain name server certificate.
one of the most recent has been in crypto mailing list regarding buying a root key that is currently acceptable to a majority of browsers, try search engine on: SSL Certificate "Monopoly" Bears Financial Fruit.
part of the issue is that while you might use certificates to a current real time public key exchange ... there is some kind of chain of trust going back to some procedure where you have accepted one or more "root key" by some method ... and all subsequent trust decisions you make involving certificates involve both the method by which you accepted that "root key" ... and all subsequent operations that the owner(s) of that root key might have been involved in ... as well as the method you use to protect and secure your list(s) of acceptable root keys.
things like PGP just eliminate the chain of trust ... they maintain a (secure) list of trusted keys and they use some out of band process for introducing keys into that list of trusted keys.
certificate infrastructures, in effect operate the same way .... but you might not even be aware of what your list of trusted keys are and/or what processes that were used to establish them and/or maintain them. These trusted keys then are used by entities that you may have no idea about to generate certificates (as opposed to directly signing pieces of email) ... which you then accept on complete faith. part of this is a possible myopic focus on the bit-stream that composes a particular public key certificate ... ignoring the whole rest of the business processes involved in creating the infrastructure for the operation of public key certificates ... certificates don't actually eliminate any of the MITM attacks on public key exchange ... they are just moved around ... at the same time adding a whole bunch of new attacks.
random refs:
https://www.garlic.com/~lynn/subpubkey.html#sslcerts
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Beginner question on Security Newsgroups: sci.crypt Date: Fri, 26 Jul 2002 13:13:51 GMTjonath-k writes:
encryption nominally isn't a business process .... it is a technology, that might be used to address things like integrity and privacy ... aka encryption can be used to keep information private ... encryption can also be used to recognize whether data has been modified in transit (aka integrity).
misc ref:
https://www.garlic.com/~lynn/secure.htm
from above
security
(1) The combination of confidentiality, integrity, and
availability. (2) The quality or state of being protected from
uncontrolled losses or effects. Note: Absolute security may in
practice be impossible to reach; thus the security 'quality' could be
relative. Within state models of security systems, security is a
specific 'state' that is to be preserved under various
operations. [AJP] (I) (1.) Measures taken to protect a system. (2.)
The condition of system that results from the establishment and
maintenance of measures to protect the system. (3.) The condition of
system resources being free from unauthorized access and from
unauthorized or accidental change, destruction, or loss. [RFC2828] A
condition that results from the establishment and maintenance of
protective measures that ensure a state of inviolability from hostile
acts or influences. [NSAINT] All aspects related to defining,
achieving, and maintaining confidentiality, integrity, availability,
accountability, authenticity, and reliability. NOTE - A product,
system, or service is considered to be secure to the extent that its
users can rely that it functions (or will function) in the intended
way. This is usually considered in the context of an assessment of
actual or perceived threats. [ISO/IEC WD 15443-1 (11/2001)] [SC27] The
combination of confidentiality, integrity, and availability. [FCv1]
The quality or state being protected from uncontrolled losses or
effects. Note: Absolute security may in practice be impossible to
reach; thus the security 'quality' could be relative. Within
state-models of security systems, security is a specific 'state', that
is to be preserved under various operations. [JTC1/SC27/N734]
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Beginner question on Security Newsgroups: sci.crypt Date: Fri, 26 Jul 2002 17:48:58 GMTAnders Thulin writes:
the previously references security glossary at
https://www.garlic.com/~lynn/secure.htm
is a merge of glossaries from:
Terms merged from: AFSEC, AJP, CC1, CC2, FCv1, FIPS140, IATF V3,
IEEE610, ITSEC, Intel, JTC1/SC27/N734, KeyAll, MSC, NCSC/TG004, NIAP,
NSA Intrustion, RFC1983, RFC2504, RFC2828, TCSEC, TDI, TNI, and
misc. Updated 20020505 with NSA Intrusion glossary. Updated 20020511
with latest ISO SC27 definitions.
(including both common criteria "1" and "2" ... aka CC1, CC2)
repeat of the definion
security
(1) The combination of confidentiality, integrity, and
availability. (2) The quality or state of being protected from
uncontrolled losses or effects. Note: Absolute security may in
practice be impossible to reach; thus the security 'quality' could be
relative. Within state models of security systems, security is a
specific 'state' that is to be preserved under various
operations. [AJP] (I) (1.) Measures taken to protect a system. (2.)
The condition of system that results from the establishment and
maintenance of measures to protect the system. (3.) The condition of
system resources being free from unauthorized access and from
unauthorized or accidental change, destruction, or loss. [RFC2828] A
condition that results from the establishment and maintenance of
protective measures that ensure a state of inviolability from hostile
acts or influences. [NSAINT] All aspects related to defining,
achieving, and maintaining confidentiality, integrity, availability,
accountability, authenticity, and reliability. NOTE - A product,
system, or service is considered to be secure to the extent that its
users can rely that it functions (or will function) in the intended
way. This is usually considered in the context of an assessment of
actual or perceived threats. [ISO/IEC WD 15443-1 (11/2001)] [SC27] The
combination of confidentiality, integrity, and availability. [FCv1]
The quality or state being protected from uncontrolled losses or
effects. Note: Absolute security may in practice be impossible to
reach; thus the security 'quality' could be relative. Within
state-models of security systems, security is a specific 'state', that
is to be preserved under various operations. [JTC1/SC27/N734]
but also including related terms (these terms are hypertect linked at
the above glossary)
(see also BLACK, Generic Security Services API, IT security policy, IT
security product, Kerberos, National Computer Security Center,
National Computer Security Center glossary, National Security Decision
Directive 145, RED, benign environment, classification level,
clearance level, computer security technical vulnerability reporting
program, concealment system, information flow control, lock-and-key
protection system, multi-level secure, national computer security
assessment program, need-to-know, network reference monitor, no-lone
zone, overwrite procedure, permissions, personal security environment,
print suppression, privacy, privileged process, restricted area,
sanitize, secure configuration management, secure envelope, secure
hash algorithm, secure hyper text transfer protocol, secure single
sign-on, secure sockets layer, secure subsystem, security authority,
security certificate, security element, security information object,
security information object class, security policy information file,
signed applet, system integrity, systems security steering group,
trusted computer system, accreditation)
(includes Advanced Mobile Phone Service, Asynchronous Transfer Mode,
Authentication Header, Automated Information System security,
Automated Security Incident Measurement, CONcept of Operations, Common
Criteria, Common IP Security Option, Computer Security Objects
Register, Cryptographic Application Program Interface, Data Encryption
Standard, DoD Information Technology Security Certification and
Accreditation Process, Generic Upper Layer Security, Internet Protocol
security, National Information Assurance partnership, PKIX private
extension, SOCKS, Simple Distributed Security Infrastructure, Simple
Public Key Infrastructure/Simple Distributed Security Infrastructure,
Standard Security Label, TEMPEST, TOE security functions, TOE security
policy, Target of Evaluation, access control, access control list,
accountability, add-on security, administrative security, adversary,
anonymity, anti-jam, application program interface, application-level
firewall, assurance, asymmetric cryptographic algorithm, attack,
audit, authentication, authorization, automated data processing
security, automated information system, automated security monitoring,
availability, baseline, binding of security functionality, biometrics,
call back, call back security, certificate, certificate revocation
list, certification and accreditation, certification authority,
challenge/response, checksum, closed security environment, code
division multiple access, common data security, common data security
architecture, common security, common security services manager,
communication and data security architecture, communications security,
compartmented security mode, compromise, compromised key list,
computer emergency response team, computer intrusion, computer
operations, audit, and security technology, computer security,
computer security incident response team, computer security object,
computer security subsystem, confidentiality, configuration
management, contingency plan, control zone, controlled security mode,
corporate security policy, correctness proof, countermeasures, covert
channel, credential, crypto-ignition key, crypto-security,
cryptographic functions, data security, dedicated security mode,
defense in depth, defense-wide information assurance program, denial
of service, designated approving authority, developer security,
digital certificate, digital signature, discretionary access control,
downgrade, dual control, eavesdropping, economy of mechanism,
effective key length, electronic key management system, email security
software, emanations security, emission security, encapsulating
security payload, evaluation assurance level, external security
controls, file security, formal security policy model, frequency
division multiple access, front-end security filter, future narrow
band digital terminal, global command and control system, global
information grid, global network information environment, guard,
hacker, hash, host-based security, identification, identification and
authentication, information assurance, information security,
information system security officer, information systems security,
information systems security engineering, information technology,
insider attack, integrity, internal security controls, internet
control message protocol, intrusion detection, intrusion detection
system, key, key management, key management infrastructure, layered
solution, local area network, mandatory access control, mission needs
statement, motivation, multi-level security, multi- level security
mode, multipurpose internet mail extensions, mutual suspicion,
mutually suspicious, national telecommunications and Information
Systems Security advisery memoranda/instructions, national
telecommunications and information system security directives, network
security, network security architecture, network security officer,
non-discretionary security, non-technical countermeasure, open
security, open security environment, open system interconnection
model, open systems security, operational data security, operational
integrity, operations security, organisational security policy,
parity, partitioned security mode, password, perimeter-based security,
personnel security, physical security, pretty good privacy, privacy,
authentication, identification, integrity, non-repudiation, privacy,
authentication, identification, non-repudiation, procedural security,
protection needs elicitation, protection profile, proxy, public-key
infrastructure, residual risk, risk, risk management, risk plane,
robustness, rule-based security policy, sanitization, secret key,
secure multipurpose internet mail extensions, secure network server,
secure profile inspector, secure state, security architecture,
security class, security clearance, security compromise, security
environment, security event, security features, security filter,
security flaw, security flow analysis, security function, security
gateway, security incident, security intrusion, security level,
security management infrastructure, security mechanism, security
model, security objective, security officer, security parameters
index, security perimeter, security policy, security protocol,
security safeguards, security service, security situation, security
software, security specifications, security target, security testing,
separation of duties, session key, signature [digital, electronic],
simple security property, social engineering, software security,
strength of mechanisms, subject security level, symmetric algorithm,
system integrity service, system security authorization agreement,
system security officer, system security policy, system-high security
mode, tamper, technical countermeasure, technical security policy,
technology gap, term rule-based security policy, threat, time division
multiple access, token, top-level security objectives, transmission
security, trojan horse, trusted computing base, trusted operating
system, tunneling router, usage security policy, user, virtual network
perimeter, virtual private network, virus, vulnerability, wide area
network, worm)
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Transportation Newsgroups: alt.folklore.computers Date: Fri, 26 Jul 2002 19:56:35 GMT"Rupert Pigott" <dark.try-eating-this.b00ng@btinternet.com> writes:
As a starting assumption that nearly all the road infrastructure costs (original build, ongoing maint., etc) are almost totally heavy trucking related ... then it would be logical(?) to start with all fuel taxes supporting road systems be only applicable to heavy trucks ... in effect all the current fuel tax income currently spread across the whole driving population but recovered solely from heavy trucking activity).
I have no idea what the current percentage of total fuel consumption is by heavy trucking ... just for argument sake lets assume three percent. With fuel tax running around 40 cents (federal + state), then if this was to be totally recovered by heavy trucking fuel consumption ... it would need to be raised by a factor of thirty to around twelve dollars per gallon.
misc ref on fuel tax:
http://www.taxadmin.org/fta/rate/motor_fl.html
misc road construction ref:
https://web.archive.org/web/20010803072011/http://www.dot.ca.gov/hq/oppd/hdm/chapters/t603.htm
603.1 Introduction
The primary goal of the design of the pavement structural section is
to provide a structurally stable and durable pavement and base system
which, with a minimum of maintenance, will carry the projected traffic
loading for the designated design period. This topic discusses the
factors to be considered and procedures to be followed in developing a
projection of truck traffic for design of the "pavement structure" or
the structural section for specific projects.
Pavement structural sections are designed to carry the projected truck
traffic considering the expanded truck traffic volume, mix, and the
axle loads converted to 80 kN equivalent single axle loads (ESAL's)
expected to occur during the design period. The effects on pavement
life of passenger cars, pickups, and two-axle trucks are considered to
be negligible.
Traffic information that is required for structural section design
includes axle loads, axle configurations, and number of
applications. The results of the AASHO Road Test (performed in the
early 1960's in Illinois) have shown that the damaging effect of the
passage of an axle load can be represented by a number of 80 kN
ESAL's. For example, one application of a 53 kN single axle load was
found to cause damage equal to an application of approximately 0.23 of
an 80 kN single axle load, and four applications of a 53 kN single
axle were found to cause the same damage (or reduction in
serviceability) as one application of an 80 kN single axle.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Transportation Newsgroups: alt.folklore.computers Date: Fri, 26 Jul 2002 20:30:47 GMTAnne & Lynn Wheeler writes:
the new/current web page for the caltrans highway design manual
http://www.dot.ca.gov/hq/oppd/hdm/hdmtoc.htm
and it does point at a (large, 750kbyte) pdf file that is online.
http://www.dot.ca.gov/hq/oppd/hdm/pdf/chp0600.pdf
a little picking around and found html file online
https://web.archive.org/web/20020619144341/http://www.dot.ca.gov/hq/oppd/hdm/c600.htm
but missing a lot of drawings found in the pdf version.
note the above also has section (606) that covers some of the issues of things like frost heaves.
old roads postings:
https://www.garlic.com/~lynn/99.html#21 Roads as Runways Was: Re: BA Solves Y2K (Was: Re: Chinese Solve Y2K)
https://www.garlic.com/~lynn/99.html#22 Roads as Runways Was: Re: BA Solves Y2K (Was: Re: Chinese Solve Y2K)
https://www.garlic.com/~lynn/99.html#23 Roads as Runways Was: Re: BA Solves Y2K (Was: Re: Chinese Solve Y2K)
https://www.garlic.com/~lynn/99.html#27 Roads as Runways Was: Re: BA Solves Y2K (Was: Re: Chinese
https://www.garlic.com/~lynn/99.html#32 Roads as Runways Was: Re: BA Solve
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Killer Hard Drives - Shrapnel? Newsgroups: alt.folklore.computers Date: Sat, 27 Jul 2002 15:37:02 GMTab528@FreeNet.Carleton.CA (Heinz W. Wiggeshoff) writes:
when i did stint at boeing for the BCS (boeing computing system/services) startup (was one of the first couple dozen employees) ... renton had a really large datacenter ... joke about there constantly being 2-3 360/65s boxed in the hallways waiting staging for installation on the machine room floor.
for disaster recovery purposes, all of renton data center was later duplicated in everett (one of the scenarios is mud-slide down the nearby mountain; which they take seriously ... some of the small towns nearer the mountain have sirens and drills).
one story they told is that the day after the 360 announcement ... boeing walked into their local salesman and placed an initial order for something like twenty 360/65s (actually would have been 360/60s on announcement day). his commission exceeded the top executive salary that year ... and as a result the next year corporate hdqtrs created the quota plan (rather than straight commission). That year, his commission also exceeded the top xecutive salary ... and they up'ed his quota again. He then left and formed his own computer consulting and services company (which much later got bought by GM, and then he formed a new computer consulting and services company and also ran for president).
random refs:
https://www.garlic.com/~lynn/99.html#32 Roads as Runways Was: Re: BA Solve
https://www.garlic.com/~lynn/99.html#130 early hardware
https://www.garlic.com/~lynn/2000f.html#66 360 Architecture, Multics, ... was (Re: X86 ultimate CISC? No.)
https://www.garlic.com/~lynn/2001b.html#8 "HAL's Legacy and the Vision of 2001: A Space Odyssey"
https://www.garlic.com/~lynn/2001b.html#9 "HAL's Legacy and the Vision of 2001: A Space Odyssey"
https://www.garlic.com/~lynn/2001b.html#23 Linux IA-64 interrupts [was Re: Itanium benchmarks ...]
https://www.garlic.com/~lynn/2001g.html#56 YKYBHTLW....
https://www.garlic.com/~lynn/2001m.html#55 TSS/360
https://www.garlic.com/~lynn/2002f.html#30 Computers in Science Fiction
https://www.garlic.com/~lynn/2002j.html#22 Computer Terminal Design Over the Years
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Funeral for a friend - Infiniband Newsgroups: comp.arch Date: Sat, 27 Jul 2002 15:45:26 GMTrpw3@rigden.engr.sgi.com (Rob Warnock) writes:
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: M$ SMP and old time IBM's LCMP Newsgroups: bit.listserv.ibm-main,alt.folklore.computers Date: Mon, 29 Jul 2002 14:29:36 GMTjfregus@ix.netcom.com (John F. Regus) writes:
at about the same time, HONE was centralizing and creating what I
believe was the largest single system complex in the world
... clusters of SMP.
https://www.garlic.com/~lynn/subtopic.html#hone
later we did an internal high-speed backbone and did some NSFNET
related work ... as well as HA/CMP and involved in both FCS and SCI
standards.
https://www.garlic.com/~lynn/95.html#13 SSA
https://www.garlic.com/~lynn/subtopic.html#hacmp
part of the reason was we were looking for scalable support and none of the rios chips had support for consistent shared memory ... and the power/pc with shared memory support was still years away (at the time we started on High Availability Cluster Multi-Processing in the late '80s).
and then after both taking an early out in '92 ... spent some time talking to sequent, convex, and tandem. both sequent and tandem claimed to have done significant (shared-memory) parallization work on the NT kernel in the early to mid 90s.
sequent had a snoopy bus with intel processors that went to 32-way ... but I believe those configurations were primarily supported by dynix (sequent's unix) ... i believe the NT work was primarily on 4-way to 8-way processor shared memory configurations.
side note ... if anybody remembers the netscape downloads of the mid-90s ... they had multiple large servers netscape1, netscape2, netscape3, ... and it was suggested that people sort of randomly try different nodes looking for lightest loaded. they eventually installed a large sequent configuration as netscape20 ... and the problem sort of just evaporated (as did most of the multiple servers). at the time, sequent dynix had possibly the best scaling tcp/ip support around (at least in terms of supporting large number of concurrent sessions, they were also one of the first to have scalable solution to the dnagling finwait opportunity; at the time there were some situations where processors were spending >90percent of the cpu running the dangling finwait list).
sequent and data general both did 256-way intel using SCI ... basically 4-way intel quad-board sharing local cache and 64-port SCI configuration implementing 256-way global shared memory (sequent took relatively standard intel 4-way SMP quad-boards and did the work to make it work with 64-port SCI).
note that there are both lcmp clusters and shared-nothing clusters. lcmp clusters typically have shared-access to disk (while not having shared-memory). shared-nothing clusters (like wolfpack) rely on network message passing ... to implement things like replicated data.
press release from 10/12/95 (remember AT&T was also NCR)
Companies Voice Support for Microsoft Clustering Strategy
AT&T Global Information Solutions welcomes the opportunity to
participate in providing customers with an industry standard for
clustering technology. AT&T has years of experience in delivering
clustering and fault-resilient technology with AT&T(R)
LifeKeeper. Through our collaboration with Microsoft, we plan to
protect and enhance our customers' investment in Windows NT Server
solutions from AT&T, and to continue to deliver superior
high-availability solutions that drive and utilize future
industry-standard clustering technology for Windows NT Server.'
extract from 8/96
http://www.winntmag.com/issues/Aug96/wolfpack.htm
What Is Wolfpack?
Several leading NT Server systems vendors, including Compaq, Digital
Equipment, HP, NCR, and Tandem, have been independently working on
clustering solutions for a few years. These vendors agreed to pool their
expertise with Microsoft in an initiative to produce a cross-vendor standard
for NT Server clusters. This group wanted to give NT Server customers the
greater choice and flexibility they wanted. So in October 1995, Microsoft
announced its intent to develop strategic partnerships to fashion a new
clustering standard with the code name Wolfpack.
This name and many of its technology goals derive from Pfister's book. In
Chapter 4, Pfister describes a cluster as a "pack of dogs." While searching
for a code name for the API, Microsoft came across this book and decided to
describe clusters with the name Wolfpack, which sounds a lot cooler than
Dogpack.
Wolfpack is an alias for clusters, and the six core vendors in Microsoft's
clustering project consider themselves members of the Wolfpack. These
members are Digital, Compaq, Tandem, Intel, HP, and NCR. Each partner
contributes key components of its existing technology. Other vendors,
including Amdahl, IBM, Octopus, Vinca, Marathon, Stratus, and Cheyenne, have
agreed to support the Wolfpack API. These vendors are part of Microsoft's
Open Process, which includes about 60 vendors and customers who are part of
design previews during various stages of Wolfpack development.
Wolfpack describes a set of cluster-aware APIs, NT cluster support, and a
clustering solution (which means a vendor can claim to be Wolfpack compliant
while competing with the Wolfpack solution on a different level--so if a
vendor claims to support Wolfpack, you need to ask how). Here's a detailed
explanation of each Wolfpack component.
<snip>
misc m'soft refs:
http://www.microsoft.com/WINDOWS2000/hpc/dsmperpec.asp
http://www.microsoft.com/technet/treeview/default.asp?url=/TechNet/prodtechnol/windows2000serv/reskit/serverop/part2/sopch10.asp
random sci refs:
https://www.garlic.com/~lynn/96.html#8 Why Do Mainframes Exist ???
https://www.garlic.com/~lynn/96.html#25 SGI O2 and Origin system announcements
https://www.garlic.com/~lynn/98.html#40 Comparison Cluster vs SMP?
https://www.garlic.com/~lynn/2001b.html#39 John Mashey's greatest hits
https://www.garlic.com/~lynn/2001b.html#85 what makes a cpu fast
https://www.garlic.com/~lynn/2001f.html#11 Climate, US, Japan & supers query
https://www.garlic.com/~lynn/2001j.html#12 OT - Internet Explorer V6.0
https://www.garlic.com/~lynn/2001j.html#17 I hate Compaq
https://www.garlic.com/~lynn/2001l.html#16 Disappointed
https://www.garlic.com/~lynn/2002g.html#10 "Soul of a New Machine" Computer?
https://www.garlic.com/~lynn/2002h.html#78 Q: Is there any interest for vintage Byte Magazines from 1983
https://www.garlic.com/~lynn/2002i.html#83 HONE
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: M$ SMP and old time IBM's LCMP Newsgroups: bit.listserv.ibm-main,alt.folklore.computers Date: Mon, 29 Jul 2002 14:49:01 GMTAnne & Lynn Wheeler writes:
also from
http://www.winntmag.com/issues/Aug96/wolfpack.htm
Wolfpack: The Solution
Microsoft will deliver Wolfpack, the solution, in two phases.
Phase 1 is two-node availability and scaling clusters (a new version of SQL
Server will let you work on the same database from two servers at once).
Phase 2 will allow more than two nodes in a cluster.
Reread the first paragraph in this article. That scenario describes a June
1996 demonstration of a Wolfpack availability cluster solution at PC Expo in
New York City. This two-node failover capability is the basis for Phase 1 of
Wolfpack (early 1997 is the estimate for delivery). The price for Wolfpack's
Phase 1 release is not set, but one rumor is that NT Server will include
Wolfpack at no additional cost. As I write this article, Compaq, Digital,
HP, NCR, Amdahl, Stratus, and Tandem have all announced plans to OEM the
Wolfpack-based cluster solution.
The next step in Phase 1 (set for the second quarter of 1997) will be an
open certification program with the goal of expanding the market for
two-node cluster solutions and giving NT Server customers a greater
selection to choose from. Microsoft is also committed to making Wolfpack
available on Intel, Alpha, PowerPC, and MIPS chips.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: M$ SMP and old time IBM's LCMP Newsgroups: bit.listserv.ibm-main,alt.folklore.computers Date: Mon, 29 Jul 2002 20:14:34 GMT"Rupert Pigott" <dark.try-eating-this.b00ng@btinternet.com> writes:
the big new thing in clustering seems to be the grid stuff that the high-energy physics guys seemed to have started ... it was all over supercomputer 2002 in denver at the start of the year ... and now "grid" seems to be the new, in term.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: SHARE Planning Newsgroups: bit.listserv.ibm-main,alt.folklore.computers Date: Mon, 29 Jul 2002 22:03:53 GMTjmaynard@CONMICRO.CX (Jay Maynard) writes:
i had been part of announcement at spring '68 share meeting in houston ... but that 30th year has come and gone (will be 35 years next spring).
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Funeral for a friend - Infiniband Newsgroups: comp.arch Date: Tue, 30 Jul 2002 14:08:49 GMT"Tarjei T. Jensen" writes:
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: SHARE Planning Newsgroups: bit.listserv.ibm-main,alt.folklore.computers Date: Tue, 30 Jul 2002 14:37:08 GMTAnne & Lynn Wheeler writes:
the spring '68 announcement that was held at houston share was for cp/67 ... the precursor to vm/370.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Next step in elimination of 3270's? Newsgroups: bit.listserv.ibm-main,alt.folklore.computers Date: Tue, 30 Jul 2002 17:44:28 GMTedgould@AMERITECH.NET (Edward Gould) writes:
random ref in killer PC thread
https://www.garlic.com/~lynn/2002j.html#34 ...killer PC's
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: "Slower is more secure" Newsgroups: sci.crypt Date: Wed, 31 Jul 2002 14:30:38 GMTMok-Kong Shen <mok-kong.shen@t-online.de> writes:
at least corporate espionage was issue in the US ... and both corporate and gov. espionage was issue outside the US. I seem to remember something in the news from the period about gov. agents in some european country going thru hotel rooms as part of industrial espionage efforts.
evem prior to the "road warrior" issue .... all of the telco lines for internal corporate network required link encryptors (for some period, the claim was that half of all link encryptors in the world were installed on the internal network, that claim may have been qualified with "non-gov" ... i don't remember) .. . I remember this causing some issues with gov/PPTs in europe ... especially lines that crossed country borders.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: SHARE Planning Newsgroups: bit.listserv.ibm-main,alt.folklore.computers Date: Wed, 31 Jul 2002 14:57:18 GMTAnne & Lynn Wheeler writes:
also in the above ref regarding origin of 360 pcm controller business
https://www.garlic.com/~lynn/submain.html#360pcm
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: MIT says I don't live in the USA Newsgroups: sci.crypt Date: Wed, 31 Jul 2002 15:38:34 GMTMickey writes:
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: AADS, ECDSA, and even some TCPA Newsgroups: sci.crypt Date: Thu, 01 Aug 2002 19:05:45 GMTAfter spending several years on the AADS chip strawman
I also gave a talk on it at the Intel Developer's Forum last year, including a claim that pretty much as it currently existed, it could do all the things that were requirement for trusted computing module. A copy of this presentation is also at the above URL (slides on assurance).
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Server and Mainframes Newsgroups: bit.listserv.ibm-main Date: Fri, 02 Aug 2002 14:51:24 GMTmsimpson@UKY.EDU (Matt Simpson) writes:
specifically within the ibm customer world ... it was associated with the ibm 360, 370, etc lineage of computers and along the way became somewhat synonymous with their applications and capabilities.
with hardware technology advances, it became possible to build single frame processors that would run the "mainframe" operating systems and the associated applications.
also over the years, with various minicomputer and microcomputer evoluation acquired applications that had lots of the attributes that had previously only been seen in the "mainframe" dataprocessing world.
slightly related to the multiple frame issue ... start of 360 pcm
controller business:
https://www.garlic.com/~lynn/submain.html#360pcm
and slightly related to the ras dataprocessing attribute:
https://www.garlic.com/~lynn/subtopic.html#disk
in any case something that may have originally started out as highlighting the distinction between the "large" multiple box dataprocessing and the single box minicomputers ... has become quite ambiquous ... loosing a lot of its original specific meaning ... and along the way acquiring a lot of additional connotations.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Server and Mainframes Newsgroups: bit.listserv.ibm-main Date: Fri, 02 Aug 2002 19:08:00 GMT"Howard Brazee" writes:
more than just the straight rack-mount ... starting with 4u and wanting to be a lot thinner.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: SSL integrity guarantees in abscense of client certificates Newsgroups: sci.crypt Date: Fri, 02 Aug 2002 19:27:12 GMT"Ben Mord" writes:
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: SSL integrity guarantees in abscense of client certificates Newsgroups: sci.crypt Date: Fri, 02 Aug 2002 19:35:53 GMTpornin@nerim.net (Thomas Pornin) writes:
as mentioned in some mailing lists there is starting to be concerns about browser tables of trusted public keys (i.e. the list of public keys for certification authorities that may sign acceptable server certificates).
there is also the issue that when processing a domain name certificate application ... the certification authority must rely on the authoritative agency responsible for the information being certified. In the case of domain name certificates, the authoritative agency is the domain name infrastrucure ... the very same domain name infrastructure who's integrity questions give rise to needing ssl server domain name certificates in the first place.
Now there are some integrity enhancements ... in part proposed by the certification authorities to improve the integrity of the domain name infrastructure ... so that the certification authorities can trust the certification of the domain name request that they perform with the domain name infrastructure.
A possible obvious catch-22 is that if the domain name infrastructure intregrity is improved for use by the certification authorities ... it may be of sufficient integrity for everybody's use and ssl domain name certificates would no longer be necessary.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: How to map a user account to a digital cert? Newsgroups: alt.technology.smartcards Date: Fri, 02 Aug 2002 19:51:25 GMTjohn.veldhuis writes:
pkinit draft specifies that a message is digital signed (in the case of a hardware token, the hardware token "signs" the message). the message is designed to prevent replay, sniffing, or skimming attacks.
any hardware token that just transmits a fixed value ... even if it is a cert ... is subject to replay/sniffing vulnerabilities (aka somebody evesdrops on any fixed transmitted value ... and then is able to reproduce it is capable of defeating the system). This is the same as the replay/sniffing vulnerabilities on passwords ... once you find out the value .... you can operate fraudulently.
unfortunately that are some number of hardware tokens that actually do just transmit a fixed value for authentication .... putting them down close to the password paradigm from an integrity standpoint (subject to sniffing/skimming vulnerability and subsequent fraudulent replays).
kerberos is internet standard
nndex to internet rfc standards can be found at
https://www.garlic.com/~lynn/rfcietff.htm
to find kerberso specific RFCs ... select term (term->RFC#) at the above web page and scroll down to "kerberos" ... aka
kerberos
see also authentication , security
3244 3129 2942 2712 2623 1964 1510 1411
selecting on the specific RFCs will bring up the summary in the lower frame. Selecting on the txt field in the summary will retrieve the actual rfc.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: SSL integrity guarantees in abscense of client certificates Newsgroups: sci.crypt Date: Fri, 02 Aug 2002 22:22:57 GMTEdward Elliott writes:
now it turns out that the existing domain name infrastructure implementations have provide a generic facility for real-time distribution of information, aka all information associated with a domain name can be distributed ... not just the ip-address.
a significant reduction in the ssl handshaking chatter would go away if in the same response the ip-address was returned to the client by the domain name infrastructure if the public key (if available) was piggy backed on the same response ... as part of the standard domain name infrastructure support.
all the certificate stuff disappears ... all of the browser trusted key repository disappears ... all the certificate related SSL handshaking chatter disappears ... poof ... you have both a trusted ip-address and a trusted public key in a single operation.
refs:
https://www.garlic.com/~lynn/subpubkey.html#sslcerts
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Server and Mainframes Newsgroups: bit.listserv.ibm-main Date: Sat, 03 Aug 2002 03:39:54 GMTcfmtech@istar.ca (Clark F. Morris, Jr.) writes:
random refs:
https://www.garlic.com/~lynn/2000f.html#69 TSS ancient history, was X86 ultimate CISC? designs)
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'
https://www.garlic.com/~lynn/2001k.html#9 HP-UX will not be ported to Alpha (no surprise)exit
https://www.garlic.com/~lynn/2001k.html#10 HP-UX will not be ported to Alpha (no surprise)exit
https://www.garlic.com/~lynn/2001k.html#11 HP-UX will not be ported to Alpha (no surprise)exit
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: SSL integrity guarantees in abscense of client certificates Newsgroups: sci.crypt Date: Sat, 03 Aug 2002 14:29:37 GMTEdward Elliott writes:
the world bank report mentioned in the attached may be of some interest
https://www.garlic.com/~lynn/aadsm12.htm#12 TOC for world bank e-security paper
general related threads:
https://www.garlic.com/~lynn/subintegrity.html#fraud
https://www.garlic.com/~lynn/subintegrity.html#assurance
part of the issue is that the account number essentially is itself
authentication information and therefor must be treated as a
shared-secret. the financial standards x9a10 working group was
given the requirement to preserve the integrity of the financial
infrastructure for all electronic retail payments (not just debit,
or credit, or atm, or just internet or point-of-sale, etc ... but
ALL):
https://www.garlic.com/~lynn/x959.html#x959
misc. security proportional to risk related threads:
https://www.garlic.com/~lynn/aadsm6.htm#websecure merchant web server security
https://www.garlic.com/~lynn/aadsm6.htm#terror4 [FYI] Did Encryption Empower These Terrorists?
https://www.garlic.com/~lynn/aadsm6.htm#pcards The end of P-Cards?
https://www.garlic.com/~lynn/aadsm6.htm#pcards3 The end of P-Cards? (addenda)
https://www.garlic.com/~lynn/aadsm7.htm#rubberhose Rubber hose attack
https://www.garlic.com/~lynn/aepay7.htm#netbank2 net banking, is it safe?? ... security proportional to risk
https://www.garlic.com/~lynn/aepay7.htm#netsecure some recent threads on netbanking & e-commerce security
https://www.garlic.com/~lynn/aepay7.htm#3dsecure2 3D Secure Vulnerabilities? Photo ID's and Payment Infrastructure
https://www.garlic.com/~lynn/aadsm8.htm#rhose17 [Fwd: Re: when a fraud is a sale, Re: Rubber hose attack]
https://www.garlic.com/~lynn/aepay7.htm#3dsecure3 financial payment standards ... finger slip
https://www.garlic.com/~lynn/aadsm10.htm#cfppki13 CFP: PKI research workshop
https://www.garlic.com/~lynn/aadsm10.htm#tamper Limitations of limitations on RE/tampering (was: Re: biometrics)
https://www.garlic.com/~lynn/aepay10.htm#20 Security Proportional to Risk (was: IBM Mainframe at home)
https://www.garlic.com/~lynn/aadsm11.htm#45 Web site exposes credit card fraud
https://www.garlic.com/~lynn/2001h.html#61 Net banking, is it safe???
https://www.garlic.com/~lynn/2001h.html#67 Would this type of credit card help online shopper to feel more secure?
https://www.garlic.com/~lynn/2001i.html#53 Credit Card # encryption
https://www.garlic.com/~lynn/2001i.html#57 E-commerce security????
https://www.garlic.com/~lynn/2001j.html#2 E-commerce security????
https://www.garlic.com/~lynn/2001j.html#44 Does "Strong Security" Mean Anything?
https://www.garlic.com/~lynn/2001k.html#55 I-net banking security
https://www.garlic.com/~lynn/2001l.html#2 Why is UNIX semi-immune to viral infection?
https://www.garlic.com/~lynn/2002d.html#8 Security Proportional to Risk (was: IBM Mainframe at home)
https://www.garlic.com/~lynn/2002d.html#9 Security Proportional to Risk (was: IBM Mainframe at home)
https://www.garlic.com/~lynn/2002d.html#11 Security Proportional to Risk (was: IBM Mainframe at home)
https://www.garlic.com/~lynn/2002d.html#16 Mainframers: Take back the light (spotlight, that is)
https://www.garlic.com/~lynn/2002d.html#24 Security Proportional to Risk (was: IBM Mainframe at home)
https://www.garlic.com/~lynn/2002d.html#25 Security Proportional to Risk (was: IBM Mainframe at home)
https://www.garlic.com/~lynn/2002d.html#28 Security Proportional to Risk (was: IBM Mainframe at home)
https://www.garlic.com/~lynn/2002e.html#5 What goes into a 3090?
https://www.garlic.com/~lynn/2002e.html#18 Opinion on smartcard security requested
https://www.garlic.com/~lynn/2002e.html#36 Crypting with Fingerprints ?
https://www.garlic.com/~lynn/2002e.html#37 Would the value of knowledge and information be transferred or shared accurately across the different culture??????
https://www.garlic.com/~lynn/2002f.html#10 Least folklorish period in computing (was Re: IBM Mainframe at home)
https://www.garlic.com/~lynn/2002f.html#23 Computers in Science Fiction
https://www.garlic.com/~lynn/2002f.html#28 Security Issues of using Internet Banking
https://www.garlic.com/~lynn/2002f.html#35 Security and e-commerce
https://www.garlic.com/~lynn/2002h.html#6 Biometric authentication for intranet websites?
https://www.garlic.com/~lynn/2002h.html#41 Biometric authentication for intranet websites?
https://www.garlic.com/~lynn/2002i.html#72 A Lesson In Security
https://www.garlic.com/~lynn/2002j.html#14 Symmetric-Key Credit Card Protocol on Web Site
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: vm marketing (cross post) Newsgroups: bit.listserv.ibm-main,alt.folklore.computers Date: Sat, 03 Aug 2002 15:25:21 GMTdoes anybody remember the cern cms/tso bake-off report distributed at share (circa 1974) and that internally copies of the report was stamped"confidential, restricted" (aka available on a need to know basis only).
at various points it was thot that share did more vm marketing than possibly any "marketing" organization ... (aka customer vm uptake at times seemed to be in despite of the marketing organization).
in any case, if it hadn't been for share ... you might not have seen the evolution of gml/sgml to html/xml/etc at cern.
the other interesting side-light was that for an extended period of
time, the whole world-wide marketing organization .... operated on
HONE ... which were all VM/CMS (initially starting out on CP/67)
... and the US HONE installation was for a long time the largest
single system data processing complex in the world.
random refs:
https://www.garlic.com/~lynn/subtopic.html#hone
starting with the 370 115/125 a marketing rep couldn't even order a machine w/o using HONE.
and eventually the whole corporation "ran" on the internal network .... which was from just about the start until possibly sometime circa 1985, larger than the whole arpanet/internet ... and was predominately VM.
One of the issues in the internal network .... was by the time mvs platform got jes support ... the size of the internal network was larger than the jes node table .... and the various increases in the jes node table size always trailed the number of nodes in the internal network. The NJE driver had a habit of throwing away network traffic that wasn't in the local table ... that eliminated the possibility of any JES node of ever acting as an intermediate store&forward node on the internal network. As a result any JES nodes were simply restricted to boundary nodes on the internal network.
The other problem was that JES made the mistake with NJE of effectively confusing network issues and jes operation; as a result incompatible releases of JES could result in bringing down the MVS system (i.e. a new release of JES with slight modification to NJE header ... could precipitate mvs sysem crashes if transmitting to earlier release JES-based systems).
The vm network support ... divorced the transport interface from the operation of the network ... and essentially from the beginning had effectively "gateway" capability at each node. A VM node might have its native drivers (which also had more efficient & higher thruput than NJE drivers) and possibly one or more NJE drivers.
Frequently a VM node acting as a store&forward node in the internal network with some number of JES boundary nodes .... would have NJE header "cleaner code" incorporated into each of its NJE drivers. The NJE header cleaner code would be specific to the release level of JES that the driver code was talking to. The point of the NJE header cleaner code would to be normalize NJE header information that might have originated from a JES system at a different release or version level and keep the local MVS system from crashing.
VM network code was possibly the original implementation that cleanly separated & layered driver, network, transport, and application issues.
One of the case histories was where a JES/MVS boundary node in San Jose was crashing MVS systems in Hursley i.e. the San Jose system had upgraded its JES2 system which was generated slightly different NJE header information ... and the VM NJE header cleaner code in Hursley wasn't handling the new variation and letting a glitch get thru. To a lot of people .... it wasn't viewed as a severe deficiency in MVS, JES, & NJE .... it was a VM "bug" because VM wasn't keeping the MVS system from crashing.
in any case, one of the reasons that the internet finally started to grow faster than the internal network in the '80s was the big internet switch-over in 1/1/83 to a protocol that actually had the IP-layer as well as "gateway" (aka ... prior to the 1/1/83 the arpanet/internet didn't have internet prototol support).
not only did cp/40, cp/67, and vm/370 come out of the cambridge science center ... but also things like gml and the internal network.
slightly related discussions of arpanet/internet with some internal network:
https://www.garlic.com/~lynn/internet.htm
some specific thread regarding internal network size
https://www.garlic.com/~lynn/99.html#112 OS/360 names and error codes (was: Humorous and/or Interesting Opcodes)
https://www.garlic.com/~lynn/2000d.html#63 Is Al Gore The Father of the Internet?
https://www.garlic.com/~lynn/2000e.html#13 internet preceeds Gore in office.
https://www.garlic.com/~lynn/2000e.html#14 internet preceeds Gore in office.
https://www.garlic.com/~lynn/2000e.html#30 Is Tim Berners-Lee the inventor of the web?
https://www.garlic.com/~lynn/2001c.html#4 what makes a cpu fast
https://www.garlic.com/~lynn/2001h.html#19 checking some myths.
https://www.garlic.com/~lynn/2001h.html#21 checking some myths.
https://www.garlic.com/~lynn/2001j.html#50 Title Inflation
https://www.garlic.com/~lynn/2001n.html#12 Author seeks help - net in 1981
misc. csc (& 545 tech sq) threads
https://www.garlic.com/~lynn/subtopic.html#545tech
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Total Computing Power Newsgroups: alt.folklore.computers Date: Sat, 03 Aug 2002 15:34:35 GMT"Russ Holsclaw" writes:
there was a bank that had thousands of 3270s at hundreds of branches with 9600baud multi-drop line (aka multiple 3270s shared the same 9600 line) to each branch). they upgraded to distributed computing model with something like T1 line to each branch and things slowed down. The issue was that the 9600baud lines was only shipping the screens to the 3270s ... while the distributed computing model was trying to continuely ship large amounts of the data to the local branches where the data then would be munged on before displaying on the screen.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: vm marketing (cross post) Newsgroups: bit.listserv.ibm-main,alt.folklore.computers Date: Sat, 03 Aug 2002 15:55:36 GMTwith respect to drop-off in the growth rate of the internal network .... see the departmental computing threads.
basically late '70s and early '80s saw an explosive growth in mainframe (and other machines) used in departmental computing environments. in the mid-80s that market place started to migrate to high-end PCs and various workstations. The internet treated those boxes as network nodes while the internal network supported then with terminal emulation ... not as true network nodes (there may have been a large number of such machines with internal network connectivity ... but they didn't show up as network nodes ... while they did on the internet).
misc. departmental computing/server threads:
https://www.garlic.com/~lynn/2001m.html#15 departmental servers
https://www.garlic.com/~lynn/2001m.html#43 FA: Early IBM Software and Reference Manuals
https://www.garlic.com/~lynn/2001m.html#44 Call for folklore - was Re: So it's cyclical.
https://www.garlic.com/~lynn/2001m.html#56 Contiguous file system
https://www.garlic.com/~lynn/2001n.html#15 Replace SNA communication to host with something else
https://www.garlic.com/~lynn/2001n.html#23 Alpha vs. Itanic: facts vs. FUD
https://www.garlic.com/~lynn/2001n.html#34 Hercules etc. IBM not just missing a great opportunity...
https://www.garlic.com/~lynn/2001n.html#39 195 was: Computer Typesetting Was: Movies with source code
https://www.garlic.com/~lynn/2002.html#2 The demise of compaq
https://www.garlic.com/~lynn/2002.html#7 The demise of compaq
https://www.garlic.com/~lynn/2002b.html#0 Microcode?
https://www.garlic.com/~lynn/2002b.html#4 Microcode? (& index searching)
https://www.garlic.com/~lynn/2002b.html#37 Poor Man's clustering idea
https://www.garlic.com/~lynn/2002b.html#44 PDP-10 Archive migration plan
https://www.garlic.com/~lynn/2002c.html#0 Did Intel Bite Off More Than It Can Chew?
https://www.garlic.com/~lynn/2002d.html#4 IBM Mainframe at home
https://www.garlic.com/~lynn/2002d.html#7 IBM Mainframe at home
https://www.garlic.com/~lynn/2002d.html#14 Mainframers: Take back the light (spotlight, that is)
https://www.garlic.com/~lynn/2002e.html#2 IBM's "old" boss speaks (was "new")
https://www.garlic.com/~lynn/2002e.html#47 Multics_Security
https://www.garlic.com/~lynn/2002e.html#61 Computers in Science Fiction
https://www.garlic.com/~lynn/2002e.html#74 Computers in Science Fiction
https://www.garlic.com/~lynn/2002e.html#75 Computers in Science Fiction
https://www.garlic.com/~lynn/2002f.html#7 Blade architectures
https://www.garlic.com/~lynn/2002f.html#60 Mainframes and "mini-computers"
https://www.garlic.com/~lynn/2002g.html#19 Why did OSI fail compared with TCP-IP?
https://www.garlic.com/~lynn/2002h.html#52 Bettman Archive in Trouble
https://www.garlic.com/~lynn/2002i.html#30 CDC6600 - just how powerful a machine was it?
https://www.garlic.com/~lynn/2002i.html#57 CDC6600 - just how powerful a machine was it?
https://www.garlic.com/~lynn/2002j.html#4 HONE, , misc
https://www.garlic.com/~lynn/2002j.html#7 HONE, , misc
https://www.garlic.com/~lynn/2002j.html#34 ...killer PC's
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Total Computing Power Newsgroups: alt.folklore.computers Date: Sat, 03 Aug 2002 20:35:58 GMTcbh@ieya.co.REMOVE_THIS.uk (Chris Hedley) writes:
I got to write the HYPERchannel support for hyperchannel A51x boxes and the channel driver for the local A22x channel attach box.
Bascially the A51x box emulated an IBM local channel and connected channel attached controllers. The A22x attached directly to IBM channel. Between the A22x box and the A51x boxes were HYPERCHnanel network that included a T1 segment.
This providing what appeared to be local, channel connected 3270 response at the remote site for the IMS group .... and had a side-effect that the thruput of the IBM mainframes went up. The side-effect was that the A22x channel box had much more efficient channel handshaking than the 3274 controllers ... which met that overall local/real channel busy went down for the same amount of 3270 activity.
I also did the rfc1044 tcp/ip support for the standard mainframe product ... using the A22x channel interface. I was able to test this at cray research using a 4341-clone operating a full chnanel speed talking to a cray machine using very modest amount of the 4341 processor. The base tcp/ip product with the standard channel interface would come close to saturating a 3090 processor getting 44kbyte (440kbit) per second.
random ref:
https://www.garlic.com/~lynn/subnetwork.html#hsdt
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Killer Hard Drives - Shrapnel? Newsgroups: alt.folklore.computers Date: Sun, 04 Aug 2002 01:29:31 GMThawk@slytherin.ds.psu.edu (Dr. Richard E. Hawkins) writes:
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Killer Hard Drives - Shrapnel? Newsgroups: alt.folklore.computers Date: Sun, 04 Aug 2002 14:24:22 GMTCharles Richmond writes:
quicky use of search engine
why does hawaii have interstate highways?
http://geography.miningco.com/library/faq/blqzhawaiiinterstates.htm
misc. other
http://geography.about.com/library/weekly/aa052499.htm
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: hone acronym (cross post) Newsgroups: bit.listserv.ibm-main,alt.folklore.computers Date: Sun, 04 Aug 2002 15:43:40 GMTone of the early HONE uses was for testing/demoing 370 software. HONE started out with 360/67s and CP/67 "H". People could do this from 2741 in the branch office w/o even needing to travel to the nearest datacenter and getting dedicated 3rd shift machine time (this possibly somewhat prompted the Hands-On Network Environment acronym).
CSC had CP "L", CP "H", and CP "I". The "L" system was standard CP/67 kernel with lots of internal modifications that hadn't shipped in the product. "H" had modifications to the kernel to provide (selectable) both 360 virtual machines and 370 virtual machines (aka instructions were simulated as per the 370 architecture not the 360 architecture ... as well as the new 370 instructions that didn't exist in 360). "H" had both 370 non-relocate mode as well as 370 "virtual memory" mode. "I" kernel had modifications that would run on the 370 virtual memory architecture rather than the 360/67 virtual memory architecture. The original purpose of the "H"/"I" project was to develop test environment for new 370. Copies of the "I" kernel were regularly running 12 months before the first 370 engineering machine with virtual memory was available. In fact, when the first 370 virtual memory engineering machine was ready to test (this was a machine that booted by throwing a knife switch), the "I" kernel was used.
After "basic" 370 had been announced ... but before machines were generally available; one of the early HONE applications was to allow field people to test software against the "new" architecture ("virtual memory" 370 mode was crippled because it hadn't been announced yet). Later when 370 "virtual memory" was announced (and machines weren't yet available), people in the field had the ability to boot operating system kernels and test software (note that "H" & "I" kernels were also being used extensively inside IBM for development and test).
There was also a CP/67-SJ kernel ... this was the CP/67 "I" kernel with changes done by the San Jose engineers to support block multiplexor channel, IDALs, 3330 disk drives, and 2305 fixed-head disks (i.e. after real 370s with virtual memory hardware became available internally with 3330s and 2305s and long before vm/370 was available).
Slightly different folklore was that the original development SVS ... was a MVT kernel modified to support virtual memory including a well-hacked copy of CP/67's "CCWTRANS" (the cp/67 module that handled virtual to real CCW translation and page fixing) .... starting out testing on 360/67 virtual memory architecture ... and then modified to test in CP/67-H 370 virtual machine.
related refs:
https://www.garlic.com/~lynn/2000b.html#61 VM (not VMS or Virtual Machine, the IBM sort)
https://www.garlic.com/~lynn/2000c.html#34 What level of computer is needed for a computer to Love?
https://www.garlic.com/~lynn/2000d.html#65 "all-out" vs less aggressive designs (was: Re: 36 to 32 bit transition)
https://www.garlic.com/~lynn/2000e.html#37 FW: NEW IBM MAINFRAMES / OS / ETC.(HOT OFF THE PRESS)
https://www.garlic.com/~lynn/2001b.html#18 Linux IA-64 interrupts [was Re: Itanium benchmarks ...]
https://www.garlic.com/~lynn/2001k.html#29 HP Compaq merger, here we go again.
https://www.garlic.com/~lynn/2002c.html#39 VAX, M68K complex instructions (was Re: Did Intel Bite Off More Than It Can Chew?)
https://www.garlic.com/~lynn/2002h.html#50 crossreferenced program code listings
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: history of CMS Newsgroups: alt.folklore.computers Date: Sun, 04 Aug 2002 16:52:17 GMTthread drift from
one of the things I was doing was walking the fab. line .... i don't envy the people that have to work all day in those bunny suits.
the chip has about the same memory as 360/30 but is much faster ... although there isn't as many i/o devices attached ... but it does fit in one of those little plastic cards you may have in your wallet.
the project started about five years ago ... see chip strawman at:
https://www.garlic.com/~lynn/x959.html#aads
misc. other
https://www.garlic.com/~lynn/2002j.html#55 AADS, ECDSA, and even some TCPA
https://www.garlic.com/~lynn/aepay10.htm#40 AADS Chip Strawman & aSuretee
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: help: Thinking with Meat Newsgroups: rec.arts.sf.science,comp.ai.philosophy,rec.arts.sf.written,alt.folklore.computers Date: Mon, 05 Aug 2002 13:25:14 GMTJ. Clarke writes:
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: How to map a user account to a digital cert? Newsgroups: alt.technology.smartcards Date: Mon, 05 Aug 2002 13:52:27 GMTjohn.veldhuis writes:
and do search on ecdsa
that does digital signing using fips186-2 ecdsa
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Itanium2 power limited? Newsgroups: comp.arch Date: Mon, 05 Aug 2002 15:40:18 GMTnmm1@cus.cam.ac.uk (Nick Maclaren) writes:
3272(controller)/3277(terminal) with some local hardware hacks made it almost livable (at least local channel attached). later 3274 controller that moved much of the hardware out of the terminal (shared hardware in the controller) ... aggravated various user interface issues and negated the ability to do hardware hacks in the terminal (also any networked controller versions were a real pain).
One of the worst 3270 issues was the traditional mainframe half-duplex i/o model. if you happened to be doing a keystroke at the same time there was a screen write ... the keyboard locked and you had to stop and hit the reset key. a simple hardware hack on the 3277 eliminated that particular bit of nastiness. form-filling was a significantly more half-duplex paradigm .... better matching the mainframe i/o model.
when the IMS group were moved out of STL to remote building .... they looked remote/network 327x controllers and somewhat blanched when they saw comparison to what they had been used to with local channel attach. they eventually went with HYPERchannel as a "channel extender" over T1 link with local 327x controllers at the remote location.
later PCs with 3277 terminal emulation for local connect allowed the hardware hacks to be done in softare instead.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
Date: Tue, 06 Aug 2002 08:04:26 -0500 Newsgroups: bit.listserv.vmesa-l From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: 30th b'dayRSCS started out as cpremote at csc. the later evolved it into networking protocol. the first production networking connection of note was between cambridge and endicott working on the CP/67 "H" & "I" systems (aka the modifications to support 370 virtual machines with virtual addressing on real 360/67). The "I" system had been running a year under an "H" systtem on real 360/67 (or in some cases under an "H" system under a "L" system on real 360/67 ... because of security concerns at cambridge with the number of MIT, BU, etc students with access to the system).
internallly it was called VNET for many years before the joint RSCS &
JES2/NJE product was announced for customers.
https://www.garlic.com/~lynn/2002j.html#64 vm marketing (cross post)
perkin-elmer was sort of interesting to be because they had bought
interdata and were marketing a pcm terminal controller. as an
undergraduate i had worked on a project that created the first pcm
terminal controller using an interdata/3 (later enhanced to
interdata/4 with interdata/3s dedicated as linescanners). we get
blamed for originating the 360 PCM controller market
https://www.garlic.com/~lynn/submain.html#360pcm
Simpson also did something called RASP at ibm ... which never became a
product ... but bore some similarity to GNOSIS/KEYKOS.
https://www.garlic.com/~lynn/2000f.html#69 TSS ancient history, was X86 ultimate CISC? designs)
https://www.garlic.com/~lynn/2000g.html#22 No more innovation? Get serious
https://www.garlic.com/~lynn/2001b.html#73 7090 vs. 7094 etc.
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/2001n.html#10 TSS/360
https://www.garlic.com/~lynn/2002f.html#59 Blade architectures
https://www.garlic.com/~lynn/2002g.html#0 Blade architectures
https://www.garlic.com/~lynn/2002g.html#4 markup vs wysiwyg (was: Re: learning how to use a computer)
https://www.garlic.com/~lynn/2002h.html#43 IBM doing anything for 50th Anniv?
https://www.garlic.com/~lynn/2002i.html#63 Hercules and System/390 - do we need it?
Simpson worked on similar project after he went to Amdahl .... which
also never made it to product .... although a lot of the people got
absorbed by gold/uts
https://www.garlic.com/~lynn/2000f.html#68 TSS ancient history, was X86 ultimate CISC? designs)
https://www.garlic.com/~lynn/2000f.html#69 TSS ancient history, was X86 ultimate CISC? designs)
https://www.garlic.com/~lynn/2000f.html#70 TSS ancient history, was X86 ultimate CISC? designs)
https://www.garlic.com/~lynn/2001g.html#35 Did AT&T offer Unix to Digital Equipment in the 70s?
https://www.garlic.com/~lynn/2001l.html#18 mainframe question
https://www.garlic.com/~lynn/2002g.html#0 Blade architectures
https://www.garlic.com/~lynn/2002i.html#63 Hercules and System/390 - do we need it?
the internal (vnet) network was larger than arpanet/internet until
about '85 .... random refs:
https://www.garlic.com/~lynn/2000f.html#60 360 Architecture, Multics, ... was (Re: X86 ultimate CISC? No.)
https://www.garlic.com/~lynn/2001h.html#19 checking some myths.
https://www.garlic.com/~lynn/2001j.html#28 Title Inflation
https://www.garlic.com/~lynn/2001j.html#29 Title Inflation
https://www.garlic.com/~lynn/2002b.html#53 Computer Naming Conventions
https://www.garlic.com/~lynn/2002b.html#54 Computer Naming Conventions
https://www.garlic.com/~lynn/2002b.html#56 Computer Naming Conventions
https://www.garlic.com/~lynn/2002c.html#39 VAX, M68K complex instructions (was Re: Did Intel Bite Off More Than It Can Chew?)
https://www.garlic.com/~lynn/2002e.html#47 Multics_Security
https://www.garlic.com/~lynn/2002g.html#48 Why did OSI fail compared with TCP-IP?
https://www.garlic.com/~lynn/2002g.html#71 Coulda, Woulda, Shoudda moments?
https://www.garlic.com/~lynn/2002h.html#48 Why did OSI fail compared with TCP-IP?
along with bitnet was earn ... random refs:
https://www.garlic.com/~lynn/94.html#22 CP spooling & programming technology
https://www.garlic.com/~lynn/99.html#38c Internet and/or ARPANET?
https://www.garlic.com/~lynn/99.html#39 Internet and/or ARPANET?
https://www.garlic.com/~lynn/99.html#126 Dispute about Internet's origins
https://www.garlic.com/~lynn/2000b.html#67 oddly portable machines
https://www.garlic.com/~lynn/2000d.html#56 Is Al Gore The Father of the Internet?
https://www.garlic.com/~lynn/2000d.html#63 Is Al Gore The Father of the Internet?
https://www.garlic.com/~lynn/2000d.html#72 When the Internet went private
https://www.garlic.com/~lynn/2000d.html#77 Is Al Gore The Father of the Internet?^
https://www.garlic.com/~lynn/2000e.html#15 internet preceeds Gore in office.
https://www.garlic.com/~lynn/2000f.html#22 Why trust root CAs ?
https://www.garlic.com/~lynn/2000f.html#51 Al Gore and the Internet (Part 2 of 2)
https://www.garlic.com/~lynn/2000g.html#24 A question for you old guys -- IBM 1130 information
https://www.garlic.com/~lynn/2000g.html#39 Could CDR-coding be on the way back?
https://www.garlic.com/~lynn/2001b.html#71 Z/90, S/390, 370/ESA (slightly off topic)
https://www.garlic.com/~lynn/2001c.html#19 What is "IBM-MAIN"
https://www.garlic.com/~lynn/2001e.html#12 Blame it all on Microsoft
https://www.garlic.com/~lynn/2001e.html#25 Pre ARPAnet email?
https://www.garlic.com/~lynn/2001h.html#65 UUCP email
https://www.garlic.com/~lynn/2002d.html#33 LISTSERV(r) on mainframes
https://www.garlic.com/~lynn/2002e.html#6 LISTSERV(r) on mainframes
https://www.garlic.com/~lynn/2002h.html#11 Why did OSI fail compared with TCP-IP?
https://www.garlic.com/~lynn/2002i.html#44 Unisys A11 worth keeping?
https://www.garlic.com/~lynn/2002j.html#29 mailing list history from vmshare
At 12:09 AM 8/6/2002 -0500, Automatic digest processor wrote:
During those many years, we've enjoyed SHAREing. I'll mention one
partnership, as an example of many. During the early seventies, U
Maine (Orono, ME), the Perkin-Elmer Corp. (Danbury, CT), and Amoco
Research (Tulsa OK) joined forces. We all saw the value and
opportunities of VM and realized that it needed some tweaking and
development that IBM may not be willing to perform. So for the
benefit of each organization, we were connected via a file-transfer
ancestor of RSCS (a derivative of RASP, if I recall correctly). For
several years we collaborated closely, jointly maintaining VM and
developing many hundreds of "mods". Some of these were made available
to the VM community via SHARE, and many or most were either later
incorporated into the product or influenced VM Developers.We did e-
mail before the folks of CUNY talked us into sharing via BITNET.
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Difference between Unix and Linux? Newsgroups: alt.folklore.computers,comp.os.linux.advocacy,gnu.misc.discuss Date: Wed, 07 Aug 2002 01:47:56 GMTPete Fenelon writes:
random refs:
https://www.garlic.com/~lynn/2000e.html#42 IBM's Workplace OS (Was: .. Pink)
https://www.garlic.com/~lynn/2000e.html#45 IBM's Workplace OS (Was: .. Pink)
https://www.garlic.com/~lynn/2000e.html#46 Where are they now : Taligent and Pink
https://www.garlic.com/~lynn/2000e.html#48 Where are they now : Taligent and Pink
https://www.garlic.com/~lynn/2001j.html#32 Whom Do Programmers Admire Now???
https://www.garlic.com/~lynn/2002i.html#60 Unisys A11 worth keeping?
https://www.garlic.com/~lynn/2002j.html#34 ...killer PC's
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: IBM 327x terminals and controllers (was Re: Itanium2 power limited?) Newsgroups: comp.arch Date: Wed, 07 Aug 2002 02:26:01 GMTEric Smith <eric-no-spam-for-me@brouhaha.com> writes:
... random refs:
https://www.garlic.com/~lynn/2001k.html#30 3270 protocol
https://www.garlic.com/~lynn/2001k.html#33 3270 protocol
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Future interconnects Newsgroups: comp.arch Date: Wed, 07 Aug 2002 02:39:04 GMTGreg Pfister writes:
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Q: Trust in an X.509 certificate Newsgroups: sci.crypt Date: Wed, 07 Aug 2002 17:20:35 GMTgrk@usa.net (G. Ralph Kuntz, MD) writes:
a primary purpose of ssl xyz.com domain name certificates .... is because of trust issues with the domain name infrastructure. the problem is that to certify some information ... a certification authority (CA) has to validate the validating of the information being certified. Typically a CA is not the authoritative agency for the information certified .... so the CA has to check with the appropriate authoritative agency. the authoritative agency for domain names (that CAs have to check with) is the domain name infrastructure ... the very thing that there are questions about originally giving rise to ssl domain name certificates.
now there are CA oriented proposals for improving the integrity of the domain name infrastructure .... allowing CAs to better trust the information they are certifying. However these methods also go a long way to improving the overall integrity of the domain name infrastructure .... and minimizing the need/requirement for ssl domain name certificates.
aka .... you are missing in the above picture .... the authoritative agency that a CA-server has to check with as to the validity of the information being certified (i.e. it can either be a dasteredly-dan-CA-server or a dasteredly-dan-information-source).
ref:
https://www.garlic.com/~lynn/subpubkey.html#sslcerts
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Difference between Unix and Linux? Newsgroups: alt.folklore.computers,comp.os.linux.advocacy,gnu.misc.discuss Date: Wed, 07 Aug 2002 22:50:35 GMTThe Ghost In The Machine writes:
random sgml/gml refs:
https://www.garlic.com/~lynn/98.html#21 Reviving the OS/360 thread (Questions about OS/360)
https://www.garlic.com/~lynn/99.html#197 Computing As She Really Is. Was: Re: Life-Advancing Work of Timothy Berners-Lee
https://www.garlic.com/~lynn/2000.html#8 Computer of the century
https://www.garlic.com/~lynn/2000e.html#0 What good and old text formatter are there ?
https://www.garlic.com/~lynn/2000e.html#1 What good and old text formatter are there ?
https://www.garlic.com/~lynn/2001i.html#1 History of Microsoft Word (and wordprocessing in general)
https://www.garlic.com/~lynn/2001i.html#39 IBM OS Timeline?
https://www.garlic.com/~lynn/2001m.html#43 FA: Early IBM Software and Reference Manuals
https://www.garlic.com/~lynn/2002.html#53 School Help
https://www.garlic.com/~lynn/2002b.html#46 ... the need for a Museum of Computer Software
https://www.garlic.com/~lynn/2002j.html#64 vm marketing (cross post)
https://www.garlic.com/~lynn/94.html#43 Bloat, elegance, simplicity and other irrelevant concepts
https://www.garlic.com/~lynn/94.html#55 How Do the Old Mainframes Compare to Today's Micros?
https://www.garlic.com/~lynn/96.html#24 old manuals
https://www.garlic.com/~lynn/97.html#9 HELP! Chronology of word-processing
misc. 545 tech sq
https://www.garlic.com/~lynn/subtopic.html#545tech
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Q: Trust in an X.509 certificate Newsgroups: sci.crypt Date: Thu, 08 Aug 2002 11:13:00 GMT"lyal collins" writes:
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: formal fips186-2/x9.62 definition for eal 5/6 evaluation Newsgroups: sci.crypt Date: Thu, 08 Aug 2002 11:28:48 GMTanybody seen a formal definition for fips186-2/x9.62/ecdsa for eal 5/6 evaluation?
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Summary: Robots of Doom. Newsgroups: rec.arts.sf.science,comp.ai.philosophy,rec.arts.sf.written,alt.folklore.computers Date: Thu, 08 Aug 2002 12:37:45 GMTJim Balter writes:
in the later two cases (actually in all the cases) ... the assembler programmer(s) was spending so much time manageing nigling hardware issues that they weren't paying attention to fundamental scale-up issues.
the rexx case (interpreted language) ... ok maybe not quite 100 times ... maybe it was only 10 times faster but provided 10 times more function. basically something like 15k-20k lines of assembler replaced with some interesting 120 lines of assembler and 3k lines of rexx.
the rewrite in C was "routes" part of airline res system ... which had been assembler. the initial pass was 100 times faster ... but they then also wanted ten impossible things that they couldn't currently do; adding support for the ten impossible things then slowed it down to only 10 times faster. however even in C there were some nigling hardware issues ... depending on how one loop was coded met a factor of three times total difference in the overall thruput because of some hardware cache stride issues.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: formal fips186-2/x9.62 definition for eal 5/6 evaluation Newsgroups: sci.crypt Date: Thu, 08 Aug 2002 12:51:12 GMT"Mads Rasmussen" writes:
fips186-2 & x9.62 standards cross reference each other for ecdsa.
eal is common criteria ... typically covers lots more than fips140
... although fips140 issues may be included in common criteria
evaluation.
https://web.archive.org/web/20021017070907/http://csrc.nist.gov/cc/ccv20/ccv2list.htm
https://web.archive.org/web/20030129051918/http://www.commoncriteria.org/
http://niap.nist.gov/
https://web.archive.org/web/20030130132546/http://www.niap.nist.gov/
this has a little about evaluation methodology in common criteria
http://csrc.nist.gov/cc/cem/cemlist.htm
https://web.archive.org/web/20021016194114/http://csrc.nist.gov/cc/cem/cemlist.htm
at least eal levels 1-4.
i'm looking at eal 5/6 for ecdsa which requires formal (or at least semi-formal) specification of ecdsa for the evaulation process.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: Summary: Robots of Doom. Newsgroups: rec.arts.sf.science,comp.ai.philosophy,rec.arts.sf.written,alt.folklore.computers Date: Thu, 08 Aug 2002 12:55:37 GMTJim Balter writes:
... well at least the rexx rewrite took part time for 3 months elapsed time .... I don't know what the original implementation time took, but they had something like 15-20 full time people just maintaining the code.
--
Anne & Lynn Wheeler | lynn@garlic.com - https://www.garlic.com/~lynn/
From: Anne & Lynn Wheeler <lynn@garlic.com> Subject: Re: formal fips186-2/x9.62 definition for eal 5/6 evaluation Newsgroups: sci.crypt Date: Thu, 08 Aug 2002 16:22:20 GMTdjohn37050@aol.com (DJohn37050) writes: