text: United States Patent: 7392395 ( 1 of 1 ) United States Patent 7,392,395 Ginter , et al. June 24, 2008 Trusted and secure techniques, systems and methods for item delivery and execution Abstract Documents and other items can be delivered electronically from sender to recipient with a level of trustedness approaching or exceeding that provided by a personal document courier. A trusted electronic go-between can validate, witness and/or archive transactions while, in some cases, actively participating in or directing the transaction. Printed or imaged documents can be marked using handwritten signature images, seal images, electronic fingerprinting, watermarking, and/or steganography. Electronic commercial transactions and transmissions take place in a reliable, "trusted" virtual distribution environment that provides significant efficiency and cost savings benefits to users in addition to providing an extremely high degree of confidence and trustedness. The systems and techniques have many uses including but not limited to secure document delivery, execution of legal documents, and electronic data interchange (EDI). Inventors: Ginter; Karl L. (Beltsville, MD), Shear; Victor H. (Bethesda, MD), Spahn; Francis J. (El Cerrito, CA), Van Wie; David M. (Sunnyvale, CA), Weber; Robert P. (Menlo Park, CA) Assignee: Intertrust Technologies Corp. (Sunnyvale, CA) Appl. No.: 11/102,216 Filed: April 7, 2005 Related U.S. Patent Documents Application NumberFiling DatePatent NumberIssue Date 09632944Aug., 2000 09221479Dec., 19986185683 08699711Aug., 1996 08388107Feb., 1995 Current U.S. Class: 713/176 ; 348/E5.006; 348/E5.008; 348/E7.06; 348/E7.07; 375/E7.009; 375/E7.024; 705/52 Current International Class: H04L 9/00 (20060101) Field of Search: 713/176 References Cited [Referenced By] U.S. Patent Documents 3573747 April 1971 Adams et al. 3609697 September 1971 Blevins 3790700 February 1974 Callais et al. 3796830 March 1974 Smith 3798359 March 1974 Feistel 3798360 March 1974 Feistel 3798605 March 1974 Feistel 3806874 April 1974 Ehrat 3806882 April 1974 Clarke 3829833 August 1974 Freeny, Jr. 3845391 October 1974 Crosby 3906448 September 1975 Henriques 3911397 October 1975 Freeny, Jr. 3924065 December 1975 Freeny, Jr. 3931504 January 1976 Jacoby 3946200 March 1976 Juodikis 3946220 March 1976 Brobeck et al. 3956615 May 1976 Anderson et al. 3958081 May 1976 Ehrsam et al. 3970992 July 1976 Boothroyd et al. 3996449 December 1976 Attanasio et al. 4020326 April 1977 Coulthurst 4048619 September 1977 Forman, Jr. et al. 4071911 January 1978 Mazur 4104721 August 1978 Markstein et al. 4112421 September 1978 Freeny, Jr. 4120030 October 1978 Johnstone 4141005 February 1979 Bonner et al. 4162483 July 1979 Entenman 4163280 July 1979 Mori et al. 4168396 September 1979 Best 4183085 January 1980 Roberts et al. 4196310 April 1980 Forman et al. 4200913 April 1980 Kuhar et al. 4209787 June 1980 Freeny, Jr. 4217588 August 1980 Freeny, Jr. 4220991 September 1980 Hamano et al. 4232193 November 1980 Gerard 4232317 November 1980 Freeny, Jr. 4236217 November 1980 Kennedy 4246638 January 1981 Thomas 4253157 February 1981 Kirschner et al. 4259720 March 1981 Campbell 4262329 April 1981 Bright et al. 4265371 May 1981 Desai et al. 4270182 May 1981 Asija 4278837 July 1981 Best 4305131 December 1981 Best 4306289 December 1981 Lumley 4309569 January 1982 Merkle 4319079 March 1982 Best 4321672 March 1982 Braun et al. 4323921 April 1982 Guillou 4328544 May 1982 Baldwin et al. 4337483 June 1982 Guillou 4361877 November 1982 Dyer et al. 4375579 March 1983 Davida et al. 4405829 September 1983 Rivest et al. 4433207 February 1984 Best 4434464 February 1984 Suzuki et al. 4442484 April 1984 Childs, Jr. et al. 4442486 April 1984 Mayer 4446519 May 1984 Thomas 4454594 June 1984 Heffron et al. 4458315 July 1984 Uchenick 4462076 July 1984 Smith, III 4462078 July 1984 Ross 4465901 August 1984 Best 4471163 September 1984 Donald et al. 4471216 September 1984 Herve 4484217 November 1984 Block et al. 4494156 January 1985 Kadison et al. 4513174 April 1985 Herman 4523271 June 1985 Levien 4525599 June 1985 Curran et al. 4528588 July 1985 Lofberg 4528643 July 1985 Freeny, Jr. 4529870 July 1985 Chaum 4553252 November 1985 Egendorf 4558176 December 1985 Arnold et al. 4558413 December 1985 Schmidt et al. 4562305 December 1985 Gaffney, Jr. 4562306 December 1985 Chou et al. 4562495 December 1985 Bond et al. 4573119 February 1986 Westheimer et al. 4577289 March 1986 Comerford et al. 4578530 March 1986 Zeidler 4584639 April 1986 Hardy 4584641 April 1986 Guglielmino 4588991 May 1986 Atalla 4589064 May 1986 Chiba et al. 4590552 May 1986 Guttag et al. 4593183 June 1986 Fukatsu 4593353 June 1986 Pickholtz 4593376 June 1986 Volk 4595950 June 1986 Lofberg 4597058 June 1986 Izumi et al. 4598288 July 1986 Yarbrough et al. 4599489 July 1986 Cargile 4609777 September 1986 Cargile 4609985 September 1986 Dozier 4621321 November 1986 Boebert et al. 4621334 November 1986 Garcia 4634807 January 1987 Chorley et al. 4644493 February 1987 Chandra et al. 4646234 February 1987 Tolman et al. 4649515 March 1987 Thompson et al. 4652990 March 1987 Pailen et al. 4658093 April 1987 Hellman 4670857 June 1987 Rackman 4672572 June 1987 Alsberg 4672605 June 1987 Hustig et al. 4677434 June 1987 Fascenda 4677552 June 1987 Sibley, Jr. 4680731 July 1987 Izumi et al. 4683553 July 1987 Mollier 4683968 August 1987 Appelbaum et al. 4685056 August 1987 Barnsdale, Jr. et al. 4688169 August 1987 Joshi 4691350 September 1987 Kleijne et al. 4696034 September 1987 Wiedemer 4700296 October 1987 Palmer, Jr. et al. 4701846 October 1987 Ikeda et al. 4712238 December 1987 Gilhousen et al. 4713753 December 1987 Boebert et al. 4740890 April 1988 William 4747139 May 1988 Taaffe 4748561 May 1988 Brown 4757533 July 1988 Allen et al. 4757534 July 1988 Matyas et al. 4757914 July 1988 Roth et al. 4768087 August 1988 Taub et al. 4780821 October 1988 Crossley 4791565 December 1988 Dunham et al. 4796181 January 1989 Wiedemer 4796220 January 1989 Wolfe 4799156 January 1989 Shavit et al. 4807288 February 1989 Ugon et al. 4816655 March 1989 Musyck et al. 4817140 March 1989 Chandra et al. 4823264 April 1989 Deming 4827508 May 1989 Shear 4858121 August 1989 Barber et al. 4864494 September 1989 Kobus, Jr. 4864616 September 1989 Pond et al. 4866769 September 1989 Karp 4868736 September 1989 Walker 4868877 September 1989 Fischer 4881197 November 1989 Fischer 4888798 December 1989 Earnest 4893248 January 1990 Pitts et al. 4893332 January 1990 Brown 4903296 February 1990 Chandra et al. 4907269 March 1990 Guillon et al. 4919545 April 1990 Yu 4924378 May 1990 Hershey et al. 4926480 May 1990 Chaum 4930073 May 1990 Cina, Jr. 4937863 June 1990 Robert et al. 4941175 July 1990 Enescu et al. 4949187 August 1990 Cohen 4953209 August 1990 Ryder, Sr. et al. 4962533 October 1990 Krueger et al. 4967403 October 1990 Ogawa 4975647 December 1990 Downer et al. 4975878 December 1990 Boddu et al. 4977594 December 1990 Shear 4995082 February 1991 Schnorr 4999806 March 1991 Chernow et al. 5001752 March 1991 Fischer 5005122 April 1991 Griffin et al. 5005200 April 1991 Fischer 5010571 April 1991 Katznelson 5014234 May 1991 Edwards, Jr. 5022080 June 1991 Durst et al. 5023907 June 1991 Johnson et al. 5027397 June 1991 Double et al. 5032979 July 1991 Hecht et al. 5047928 September 1991 Wiedemer 5048085 September 1991 Abraham et al. 5050212 September 1991 Dyson 5050213 September 1991 Shear 5051932 September 1991 Inoue et al. 5058162 October 1991 Santon et al. 5065429 November 1991 Lang 5079648 January 1992 Maufe 5091966 February 1992 Bloomberg et al. 5103392 April 1992 Mori 5103459 April 1992 Gilhousen et al. 5103476 April 1992 Waite et al. 5109413 April 1992 Comerford et al. 5111390 May 1992 Ketcham 5113518 May 1992 Durst, Jr. et al. 5119493 June 1992 Janis et al. 5126936 June 1992 Champion et al. 5128525 July 1992 Stearns et al. 5129084 July 1992 Kelly, Jr. et al. 5136643 August 1992 Fischer 5136646 August 1992 Haber et al. 5136647 August 1992 Haber et al. 5136716 August 1992 Harvey et al. 5138712 August 1992 Corbin 5146575 September 1992 Nolan, Jr. 5148481 September 1992 Abraham et al. 5150407 September 1992 Chan 5155680 October 1992 Wiedemer 5163091 November 1992 Graziano et al. 5164988 November 1992 Matyas et al. 5168147 December 1992 Bloomberg 5185717 February 1993 Mori 5187787 February 1993 Skeen et al. 5191573 March 1993 Hair 5191613 March 1993 Graziano et al. 5191693 March 1993 Umetsu 5199066 March 1993 Logan 5199074 March 1993 Thor 5201046 April 1993 Goldberg et al. 5201047 April 1993 Maki et al. 5204897 April 1993 Wyman 5206951 April 1993 Khoyi et al. 5208748 May 1993 Flores et al. 5214700 May 1993 Pinkas et al. 5214702 May 1993 Fischer 5216603 June 1993 Flores et al. 5218605 June 1993 Low et al. 5221833 June 1993 Hecht 5222134 June 1993 Waite et al. 5224160 June 1993 Paulini et al. 5224163 June 1993 Gasser et al. 5235642 August 1993 Wobber et al. 5237614 August 1993 Weiss 5241671 August 1993 Reed et al. 5245165 September 1993 Zhang 5247575 September 1993 Sprague et al. 5251294 October 1993 Abelow 5257369 October 1993 Skeen et al. 5260999 November 1993 Wyman 5263157 November 1993 Janis 5263158 November 1993 Janis 5263165 November 1993 Janis 5265164 November 1993 Matyas et al. 5276735 January 1994 Boebert et al. 5276901 January 1994 Howell et al. 5280479 January 1994 Mary 5283830 February 1994 Hinsley et al. 5285494 February 1994 Sprecher et al. 5287407 February 1994 Holmes 5291598 March 1994 Grundy 5301231 April 1994 Abraham et al. 5301326 April 1994 Linnett et al. 5311591 May 1994 Fischer 5315448 May 1994 Ryan 5319705 June 1994 Halter et al. 5319735 June 1994 Preuss et al. 5319785 June 1994 Thaller 5325524 June 1994 Black et al. 5335169 August 1994 Chong 5335346 August 1994 Fabbio 5337357 August 1994 Chou et al. 5337360 August 1994 Fischer 5341429 August 1994 Stringer et al. 5343526 August 1994 Lassers 5343527 August 1994 Moore 5347579 September 1994 Blandford 5349642 September 1994 Kingdon 5351293 September 1994 Michener et al. 5354097 October 1994 Tel 5355474 October 1994 Thuraisngham et al. 5359721 October 1994 Kempf et al. 5361359 November 1994 Tajalli et al. 5365587 November 1994 Campbell et al. 5367621 November 1994 Cohen et al. 5369702 November 1994 Shanton 5369707 November 1994 Follendore, III 5371792 December 1994 Asai et al. 5373440 December 1994 Cohen et al. 5373561 December 1994 Haber et al. 5375240 December 1994 Grundy 5383113 January 1995 Kight et al. 5388211 February 1995 Hornbuckle 5390247 February 1995 Fischer 5390297 February 1995 Barber et al. 5390330 February 1995 Talati 5392220 February 1995 Van den Hamer et al. 5392390 February 1995 Crozier 5394469 February 1995 Nagel et al. 5408501 April 1995 Cornaby 5410598 April 1995 Shear 5412717 May 1995 Fischer 5418713 May 1995 Allen 5420927 May 1995 Michali 5421006 May 1995 Jablon et al. 5422953 June 1995 Fischer 5428606 June 1995 Moskowitz 5428685 June 1995 Kadooka et al. 5432851 July 1995 Scheidt et al. 5432928 July 1995 Sherman 5432950 July 1995 Sibigtroth 5438508 August 1995 Wyman 5440634 August 1995 Jones et al. 5442645 August 1995 Ugon et al. 5444779 August 1995 Daniele 5449895 September 1995 Hecht et al. 5449896 September 1995 Hecht et al. 5450490 September 1995 Jensen et al. 5450493 September 1995 Maher 5453601 September 1995 Rosen 5453605 September 1995 Hecht et al. 5455407 October 1995 Rosen 5455861 October 1995 Faucher et al. 5455953 October 1995 Russell 5457746 October 1995 Dolphin 5457747 October 1995 Drexler et al. 5458494 October 1995 Krohn et al. 5463565 October 1995 Cookson et al. 5473687 December 1995 Lipscomb et al. 5473692 December 1995 Davis 5479509 December 1995 Ugon 5485622 January 1996 Yamaki 5490216 February 1996 Richardson, III 5491800 February 1996 Goldsmith et al. 5497479 March 1996 Hornbuckle 5497491 March 1996 Mitchell et al. 5499298 March 1996 Narasimhalu et al. 5504757 April 1996 Cook et al. 5504818 April 1996 Okano 5504837 April 1996 Griffeth et al. 5505461 April 1996 Bell et al. 5508913 April 1996 Yamamoto et al. 5509070 April 1996 Schull 5513261 April 1996 Maher 5517518 May 1996 Morson et al. 5521815 May 1996 Rose, Jr. 5524933 June 1996 Kunt et al. 5530235 June 1996 Stefik et al. 5530752 June 1996 Rubin 5533123 July 1996 Force et al. 5534855 July 1996 Shockley et al. 5534975 July 1996 Stefik et al. 5535322 July 1996 Hecht 5537526 July 1996 Anderson et al. 5539735 July 1996 Moskowitz 5539828 July 1996 Davis 5550971 August 1996 Brunner et al. 5553282 September 1996 Parrish et al. 5557518 September 1996 Rosen 5557798 September 1996 Skeen et al. 5563946 October 1996 Cooper et al. 5568552 October 1996 Davis 5572673 November 1996 Shurts 5574962 November 1996 Fardeau et al. 5577209 November 1996 Boyle et al. 5581686 December 1996 Koppolu et al. 5581800 December 1996 Fardeau et al. 5592549 January 1997 Nagel et al. 5603031 February 1997 White et al. 5606609 February 1997 Houser et al. 5613004 March 1997 Cooperman et al. 5621797 April 1997 Rosen 5625693 April 1997 Rohatgi et al. 5629770 May 1997 Brassil et al. 5629980 May 1997 Stefik et al. 5633932 May 1997 Davis et al. 5634012 May 1997 Stefik et al. 5636276 June 1997 Brugger 5636292 June 1997 Rhoads 5638443 June 1997 Stefik et al. 5638504 June 1997 Scott et al. 5640546 June 1997 Gopinath et al. 5644686 July 1997 Hekmatpour 5646997 July 1997 Barton 5649099 July 1997 Theimer et al. 5655077 August 1997 Jones et al. 5671279 September 1997 Elgamal 5678170 October 1997 Grube et al. 5682027 October 1997 Bertina et al. 5687236 November 1997 Moskowitz et al. 5689565 November 1997 Spies et al. 5689566 November 1997 Nguyen 5689587 November 1997 Bender et al. 5692047 November 1997 McManis 5692180 November 1997 Lee 5692980 December 1997 Trotman 5699427 December 1997 Chow et al. 5710834 January 1998 Rhoads 5715314 February 1998 Payne et al. 5715403 February 1998 Stefik 5717923 February 1998 Dedrick 5721788 February 1998 Powell et al. 5724424 March 1998 Gifford 5724425 March 1998 Chang et al. 5732398 March 1998 Tagawa 5734719 March 1998 Tsevdos et al. 5740549 April 1998 Reilly et al. 5745569 April 1998 Moskowitz et al. 5745604 April 1998 Rhoads 5745678 April 1998 Herzberg et al. 5748763 May 1998 Rhoads 5748783 May 1998 Rhoads 5748960 May 1998 Fischer 5754849 May 1998 Dyer et al. 5757914 May 1998 McManis 5758152 May 1998 LeTourneau 5759101 June 1998 Von Kohorn 5765152 June 1998 Erickson 5768426 June 1998 Rhoads 5774872 June 1998 Golden et al. 5778385 July 1998 Pratt 5787334 July 1998 Fardeau et al. 5802590 September 1998 Draves 5819263 October 1998 Bromley et al. 5832119 November 1998 Rhoads 5842173 November 1998 Strum et al. 5845281 December 1998 Benson et al. 5878421 March 1999 Ferrel et al. 5892899 April 1999 Aucsmith et al. 5892900 April 1999 Ginter et al. 5896454 April 1999 Cookson et al. 5910987 June 1999 Ginter et al. 5915019 June 1999 Ginter et al. 5917912 June 1999 Ginter et al. 5920861 July 1999 Hall et al. 5940504 August 1999 Griswold 5940505 August 1999 Kanamaru 5943422 August 1999 Van Wie et al. 5949876 September 1999 Ginter et al. 5956408 September 1999 Arnold 5966440 October 1999 Hair 5978484 November 1999 Apperson et al. 5982891 November 1999 Ginter et al. 5991876 November 1999 Johnson et al. 5996756 December 1999 Schmodde et al. 5999949 December 1999 Crandall 6009170 December 1999 Sako et al. 6016393 January 2000 White et al. 6026193 February 2000 Rhoads 6044205 March 2000 Reed et al. 6085238 July 2000 Yuasa et al. 6102965 August 2000 Dye et al. 6112181 August 2000 Shear et al. 6135646 October 2000 Kahn et al. 6138119 October 2000 Hall et al. 6157721 December 2000 Shear et al. 6185683 February 2001 Ginter et al. 6237786 May 2001 Ginter et al. 6240185 May 2001 Van Wie et al. 6253193 June 2001 Ginter et al. 6292569 September 2001 Shear et al. 6363488 March 2002 Ginter et al. 6389402 May 2002 Ginter et al. 6393484 May 2002 Massarani 6427140 July 2002 Ginter et al. 6449367 September 2002 Van Wie et al. 6477559 November 2002 Veluvali et al. 6519615 February 2003 Wollrath et al. 6590998 July 2003 Rhoads 6618484 September 2003 Van Wie et al. 6640304 October 2003 Ginter et al. 6647130 November 2003 Rhoads 6658568 December 2003 Ginter et al. 6668325 December 2003 Collberg et al. 6785815 August 2004 Serret-Avila et al. 6807534 October 2004 Erickson 6832316 December 2004 Sibert 6938021 August 2005 Shear et al. 6944555 September 2005 Blackett et al. 6961854 November 2005 Serret-Avila et al. 7035427 April 2006 Rhoads 2001/0042043 November 2001 Shear et al. 2002/0023214 February 2002 Shear et al. 2002/0048369 April 2002 Ginter et al. 2002/0087859 July 2002 Weeks et al. 2002/0112171 August 2002 Ginter et al. 2002/0152173 October 2002 Rudd 2003/0023856 January 2003 Horne et al. 2003/0041239 February 2003 Shear et al. 2003/0046244 March 2003 Shear et al. 2003/0069748 April 2003 Shear et al. 2003/0069749 April 2003 Shear et al. 2003/0084003 May 2003 Pinkas et al. 2003/0105721 June 2003 Ginter et al. 2003/0163431 August 2003 Ginter et al. 2004/0054630 March 2004 Ginter et al. 2004/0059951 March 2004 Pinkas et al. 2004/0073813 April 2004 Pinkas et al. 2004/0103305 May 2004 Ginter et al. 2004/0107356 June 2004 Shamoon et al. 2004/0123129 June 2004 Ginter et al. 2004/0133793 July 2004 Ginter et al 2005/0027871 February 2005 Bradley et al. 2005/0050332 March 2005 Serret-Avila et al. 2005/0060560 March 2005 Sibert 2005/0060584 March 2005 Ginter et al. 2005/0108555 May 2005 Sibert Foreign Patent Documents A-36815/97 Feb., 1998 AU A-36816/97 Feb., 1998 AU A-36840/97 Feb., 1998 AU 9 004 79 Dec., 1984 BE 29 43 436 Oct., 1979 DE 3 803 982 Jan., 1990 DE 0 084 441 Jul., 1983 EP 0 128 672 Dec., 1984 EP 0 135 422 Mar., 1985 EP 0 180 460 May., 1986 EP 0 367 700 May., 1990 EP 0 370 146 May., 1990 EP 0 398 645 Nov., 1990 EP 0 399 822 Nov., 1990 EP 0 421 409 Apr., 1991 EP 0 456 386 Nov., 1991 EP 0 469 864 Feb., 1992 EP 0 469 894 Feb., 1992 EP 0 565 314 Oct., 1993 EP 0 567 800 Nov., 1993 EP 0 570 123 Nov., 1993 EP 0 593 305 Apr., 1994 EP 0 651 554 May., 1995 EP 0 653 695 May., 1995 EP 0 668 695 Aug., 1995 EP 0 668 695 Aug., 1995 EP 0 695 985 Feb., 1996 EP 0 696 798 Feb., 1996 EP 0 714 204 May., 1996 EP 0 715 243 Jun., 1996 EP 0 715 244 Jun., 1996 EP 0 715 245 Jun., 1996 EP 0 715 246 Jun., 1996 EP 0 715 247 Jun., 1996 EP 0 725 376 Aug., 1996 EP 0 749 081 Dec., 1996 EP 0 763 936 Mar., 1997 EP 0 778 513 Jun., 1997 EP 0 795 873 Sep., 1997 EP 0 800 312 Oct., 1997 EP 0 913 757 May., 1999 EP 2136175 Sep., 1984 GB 2264796 Sep., 1993 GB 2294348 Apr., 1996 GB 2295947 Jun., 1996 GB 57-000726 Jan., 1982 JP 61 121145 Jun., 1986 JP 62-225059 Oct., 1987 JP 62-241061 Oct., 1987 JP 63 129564 Jun., 1988 JP 63 289646 Nov., 1988 JP 01-068835 Mar., 1989 JP 01 68853 Mar., 1989 JP 64-068835 Mar., 1989 JP 01 248891 Oct., 1989 JP 01 296363 Nov., 1989 JP 02-242352 Sep., 1990 JP 02-247763 Oct., 1990 JP 02-294855 Dec., 1990 JP 04 117548 Apr., 1992 JP 04 504794 Aug., 1992 JP 04-369068 Dec., 1992 JP 05-020359 Jan., 1993 JP 05 173892 Jul., 1993 JP 05-181734 Jul., 1993 JP 05-257783 Oct., 1993 JP 05 258463 Oct., 1993 JP 05-268415 Oct., 1993 JP 06 501120 Jan., 1994 JP 06 152585 May., 1994 JP 06 161719 Jun., 1994 JP 06-175794 Jun., 1994 JP 06-215010 Aug., 1994 JP 06-225059 Aug., 1994 JP 06 250924 Sep., 1994 JP 07-056794 Mar., 1995 JP 07-084852 Mar., 1995 JP 07-141138 Jun., 1995 JP 07-200317 Aug., 1995 JP 07-200492 Aug., 1995 JP 07-244639 Sep., 1995 JP 07 319681 Dec., 1995 JP 08-137795 May., 1996 JP 08-152990 Jun., 1996 JP 08-185292 Jul., 1996 JP 08-185298 Jul., 1996 JP WO 85/02310 May., 1985 WO WO 85/03584 Aug., 1985 WO WO 90/02382 Mar., 1990 WO WO 90/06438 Apr., 1992 WO WO 92/22870 Dec., 1992 WO WO 93/01550 Jan., 1993 WO WO 94/01821 Jan., 1994 WO WO 94/03859 Feb., 1994 WO WO 94/06103 Mar., 1994 WO WO 94/16395 Jul., 1994 WO WO 94/18620 Aug., 1994 WO WO 94/22266 Sep., 1994 WO WO 94/27406 Nov., 1994 WO WO 95/14289 May., 1995 WO WO 96/00963 Jan., 1996 WO WO 96/03835 Feb., 1996 WO WO 96/05698 Feb., 1996 WO WO 96/06503 Feb., 1996 WO WO 96/13013 May., 1996 WO WO 96/17467 Jun., 1996 WO WO 96/21192 Jul., 1996 WO WO 96/24092 Aug., 1996 WO WO 96/27155 Sep., 1996 WO WO 97/03423 Jan., 1997 WO WO 97/07656 Mar., 1997 WO WO 97/22074 Jun., 1997 WO WO 97/25816 Jul., 1997 WO WO 97/32251 Sep., 1997 WO WO 97/43761 Nov., 1997 WO WO 97/48203 Dec., 1997 WO WO 98/09209 Mar., 1998 WO WO 98/10381 Mar., 1998 WO WO 98/37481 Aug., 1998 WO WO 98/45768 Oct., 1998 WO WO 99/01815 Jan., 1999 WO WO 99/24928 May., 1999 WO WO 99/48296 Sep., 1999 WO WO 00/75925 Dec., 2000 WO WO 01/06374 Jan., 2001 WO WO 01/09702 Feb., 2001 WO WO 01/10076 Feb., 2001 WO Other References "Information Society Facing a Turning Point, Information Flood, How to Stand Against Flood of Copies," Nikkei Byte, 92:316-319, 1991. cited by other . Garrett et al., "Toward an electronic Copyright Management System," J. of the Amer. Soc. for Info., 44(8):468-473, 1993. cited by other . Kozuka et al., "Electronic Magazine Editing Software for 3DO," National Technical Report, Matsushita Electric Industrial Co., Ltd., 40(6):88-97, 1994. cited by other . Rozenblit, Moshe, "Secure Software Distribution," IEEE Network Operations and Management Symposium, 2:486-496, 1994. cited by other . Seki et al., "A Proposal for New Software Distribution System Using a Secret Code," Research Report of Information Processing Societies, 93(64):19-28, 1993. cited by other . Terada, Minoru, "Exhausting Software," bit, Kyoritsu Shuppan Co., Ltd., 26(10):12-18, 1994. cited by other . Torii et al., "System Architecture for Super Distribution," Technical Research Report of Institute of Electronics, Information and Communication Engineers, 94(240):59-66, 1994. cited by other . Ueki et al., "Accounting Processing in Right Management Mechanism for Super Distribution," Study Report of Information Processing Societies, 90(1):1-10, 1990. cited by other . A Brief History of the Green Project, viewed on Mar. 12, 2002 at <http://java.sun.com/people/jag/green/index.html> pp. 1-2. cited by other . A Guide to Understanding Security Modeling in Trusted Systems, National Security Agency, Oct. 1992, 122 pages. cited by other . A Publication of the Electronic Frontier Foundation, EFFector Online, vol. 6, No. 6, 8 pages, Dec. 6, 1993. cited by other . A2b's Recent Press Coverage, 1998. cited by other . Abadi, M. et al., "Authentication and Delegation with Smart-cards," Technical Report 67, DEC Systems Research Center, Oct. 1990, available at <http://citeseer.nj.nec.com/article/abadi92authentication.html>, 22 pages. cited by other . Avery, et al., "Recommender Systems for Evaluating Computer Messages," Communications of the ACM, Mar. 1997, pp. 88-89. cited by other . Background on the Administration's Telecommunications Policy Reform Initiative, News Release, The White House, Office of the President, Jan. 11, 1994, 7 pages. cited by other . Baggett, C., "Cable's Emerging Role in the Information Superhighway," Cable Labs, (undated), 13 slides. cited by other . Baker, R.H., The Computer Security Handbook, Tab Books, Inc., 1985. cited by other . Balbanovic, et al., Content-based, Collaborative Recommendation, Communications of the ACM, Mar. 1997, pp. 66-72. cited by other . Barnes, H., memo to Henry LaMuth, subject: George Gilder articles, May 31, 1994, 2 pages. cited by other . Bart, D., "Comments in the Matter of Public Hearing and Request for Comments on the International Aspects of the National Information Infrastructure," Before the Department of Commerce, Aug. 12, 1994, 17 pages. cited by other . Bartock, P.F., et al., "Guide to Securing Microsoft Windows NT Networks," National Security Agency, Sep. 18, 2001, pp. 1-132. cited by other . Baum, M., "Worldwide Electronic Commerce: Law, Policy and Controls Conference," (program details) Nov. 11, 1993, 18 pages. cited by other . Bellare, M., "iKP-A Family of Secure Electronic Payment Protocols," Apr. 16, 1995, pp. 1-19. cited by other . Bell-Labs Secure Technologies, "Information Vending Encryption System (IVES).TM.," Lucent Technologies, May 31, 2002, pp. 1-16. cited by other . Bellovin, S.M., "Encrypted Key Exchange: Password-Based Protocols Secure Against Dictionary Attacks," Proceedings of the IEEE Symposium on Research in Security and Privacy, Oakland, California, May 1992, 13 pages. cited by other . Bellovin, S.M., "There Be Dragons," AT&T Bell Laboratories, Aug. 15, 1992, 16 pages. cited by other . Bender et al. "Techniques for Data Hiding," IBM Systems Journal, vol. 35, Nos. 3&4, 1996. cited by other . Berghal et al., "Protecting Ownership Rights Through Digital Watermarking," IEEE Computing, vol. 29, No. 7, Jul. 1996. cited by other . Berkovitz, S. et al., "Authentication of Mobile Agents," Mobile Agents and Security, Springer-Verlag, Giovanni Vigna, Ed., 1998, pp. 114-136. cited by other . Berners-Lee, T.J., et al., "Networked Information Services: The World-Wide Web," Computer Networks and ISDN Systems, 1992, pp. 454-459. cited by other . Bertino, Elisa, "Data Hiding and Security in Object-Oriented Databases," Dipartimento di Matematica, Universita di Genova, IEEE, 1992, pp. 338-347. cited by other . Best, R.M., "Preventing Software Piracy With Crypto-Microprocessors," Digest of Papers, VLSI: New Architectural Horizons, Feb. 1980, pp. 466-469. cited by other . Bickel, R., et al., "Guide to Securing Microsoft Windows XP," National Security Agency, Oct. 30, 2002, pp. 1-129. cited by other . Birrell, Andrew, D., et al., "A Global Authentication Service Without Global Trust," Proceedings of the IEEE Symposium on Security and Privacy, Oakland, California, Apr. 1986, pp. 1-11. cited by other . Bisbey II, R.L. et al., "Encapsulation: An Approach to Operating System Security," (USC/Information Science Institute, Marina Del Rey, CA), Oct. 1973, pp. 666-675. cited by other . Blaze, M. et al., "Decentralized Trust Management," Proc. IEEE Conference on Security and Privacy, 1996, pp. 164-173. cited by other . Blaze, M., "A Cryptographic File System for Unix," pre-print of paper for First ACM Conference on Computer and Communications Security, Fairfax, Virginia, Nov. 3-5, 1993, pp. 1-8. cited by other . Blaze, Matt, "Key Management in an Encrypting File System," Proc. Summer '94 USENIX Tech. Conference, Boston, MA. Jun. 1994, available at <http://www.usenix.org/publicaitons/libratry/proceedings/bos94/full.su- b.--papers/blaze.asp>, pp. 1-12. cited by other . Blaze, Matt, et al., "The Architecture and Implementaiton of Network Layer Security Under Unix", Columbia University and AT&T Bell Laboratories, 1994. cited by other . Blom, R. et al., "Encryption Methods in Data Networks," Ericsson Technics, No. 2, Stockholm, Sweden, 1978, 17 pages. cited by other . Boly, J.P. et al., "The Esprit Project Cafe: High Security Digital Payment Systems," Escorics 94, European Symposium on Research Computer Security, Springer-Verlas Berlin, 1994, pp. 217-230. cited by other . Boone, J.V.,et al., "The Start of Digital Revolution: Sigsaly Secure Digital Voice Communications in World War II," Dec. 10, 2002. cited by other . Borenstein, N., "MIME Extensions for Mail-Enabled Applications: Application/Safe-Tel and Multipart/Enabled-Mail," Nov. 1993, 24 pages. cited by other . Born, E, et al., "Discretionary Access Control by Means of Usage Conditions," Computers & Security, vol. 13, No. 5, 1994, pp. 437-450. cited by other . Brassil et al., "Electronic Marking and Identification Techniques to Discourage Document Copying," AT&T Bell Laboratories, Proc. Infocom 94, 1994. cited by other . Breon, R., et al., "Microsoft Office 97 Executable Content Security Risks and Countermeasures," National Security Agency, Dec. 20, 1999, pp. 1-44. cited by other . Brickell, E.F., et al., "The Skipjack Algorithm," Jul. 28, 1993, pp. 1-7. cited by other . Brockschmidt, Kraig, "A Primer on Designing Custom Controls," Microsoft Systems Journal, Mar./Apr. 1992, pp. 87-101. cited by other . Brockschmidt, Kraig, "Implementing OLE 2.0, Part III: Uniform Data Transfer with Data Objects," Microsoft Systems Journal, Dec. 1993, pp. 47-77. cited by other . Brockschmidt, Kraig, "Introducing OLE 2.0, Part 1: Windows Objects and the Component Object Model," Microsoft Systems Journal, Aug. 1993, pp. 15-23. cited by other . Brockschmidt, Kraig, "OLE 2.0 Part II: Implementing a Simple Windows Object Using Either C or C++," Microsoft Systems Journal, Oct. 1993, pp. 45-62. cited by other . Brockschmidt, Kraig, Inside OLE 2, Microsoft Press Programming Series, 1994. cited by other . Brown, Patrick W., "Digital Signatures: Can They Be Accepted as Legal Signatures in EDI?," 1st Conference on Computer and Communication Security, Nov. 1993, pp. 86-92. cited by other . Brumm, P., et al., 80386/80486 Assembly Language Programming, Windcrest/McGraw-Hill, 1993. cited by other . Bruner, R.E., "Power Agent, NetBot Help Advertisers Reach Internet Shoppers," Aug. 1997, 2 pages. cited by other . Brunnstein et al., "Intellectual Property Rights and new Technologies," Proceedings of the KnowRight '95 Conference, Aug. 1995. cited by other . Bureau Van Dijk, Management Report for Task 4.5: Feasibility Study of the Cited Agency, 1992-1993. cited by other . Bureau Van Dijk, Cited: Preparation of the Cited Model Functional Requirements Specifications; Discussion Paper (Revision 1), Jan. 16, 1991. cited by other . Bureau Van Dijk, Cited: Preparation of the Cited Model Functional Requirements Specifications; Reports of the Interviews with Five Cited Partners, (Partners: Sagem, Telesystemes, NTE, Elsevier, Oxford University Press), Apr. 5, 1991. cited by other . Bureau Van Dijk, Gestion Des Contrats; 497C.C.C.E.: Cited (Suite), Feb. 1993. cited by other . Byte.com, "Speaking the Same Language," May 1994, pp. 1-2. cited by other . Cabell, D., et al., "Software Protection," May 1985, pp. 35-37. cited by other . Cable Television and America's Telecommunications Infrastructure, (National Cable Television Association, Washington, D.C.), Apr. 1993, 19 pages. cited by other . Calas, C., "Distributed File System Over a Multilevel Secure Architecture Problems and Solutions," Computer Security, Escorics 94, Brighton, United Kingdom, Nov. 7-9, 1994, pp. 281-297. cited by other . CardTech/SecurTech 94 Conference Proceedings, "Building Foundations for Innovation," CardTech/SecurTech, Inc., Apr. 1994, 1,031 pages. cited by other . Caruso, D., "Technology, Digital Commerce: 2 Plans for Watermarks, Which Can Bind Proof of Authorship to Electronic Works," N.Y. Times, Aug. 7, 1995, p. D5. cited by other . Case, J., "A Simple Network Management Protocol (SNMP)," Network Working Group, May 1990, pp. 1-21. cited by other . Castano, S., et al., "Database Security," Addison-Wesley & Acm Press, 1995. cited by other . CGI Common Gateway Interface, Document from the Internet email@example.com, 1996, 1 page. cited by other . Champine, G., MIT Project Athena: A Model for Distributed Campus Computing, Digital Equuipment Corporation, 1991, 22 introductory pages, Chapter 1 (pp. 3-18); Chapter 2 (pp. 19-33); Chapter 3, (pp. 37-68); Chapter 4 (pp. 69-75); Chapter 5 (pp. 79-107); C. cited by other . Chase, Chevy, M.D., "DiscStore", Electronic Publishing Resources, 1991. cited by other . Chaum, D. et al. "Wallet databases with observers," Ernest F. Brickell, editor, Advances in Cryptology--CRYPTO '92, 12th Annual International Cryptology Conference, Santa Barbara, CA, Aug. 16-20, 1992, Proceedings, pp. 89-105. cited by other . Chaum, David L., "Achieving Electronic Privacy," Scientific American, Aug. 1992, 6 pages. cited by other . Chaum, David L., "Security Without Identification Card Computers to Make Big Brother Obsolete," Communications of the ACM, vol. 28., No. 10, Oct. 1985, pp. 1-24. cited by other . Chaum, David L., "Smart Card 2000," Selected Papers from the Second International Smart Card 2000 Conference, Oct. 4-6, 1989. cited by other . Chaum, David L., "Untraceable Electronic Cash," Extended Abstract, Center for Mathematics and Computer Science, 1988, pp. 319-327. cited by other . Chaum, David L., et al., "Implementing Capability-Based Protection Using Encryption," College of Engineering, University of California, Berkeley, Jul. 17, 1978, 12 pages. cited by other . Chess, D., "Security Issues in Mobile Code Systems," Mobile Agents and Security, Springer-Verlag, Giovanni Vigna, Ed., 1998, 14 pages. cited by other . Chor et al., "Tracing Traitors," Crypto 94, 1994, p. 257. cited by other . Choudhury, A.K., et al., "Copyright Protection for Electronic Publishing Over Computer Networks," AT&T Bell Laboratories, Murray Hill, N.J., submitted to IEEE Network Magazine, Jun. 1994, pp. 1-17. cited by other . Choy, D.M., et al., "A Digital Library System for Periodicals Distribution" , May 1996. cited by other . Cina Jr. et al., "ABYSS: A Basic Yorktown Security System PC Software Asset Protection Concepts," IBM Research Report No. RC 12401, IBM Thomas J. Watson Research Center, Dec. 18, 1986. cited by other . Cited: Copyright in Transmitted Electronic Documents, Special Interest Group, Cited Meeting, Heathrow, Sep. 22, 1993. cited by other . Cited: Final Report: A Guide to Cited Documentation, Espirit, Project 5469, ISBN 0-7123-2115-2, The Cited Consortium, Sep. 1994. cited by other . Clark, Paul C., et al., "BITS: A Smartcard Protected Operating System," Communications of the ACM, vol. 37, No. 11, Nov. 1994, pp. 66-70 & 94. cited by other . Clark, T., "Ad Service Gives Cash Back," <www.news.com/News/Item/0,4,13050,00.html> (visited Aug. 4, 1997), 2 pages. cited by other . Clarke et al., "Cryptography Issues in Plain Text," Privacy Law and Policy Reporter, 1996. cited by other . Coad, Peter, "Object-Oriented Patterns," Communications of the ACM, vol. 35, No. 9, Sep. 1992, pp. 152-159. cited by other . Cohen, F.B., "Operating System Protection Through Program Evolution," Computers & Security, vol. 12, No. 6, (Oxford, Great Britain) Oct. 1993, 22 pages. cited by other . Cohen, F.B., Protection and Security on the Information Superhighway, John Wiley & Sons, Inc., 1995. cited by other . Communications of the ACM, Intelligent Agents, vol. 37, No. 7, Jul. 1994, 170 pages. cited by other . Communications of the ACM, vol. 39, No. 6, Jun. 1996, 134 pages. cited by other . Competitive Analysis AT&T/a2b music, Jun. 16, 1998. cited by other . Computer Systems Policy Project (CSSP), Perspectives on the National Information Infrastructure: Ensuring Interoperability, Feb. 1994, 5 slides. cited by other . Constructing a High Assurance Mail Guard, Secure Computing, 1994, pp. 1-10. cited by other . Cook, S., "Net Results," PC World, Dec. 1985, pp. 270-328. cited by other . Copyright Ownership Projection in Computer-Assisted Training, COPICAT--8195, Esprit, Dec. 1993. cited by other . Copysmart--20517: "Cited Based Multi-media IPR Management on Cost Effective Smart Device," European Information Technology for Information Science, start date Dec. 1, 1995. cited by other . CopySmart (CSM) suit, European Information technology for Information Science. cited by other . Corbato, F.J., et al., "Introduction and Overview of the Multics System," viewed on Nov. 13, 2001 at <http://www.multicians.org/fjcc1.html> pp. 1-18. cited by other . Cornish, Graham, "Copyright Management of Document Supply in an Electronic Age," The Cited.TM. Solution, Interlending & Document Supply, vol. 21, No. 2, 1993, pp. 13-20. cited by other . Coutrot, Francois, et al., "A Single FConditional Access System for Satellite-Cable and Terrestrial TV", IEEE Transactions on Consumer Electronics, vol. 35, No. 3, Aug. 1989. cited by other . Cox, B., "Superdistribution," Wired, Sep. 1994, 2 pages. cited by other . Cox, Brad, "What if there is a Silver Bullet and the competition gets it first?" Journal of Object-Oriented Programming, Jun. 1992, available at <http://www.virtualschool.edu/cox/CoxWhatIfSilverBullet.html>, pp. 1-5. cited by other . CREANET--Creative Rights European Agency NETwork--Project Profile, Information Society Technologies, Feb. 18, 2000. cited by other . Crocker et al., "MIME Object Security Services," Network Working Group RFC 1848, Oct. 1995. cited by other . Cryptographic API Specification, Version 0.6, Microsoft, Mar. 1995. cited by other . Cunningham, D. et al., "AT&T, VLSI Technology Join To Improve Info Highway Security," (News Release) Jan. 31, 1995, 3 pages. cited by other . CUPID Protocols and Services (Version 1): "An Architectural Overview," Nov. 1992, available at <http//www.cni.org/projects/CUPID>, 25 pages, Nov. 20, 1997. cited by other . Curry, D.A., UNIX System Security: A Guide for Users and System Administrators, Addison-Wesley Publishing Company, Inc., 1992. cited by other . Curry, David A., "Improving the Security of Your Unix System," Final Report Apr. 1990, pp. 1-74. cited by other . Custer, H. "Inside Windows NT," Microsoft Press, Redmond WA, 1993. cited by other . Custer, H., Inside the Windows NT File System, Microsoft Press, 1994. cited by other . Cybenko, G, et al., "Cognitive Hacking: A Battle for the Mind," Computer, Aug. 2002, 0018-9162/02a2002 IEEE, pp. 50-56. cited by other . Data Network and Open System Communications, Directory: Information Technology--Open Systems Interconnection--The Directory: Overview of Concepts, Models, and Services, ITU-T Recommendation X.500, International Telecommunication Union, Nov. 1993. cited by other . Data Widgets 2.0: Programmer's Guide, Sheridan Software Systems, Inc., 1993-1995. cited by other . Date, C.J., "An Introduction to Database Systems," 4th. Ed., vol. 1, Addison-Wesley Publishing Company, 1987. cited by other . Davies, D. et al., Security for Computer Networks, 2nd ed., John Wiley & Sons, 1989, 22 introductory pages and pp. 1-377. cited by other . Davin, J., et al., "SNMP Administrative Model," Network Working Group, Jul. 1992, pp. 1-22. cited by other . DCE Technology at Work, Distributed Computing Environment, http://www.opengroup.org/tech/dce/ tech/tech.htm, Nov. 7, 2000, pp. 1-3. cited by other . Deering, S.E., "Host Extensions for IP Multicasting," Network Working Group, RFC 1112, Aug. 1989. cited by other . Deliverable D3: Specification of the Infrastructure and Explanation of Trust and Confidence Building Solutions, Ver. 0.1, Telenet, Jul. 18, 2000. cited by other . Dempsey L. et al., "The Warwick Metadata Workshop: A Framework for the Deployment of Resource Description," D-Lib Magazine, Jul. 15, 1996, 8 pages. cited by other . Denning, A., OLE Controls Inside Out, Microsoft Press, 1995. cited by other . Denning, Dorothy E.R., "Secure Personal Computing in an Insecure Network," Communications of the ACM, Aug. 1979, vol. 22, No. 8, pp. 476-482. cited by other . Denning, Dorothy E.R., Cryptography and Data Security, Addison-Wesley Publishing Company, 1982, Reprinted with corrections, Jan. 1983. cited by other . Denning, Dorothy E.R., et al., "Data Security," 11 Computing Surveys, No. 3, Sep. 1979, pp. 227-249. cited by other . Denning, P.J., Computer Under Attack: Intruders, Worms, and Viruses, ACM Press, 1990. cited by other . Department of Defense Computer Security Center, "Department of Defense Password Management Guideline," Department of Defense Computer Security Center, Apr. 12, 1985, pp. 1-34. cited by other . Department of Defense Standard, "Department of Defense Trusted Computer System Evaluation Criteria," Dec. 1985, pp. 1-72. cited by other . Deutsch, P., "GZIP File Format Specification Version 4.3," Network Working Group, May 1996, pp. 12. cited by other . Diffie, Whitfield, "Authentication and Authenticated Key Exchanges", Sun Microsystems and Bell-Northern Research, Mar. 6, 1992. cited by other . Diffie, Whitfield, "The First Ten Years of Public-Key Cryptography", Proceedings of the IEEE, vol. 76, No. 5, May 1988. cited by other . Diffie, Whitfield, et al., "New Directions in Cryptography," IEEE Transactions on Information Theory, vol. 22, No. 6, Nov. 1976, pp. 644-651. cited by other . Diffie, Whitfield, et al., "Privacy and Authentication: An Introduction to Cryptography," Proceedings of the IEEE, vol. 67, No. 3, Mar. 1979, pp. 397-427. cited by other . Diffie, Whitfield, et al., Privacy on the Line: The Politics of Wiretapping and Encryption, Massachusetts Institute of Technology, 1998. cited by other . Digital Broadband Delivery System, Phase 1.0, System Overview, Revision 1.0, Scientific Atlanta, 1997. cited by other . DiLascia, Paul, "OLE Made Almost Easy: Creating Containers and Servers Using MFC 2.5," Microsoft Systems Journal, Apr. 1994, pp. 13-33. cited by other . DiscStore (Electronic Publishing Resources, Chevy Chase, MD, 1991, 3 pages. cited by other . Dougherty, D., et al., The Mosaic Handbook for the X Window System, O'Reilly & Associates, 1994. cited by other . Downs, D.D., et al., "Issues in Discretionary Access Control," Proceedings of the 1985 Symposium on Security and Privacy, Apr. 22-24, 1985, Oakland, California, pp. 208-218. cited by other . DSP56000/DSP56001 Digital Signal Processor User's Manual, (Motorola), 1990, p. 2-2. cited by other . Dusse, S.R. et al., "A Cryptographic Library for the Motorola 56000," Advances in Cryptology-Proceedings of Eurocrypt 90 (I.M. Damgard, ed., Springer-Verlag), 1991, pp. 230-244. cited by other . Dyson, E., "Intellectual Value," Wired Magazine, Jul. 1995, pp. 136-141 and 182-184. cited by other . Eastlake III, D., "Physical Link Security Type of Service," Network Working Group RFC 1455, May, 1993. cited by other . Eastlake III, D., et al., "Randomness Recommendations for Security," Network Working Group RFC 1750, Dec. 1994. cited by other . EFT Network Data Book; 1993 Edition, Bank Network News, vol. 11, No. 13, Nov. 1992. cited by other . Electronic Reverse Copyright Management System (ERCOMS), International Institute for Electronic Library Research, website updated by Ramsden, Anne, Jul. 22, 1996. cited by other . Ellison, C. et al., "SPKI Certificate Theory," Internet Engineering Task Force (IETF) RFC 2693, Sep. 1999, 38 pages, available at http://www.ietf.org/rfc/rfc26939.txt?number=2693. cited by other . E-mail from Caglar Gunyakti entitled: "Private Test Needed," Apr. 28, 2001, 1 page. cited by other . Email from Chris Drost-Hansen re press release: "AT&T Launches A2B Music Trial for Delivering Songs Over the Internet," Business Wire, Nov. 3, 1997. cited by other . Email from Edmond Kouka to Jean-Francois Boisson re TELENET TELEtraining platform--Bogdan Lutkiewicz, Poland, Gdansk, Mar. 4, 2001. cited by other . Enterprise Solutions Announces RSA Mail, RSA Security News, viewed at <http://rsasecurity.com/news/pr/940112-2.html.>, dated Jan. 12, 1994, pp. 1-2. cited by other . Epstein, J., "A Trusted X Window System Server for Trusted Mach," Usenix Association Proceedings, Mach Workshop, Oct. 4-5, 1990, Burlington, Vermont, pp. 141-155. cited by other . Erickson, John S., "A Copyright Management System for Networke Interactive Multimedia", Proceedings of the 1995 Dartmouth Institute for Advanced Graduate Studies, 1995. cited by other . Erickson, John S., "Rights Management Through Enhanced Attribution", Presented at INET 96 Proceedings, Jun. 1996. cited by other . ESPRIT Project 20517--Copysmart cited based multi-media IPR management on cost effective smart device, Summaries of Projects (FP III/IV)--Part I, European Information technology for Information Science, Oct. 1998. cited by other . ESPRIT Project 20676--IMPRIMATUR--Intellectual Multimedia Property Rights Model and Terminology for Universal Reference, IMPRIMATUR Consortium, Oct. 1998. cited by other . ESPRIT Project 22226--MUSE--Developing Standardized Digital media Management, Signaling and encryption Systems for the European Music Sector, International Federation of the Phonographic Industry, Oct. 1998. cited by other . ESPRIT Project 24378--MENHIR European Multimedia Network of High Quality Image Registration, Museums On Line, Feb. 1, 1997. cited by other . ESPRIT Project: 5469: Contract Amendment No. 2; Commission of the European Communities, Sep. 16, 1993. cited by other . Europe and The Global Information Society Recommendations to the European Council, Bamgemann Report, www.medicif.org web pages, Global Information Society, May 1994. cited by other . Everett, David B., "Smart Card Tutorial-Part 1," Sep. 1992. cited by other . Farmer, D., "The COPS Security Checker System," Jul. 10, 1992. cited by other . Federal Criteria for Information Technology Security vol. II, Version 1.0, National Institute of Standards and Technology and National Security Agency, Dec. 1992, 270 pages. cited by other . Feistel, H. "Cryptographic Coding for Data-Bank Privacy," IBM document RC 2827, Mar. 18, 1970. cited by other . Ferraiolo, D., et al., "Role-Based Access Control," Reprinted from the Proceedings of the 15th National Computer Security Conference, 1992, pp. 1-11. cited by other . Financial Transaction Card Originated Messages--Interchange Message Specifications--Part 2: Application and registration Procedures for Institution Identification Codes (IIC), ISO 8583-2, Jul. 1, 1998. cited by other . Financial Transaction Card Originated Messages--Interchange Message Specifications--Part 3: Maintenance Procedures for Codes, ISO 8583-3, Jul. 1, 1998. cited by other . Fine, T.,et al., "Assuring Distributed Trusted Mach," Secure Computing Corporation 1993, 13 pages. cited by other . Finin et al., "A Language and Protocol to Support Intelligent Agent Interoperability," Proceedings of the CE & CALS, Washington '92 Conference, Apr. 1992. cited by other . First CII Honeywell Bull International Symposium on Computer Security and Confidentialty, Conference Text, Jan. 26-28, 1981, 21 pages. cited by other . Forcht, K.A., Computer Security Management, Boyd & Fraser Publishing Company, 1994. cited by other . Forum on Risks to the Public in Computers and Related Systems, The Risks Digest, vol. 15; Issue 39, Jan. 21, 1994, pp. 1-12. cited by other . Forum on Technology-Based Intellectual Property Management--Electronic Commerce for Content, IMA INtellectual Property Proceedings, vol. 2, Jun. 1996. cited by other . Framework for National Information Infrastructure Services, Draft, U.S. Department of Commerce, Jul. 1994, 157 pages. cited by other . Framework for National Information Infrastructure Services, NIST, Jul. 1994, 12 Slides. cited by other . Franklin, M., et al., "An Overview of Secure Distribution Computing," Mar. 24, 1992, pp. 1-46. cited by other . FreeBSD System Manager's Manual "LDCONFIG", Oct. 3, 1993. cited by other . Fugini, M.G., et al., "Authorization and Access Control in the Office-Net System," Computer Security in the Age of Information, 1989, pp. 147-162. cited by other . Fugini, M.G., et al., "Security Management in Office Information Systems," Computer Security: A Global Challenge, 1984, pp. 487-498. cited by other . Galvin, J., et al., "Security Protocols for version 2 of the Simple Network Management Protocol (SNMPv2)," Network Working Group RFC 1446, Apr. 1993. cited by other . Galvin, J., et al., "SNMP Security Protocols," Network Working Group, Jul. 1992, pp. 1-26. cited by other . Gamble, Todd, "Implementing Execution Controls in Unix," Usenix Association, Proceedings of the Seventh Systems Administration Conference, Nov. 1-5, 1993, Monterey, California, pp. 237-242. cited by other . Garcia, D.L., "Science, Space and Technology, Hearing before Subcommittee on Technology, Environment, and Aviation," May 26, 1994, pp. 97-108. cited by other . Garfinkel, Simson, et al., Practical UNIX Security, O' Reilly & Associates, Inc., 1991. cited by other . Gasser, M., et al., "The Digital Distributed System Security Architecture," Reprint from the Proceedings of 1989 National Computer Security Conference, 1989, pp. 1-13. cited by other . Gemplus, MCOS: Multi Application Chip Operating System--Introduction, Gemplus Card International, 1990. cited by other . General Magic Picks RSA, RSA Security News, viewed at <http://rsasecurity.com/news/pr/940112-3.html.>, dated Jan. 12, 1994, pp. 1-2. cited by other . Gifford, D.K., "Cryptographic Sealing for Information Secrecy and Authentication," Communications of the ACM, vol. 25, No. 4, Apr. 1982, pp. 274-286. cited by other . Gifford, D.K., et al., "The Cirrus Banking Network," Communications of the ACM, vol. 28, No. 4, Aug. 1985, pp. 798-807. cited by other . Gilde, R., "DAT-Heads: Frequently Asked Questions," 1991, Release 3.1, Sep. 2, 1992. cited by other . Gircys, G.R., Understanding and Using COFF, O'Reilly & Associates, Inc., Nov. 1988. cited by other . Glatzer, H., "The Promise of LANs MIS Back in Control," Software News, Mar. 1985, pp. 51-58. cited by other . Gleick, J., "Dead as a Dollar," The New York Times Magazine, Jun. 16, 1996, Sect. 6, pp. 26-30, 35, 42, 50, 54. cited by other . Gligor, V.D., et al., "Object Migration and Authentication," IEEE Transactions on Software Engineering, vol. SE-5, No. 6, Nov. 1979, pp. 607-611. cited by other . Gong, Li, "A Secure Identity-Based Capability System," University of Cambridge Computer Laboratory, Jan. 1989, pp. 1-15. cited by other . Gong, Li, et al., "Signing, Sealing and Guarding Java Objects," Mobile Agents and Security, G. Vigna, editor, Springer-Verlag, 1998, vol. 1419 of LNCS, pp. 206-216. cited by other . Gosler, James, "Software Protection: Myth or Reality", Lecture Notes in Computer Science, Advances in Cryptology--Crypto '85 Proceedings, 1985. cited by other . Gosling, J., "Oak Intermediate Bytecodes," 1995, 5 pages. cited by other . Gozani et al., "GAFFES: The Design of a Globally Distributed File System," Report No. UCB/CSD 87/361; Computer Science Division (EECS), U.C. Berkley, Jun. 1997. cited by other . Greenwald et al., "The Distributed Compartment Model for resource management and Access Control," Technical report No. TR94-035, The University of Florida, Oct. 1994. cited by other . Greguras, F., "Softic Symposium '95, Copyright Clearances and Moral Rights," Dec. 11, 1995, 3 pages. cited by other . Griswold, Gary N., "A Method for Protecting Copyright on Networks", IMA Intellectual Property Proceedings, vol. 1, Issue 1, Jan. 1994. cited by other . Guide to the Secure Configuration and Administration of Microsoft Exchange 5.x.RTM., National Security Agency, Jun. 20, 2002, pp. 1-58. cited by other . Guillou, L.C., "Smart Cards and Conditional Access," Advances in Cryptography--Proceedings of EuroCrypt 84 (T. Beth et al, Ed., Springer-Verlag), 1985, pp. 480-490. cited by other . Haar, S.V., Document from the Internet: "PowerAgent Launches Commercial Service," Interactive Week, Aug. 4, 1997, 1 page. cited by other . Halfhill, Tom R., et al., "Agents on the Loose," Byte.com, Feb. 1994, pp. 1-2. cited by other . Halfhill, Tom R., et al., "Just Like Magic?, " Byte.com, Feb. 12, 1994, pp. 1-5. cited by other . Haller, N., "The S/KEY One-Time Password System," Network Working Group RFC 1760, Feb. 1995. cited by other . Handwritten note re: GVS and AJL, Mar. 2, 1994. cited by other . Hansen, S.E., et al., "Automated System Monitoring and Notification with Swatch," Proceedings of the 1993 LISA, Monterey, California, Nov. 1-5, 1993, pp. 101-108. cited by other . Hardjono, Thomas, "Record Encryption in Distributed Databases," Department of Computer Science, University of New South Wales, Jan. 1990, pp. 386-395. cited by other . Hardy, N., "The Keykos Architecture," Eighth Edition, Dec. 1990, pp. 1-8. cited by other . Harman, H., Modern Factor Analysis, Third Edition Revised, University of Chicago Press, Chicago and London, 1976. cited by other . Harn, Lein, et al., "A Software Authentication System for the Prevention of Computer Viruses," ACM, 1992, pp. 447-450. cited by other . Harris, J., et al., "Bento Specification," Apple Computer, Inc., Jul. 15, 1993, 106 pages. cited by other . Harty, K., et al., "Case Study: The VISA Transaction Processing System," May 30, 1988, pp. 1-23. cited by other . Hauser, Ralf C., et al., "LTTP Protection--A Pragmatic Approach to Licenseing", Institut fur Informatik, Universitat Zurich, Jan. 13, 1994. cited by other . Hauser, Ralf, "Control Information Distribution and Access," Dissertation Der Wirtschaftswissenschaftlichen Fakultat Der Universitat Zurich, May 31, 1995. cited by other . Hauser, Ralf, C., "Does Licensing Require New Access Control Techniques?," Institut fur Informatik, Universitat Zurich, Aug. 12, 1993, 9 pages. cited by other . Hawk, H.S., "RSA & General Magic," emall to Good Guys, Jan. 6, 1994, 1 page. cited by other . Hearst, M.A., "Interfaces for Searching the Web," Scientific American, Mar. 1997, pp. 68-72. cited by other . Herzberg, A. et al., "Public Protection of Software," ACM Transactions on Computer Systems, vol. 5, No. 4, Nov. 1987, pp. 371-393. cited by other . Herzberg, Amir, et al., "On Software Protection", Proceedings of the 4th Jerusalem Conference on Information Technology (JCIT), IEE Computer Society Press, Apr. 1984. cited by other . Hewlett-Packard Chooses RSA, RSA Sercurity News, viewed at <http://rsasecurity.com/news/pr/940112-5.html.>, dated Jan. 12, 1994, pp. 1-2. cited by other . Hickman, Kipp, E.B., SSL 2.0 Protocol Specificatoin. cited by other . Hilgraeve Ships Secure Version of HyperACCESS/5, RSA Security News, viewed at <http://rsasecurity.com/news/pr/940112-8.html.>, dated Jan. 12, 1994, pp. 1-2. cited by other . Hill, William et al., "Edit Wear and Read Wear," Computer Graphics and Interactive Media Research Group, ACM; May 3-7, 1992. cited by other . Hill, William et al., "History-Enriched Digital Objects," Computer Graphics and Interactive Media Research Group; Bell Communications Research, 1993. cited by other . History of Computer Security: Early Computer Security Papers, Part 1, National Institute of Standards and Technology, Sep. 4, 2002, viewed at <http://csrc.nist.gov/publications/history/index.html> pp. 1-27. cited by other . Hoffman, L.J., Modern Methods for Computer Security and Privacy, Prentice-Hall, Inc., 1977. cited by other . Hofmann, L.J., "Interfacing the NII to User Homes," Consumer Electronic Bus. Committee, NIST, Jul. 1994, 14 slides. cited by other . Hohl, F., "Time Limited Blackbox Security: Protecting Mobile Agents from Malicious Hosts," Lecture Notes in Computer Science, vol. 1419: Mobile Agents and Security, Springer-Verlag, 1998, G. Vigna Ed., pp. 90-111. cited by other . Holsinger, E., How Music and Computers Work, Ziff-Davis Press, 1994. cited by other . Holt, S., "Start-Up Promises User Confidentiality in Web Marketing Service," InfoWorld Electric News, updated Aug. 13, 1997, 2 pages. cited by other . Holzner, S., Heavy Metal OLE 2.0 Programming, IDG Books Worldwide, Inc., 1994. cited by other . Honeyman, P., "Digest of the First UNSENIX Workshop on Electronic Commerce (EC 95)," Jul. 1995. cited by other . Horster, P., Communications and Multimedia Security II, Chapman & Hall, 1996. cited by other . How Can I Put an Access Counter on My Home Page?, World Wide Web FAQ, 1996, 1 page. cited by other . Hsiao, D., et al., Computer Security, Academic Press, Inc., 1979. cited by other . Hutt, A.E., et al., Computer Security Handbook Second Edition, Macmillan Publishing Company, 1988, pp. 201-217. cited by other . IBM Cryptolope Technology-Executive Summary, IBM, viewed on Mar. 13, 2002 at <http://www-3.ibm.com/software/security/cryptolope.about.html> pp. 1-3. cited by other . Identification Cards-Financial Transaction Cards, ISO 7813, 1987. cited by other . Imprimatur News, imprimatur, Dec. 1998. cited by other . Intellectual Property and the National Information Infrastucture, a Preliminary Draft of the Report of the Working Group on Intellectual Property Rights, Green paper, Jul. 1994, 141 pages. cited by other . Interchange Message Specification for Debit and Credit Card Message Exchange Among Financial Institutions, American National Standard, Accredited Standards Committee X9-Financial Services Committee, ANSI X9.2-1988, American Bankers Association, May 16, 11. cited by other . International Infrastructure Standards Panel, "IISP Need #31-Containers or Secure Packaging," Electronic Publishing Research, Sep. 18, 1995, pp. 1-3. cited by other . International Infrastructure Standards Panel, "IISP Need #32-Authentication of Content," Electronic Publishing Research, Sep. 18, 1995, pp. 1-3. cited by other . International Infrastructure Standards Panel, "IISP Need #33-Control Enforcement," Electronic Publishing Research, Sep. 18, 1995, pp. 1-3. cited by other . International Infrastructure Standards Panel, "IISP Need #34-Billing and Payment," Electronic Publishing Research, Sep. 18, 1995, pp. 1-3. cited by other . International Infrastructure Standards Panel, "IISP Need #35-Reporting," Electronic Publishing Research, Sep. 18, 1995, pp. 1-3. cited by other . International Standard ISO8583, "Bank Card Originated Messages--Interchange Message Specifications--Contents for Financial Transactions," International Organization for Standardization, Aug. 15, 1987, pp. 1-33. cited by other . Internet Billing Server, Carnegie Mellon University, Prototype Scope Document, INI Tech Report, Oct. 14, 1993, pp. 1-29. cited by other . Introduction to Smart Cards v. 1.0, Gemplus Card International, Mar. 21, 1991. cited by other . Invoice? What's an Invoice?, Business week, Jun. 10, 1996, pp. 110-112. cited by other . Ioannidis, J. et al., "The Architecture and Implementation of Network-Layer Security Under Unix," Fourth USENIX Security Symposium Proceedings (Oct.), USENIX, Berkeley, Calif. 1993, 11 pages. cited by other . iOpener, Registered Trademark of National Semiconductor Corporation, Registration date Oct. 4, 1994, 1 page. cited by other . iOpener, U.S. Patent and Trademark Prosecution History for National Semiconductor Corporation, Registration date, Oct. 4, 1994, 27 pages, TULIP Final Report. cited by other . iPower's Data Security Approach, RSA Security News, viewed at <http://rsasecurity.com/news/pr/940112-10.html.>, dated Jan. 12, 1994. cited by other . Is Advertising Really Dead?, Wired 2.02, Part 2, 1994, 4 pages. cited by other . Jaeger, T, et al., "Support for the File System Security Requirements of Computational E-Mail Systems," Nov. 1994, ACM 0-89791-732-4/94/0011, 9 pages. cited by other . JAVASOFT, Frequently Asked Questions-Applet Security, Jun. 7, 1996, 7 pages. cited by other . Jiang, J.J. et al., "A Concept-based Approach to Retrieval from an Electronic Industrial Directory," International Journal of Electronic Commerce, vol. 1, No. 1 (Fall 1996) pp. 51-72. cited by other . Johnson, H.L., et al., "A Secure Distributed Capability Based System," ACM, 1985, pp. 392-402. cited by other . Johnson, R., "Info on Telescript," 1994 Software Agents List Archive, Dec. 6, 1994, pp. 1-4. cited by other . Jones, D., Document from the Internet: "Top Tech Stories, PowerAgent Introduces First Internet `Informediary` to Empower and Protect Consumers," (updated Aug. 13, 1997) 3 pages. cited by other . Kahn, D., The Codebreakers: The Story of Secret Writing, The Macmillan Company, 1967. cited by other . Kahn, R., et al., A Framework for Distributed Digital Object Services, Corporation for National Research Initiatives, May 13, 1995. cited by other . Kaliski, Jr., et al. "A Layman's Guide to a Subset of ASN.1, BER, and DER", RSA Laboratories Technical Note, 1991, Revised Nov. 1, 1993. cited by other . Kamens, J.I., "Retrofitting Network Security to Third-Party Applications-The SecureBase Experience,"Symposium Proceedings, Unix Security IV, Oct. 4-6, 1993 Santa Clara, California, pp. 41-57. cited by other . Kaner, Cem et al., Testing Computer Software, Second Edition, Van Nostrand Reinhold, 1988. cited by other . Kaplan, M., "IBM Cryptolopes, Super Distribution and Digital Rights Management," viewed at < <http://www.research.ibm.com/people/k/kaplan/cryptolope-docs/crypap.ht- ml>on Dec. 30, 1996, pp. 1-10. cited by other . Karger, P.A., et al., "A VMM Security Kernel for the VAX Architecture," CH2884-5/90/0000/0002, IEEE 1990, pp. 2-19. cited by other . Karger, P.A., et al., "Multics Security Evaluation: Vulnerability Analysis," HQ Electronic Systems Division, Hanscom AFB, Technical Report 19, Jun. 1974, 14 pages. cited by other . Kastenholz, F., "The Definitions of Managed Objects for the Security Protocols of the Point-to-Point Protocol," Network Working Group RFC 1472, Jun. 1993. cited by other . Katzan, Harry, Jr., Computer Data Security, Litton Educational Publishing Company 1973. cited by other . Keefe, T.F., et al., "Prototyping the SODA Security Model," Department of Computer Science, University of Minnesota, 1990, pp. 211-235. cited by other . Kelly, K., "E-Money," Whole earth Review, Summer 1993, pp. 40-59. cited by other . Kelman, Alistair, "Electronic Copyright Management: Possibilities and Problems", Scientists for Labor Presentation, Nov. 14, 1996. cited by other . Kelter, U., "Discretionary Access Controls in a High-Performance Object Management System," 1991 IEEE Computer Society Symposium on Research in Security and Privacy, May 20-22, 1991, Oakland, California, pp. 288-299. cited by other . Ketler, U., et al., "Type Level Access Controls for Distributed Structurally Object-Oriented Database Systems," Computer Security, ESCORICS 92, Second European Symposium on Research in Computer Security, Toulouse, France, Nov. 23-25, 1992, pp. 21-40. cited by other . Kent, S. T., "Protecting Externally Supplied Software in Small Computers," (MIT/LCS/TR-255) Sep. 1980, 254 pages. cited by other . Kent, S., et al., "Privacy Enhancement for Internet Electronic Mail: Part II--Certificate-Based Key Management," Network Working Group, Aug. 1989, pp. 1-22. cited by other . Kent, S.T., "U.S. Department of Defense Security Options for the Internet Protocol," Network Working Group RFC 1108, Nov. 1991. cited by other . Key Cryptolope Components, IBM, viewed on Mar. 13, 2002 at <http://www-3.ibm.com/software/security/cryptolope.about.html> pp. 1-2. cited by other . Key Management (retail)--Part I: Introduction to Key Management; Part II: Key Management Techniques for Symmetric Ciphers, ISO 11568-1 and -2, Dec. 1, 1994. cited by other . Key Management Using ANSI X9.17, Federal Information Processing Standards Publication 171, U.S. Department of Commerce, Apr. 1992. cited by other . KeyKOS Principles of Operation, Key Logic document KL002-04, 1985, Fourth Edition, Jan. 1987. cited by other . Kim, G.H., et al., "Experiences with Tripwire: Using Integrity Checkers for Intrusion Detection," Purdue Technical Report CSD-TR-94-012, Feb. 21, 1994. cited by other . Kim, G.H., et al., "The Design and Implementation of Tripwire: A File System Integrity Checker," Nov. 19, 1993. cited by other . Kim, L., et al., "Novell Cuisine," Proceedings of the ACM SIGUCCS User Services Conference XIX, Nov. 3-6, 1991, Seattle, Washington, pp. 183-184. cited by other . Kim, W., et al., "Features of the ORION Object-Oriented Database System," 1989, pp. 251-282. cited by other . Kim, W., et al., "Object-Oriented Concepts, Databases, and Applications," ACM Press, 1989. cited by other . Klemond, P., "Investigating Object Linking and Embedding, Part II: Adding Server Support," Microsoft Systems Journal, May/Jun. 1992, pp. 87-94. cited by other . Klemond, P., "Taking the Bull by the Horns: Investigating Object Linking and Embedding, Part I," Microsoft Systems Journal, Mar./Apr. 1992, pp. 19-38. cited by other . Kluepfel, H.M., "Securing a Global Village and its Resources: Baseline Security for Interconnected Signaling System #7 Telecommunications Networks," 1993, pp. 195-212. cited by other . Koenig, A., "Automatic Software Distribution," Usenix Association Software Tools Users Group, Summer Conference, Salt Lake City, Jun. 12-15, 1984, pp. 312-322. cited by other . Kohl, J.T., et al., "The Evolution of the Kerberos Authentication Service," Digital Equipment Corporation, 1991, pp. 1-15. cited by other . Kohl, J.T., et al., "The Kerberos Network Authentication Service (V 5), "Network Working Group Request for Comments RFC-1510, Sep. 1993, pp. 1-104. cited by other . Kohl, U., et al., "Safeguarding Digital Library Contents and Users," IBM research Division, D-Lib magazine, Sep. 1997. cited by other . Konheim, Alan, G., et al., "Cryptography: A Primer," John Wiley & Sons, Inc., 1981. cited by other . Krajewski, Jr., M., "Applicability of Smart Cards to Network User Authentication," Computing Systems, vol. 7, No. Winter 1994, pp. 75-89. cited by other . Kramer, M., "Strength in Numbers," PC Week, Jul. 22, 1986, pp. 57-58. cited by other . Kreutzer, A.N., "An On-Line System for Controlling and Monitoring Software Usage in a Microcomputer Laboratory," SIGUCCS Newsletter, vol. 18, No. 2, 1988, pp. 29-32. cited by other . Kristol, D.M., et al., "Anonymous Internet Mercentile Protocol," AT&T Bell Laboratories, Mar. 17, 1994, pp. 1-16. cited by other . Krol, E., The Whole Internet User's Guide and Catalog, 2nd. Ed., O'Reilly & Associates, Inc., 1992. cited by other . Kurak, C., et al., "A Cautionary Note On Image Downgrading," Proceedings of the 1992 Computer Security Applications Conference, San Antonio, TX, Dec. 1992, 7 pages. cited by other . Lagoze et al., "A Design for Inter-Operable Secure Object Stores (ISOS)," Cornell University, NCSA, CNRI, Nov. 1995. cited by other . Lagoze, C., "The Warwick Framework, A Container Architecture for Diverse Sets of Metadata," D-Lib Magazine, Jul./Aug. 1996, 7 pages. cited by other . Lagoze, Carl, "A Secure Repository Design for Digital Libraries", D-Lib Magazine, Dec. 1995. cited by other . LaLonde Wilf, R., et al., Inside Smalltalk: vol. 1, Prentice-Hall, Inc., 1990. cited by other . Lampson, B.W., "A Note on the Confinement Problem," Communications of the ACM, Oct. 1973, pp. 1-5. cited by other . Lampson, B.W., "Computer Security," Digital Equipment Corporation, 1991, pp. 1-54. cited by other . Lampson, Butler, et al., "Authentication in Distributed Systems: Theory and Practice," ACM Trans. Computer Systems, vol. 10, No. 4, Nov. 1992, 46 pages. cited by other . Landwehr, C.E, et al., "A Taxonomy of Computer Program Security Flaws," ACM Computer Surveys, vol. 26, No. 3, Sep. 1994, pp. 211-254. cited by other . Landwehr, C.E., "Formal Models for Computer Security," Computer Surveys, vol. 13, No. 3, Sep. 1981, pp. 247-278. cited by other . Langelaar, G.C. "Overview of Protection Methods in Existing TV and Storage Devices," SMS-TUD-609-1, Final Ver. 1,2, Feb. 26, 1996. cited by other . Lanza, M., "George Gilder's Fifth Article-Digital Darkhorse--Newspapers," Feb. 21, 1994, 2 pages. cited by other . Leary, P., "Are There Ciphers in Shakespeare?," 1995, pp. 1-18. cited by other . Lehman, B., "Intellectual Property and the National Information Infrastructure, A Preliminary Draft of the Report of the Working Group on Intellectual Property Rights," Jul. 1994, 4 introductory pages and pp. 1-141. cited by other . Leiss, E., "On Authorization Systems with Grantor-Controlled Propagation on Privileges," Compcon 83, Feb. 28-Mar. 3, 1983, San Francisco, California, pp. 499-502. cited by other . Lesk, M., "Digital Libraries Meet Electronic Commerce: On-Screen Intellectual Property," Dec. 15, 1998. cited by other . Levine, P.H., et al., "Network License Server," Apollo, Oct. 1987, pp. 1-19. cited by other . Levy, S., "E-Money, That's What I Want," Wired, Issue 2.12, Dec. 1994, 10 pages. cited by other . Lewontin, S., et al., "The DCE Web Project: Providing Authorization and Other Distributed Services to the World Wide Web," Feb. 22, 2002. cited by other . Lin, P., "The Encapsulated Security Services Interface (ESSI)," Computer Security (A-37), 1993, pp. 119-135. cited by other . Linn, J., "Privacy Enhancement for Internet Electronic Mail: Part I--Message Encipherment and Authentication Procedures," Network Working Group, Aug. 1989, pp. 1-30. cited by other . Lipson, S., "Little Black Box `Blocks` Illicit Software Copying," Stamford Advocate, Sep. 14, 1986, pp. E1-E2. cited by other . List of Articles, <www.chaum.com/articles/list-of-articles.htm>, as on Aug. 23, 2002, 4 pages. cited by other . Lockhart, Jr., H.W., OSF DCE Guide to Developing Distributed Applications, McGraw-Hill, Inc., 1994. cited by other . Lord et al., "Access Management in Multi-Administration Networks," IEE 2nd International Conference on Secure Communication Systems, 1986. cited by other . Low, S.H. et al., "Anonymous Credit Cards," AT&T Bell Laboratories, Proceedings of the 2nd ACM Conference on Computer and Communication Security, Fairfax, VA, Nov. 2-4, 1994, 10 pages. cited by other . Low, S.H. et al., "Document Marking and Identification Using both Line and Word Shifting," AT&T Bell Laboratories, Murray Hill, NJ, Jul. 29, 1994, 22 pages. cited by other . Lunt, Teresa, "Multilevel Security for Object-Oriented Database Systems," SRI International Computer Science Laboratory, 1990, pp. 199-209. cited by other . Lynch, C., "Searching the Internet," Scientific American, Mar. 1997, pp. 52-56. cited by other . Mach Books, viewed on Feb. 6, 2002 at http://www2.cs.cmu.edu/afs/cs/project/mach/public/www/doc/books.html., pp. 1-3. cited by other . Maclachlan, M., Document from the Internet: "PowerAgent Debuts Spam-Free Marketing," TechWire, Aug. 13, 1997, 3 pages. cited by other . Manager's Guide to MPE/IX Security, Hewlett-Packard Company, Apr. 1994. cited by other . Mann, C.C., "Homeland Insecurity," Sep. 2002. cited by other . Mathy, Laurent, "Features of the ACCOPI Multimedia Transport Service", Lecture Notes in Computer Science, No. 1045, Porc. of European Workshop IDMS' 96, Mar. 1996. cited by other . Maude, T., et al., "Hardware Protection Against Software Piracy," Communications of the ACM, vol. 27, No. 9, Sep. 1984, pp. 951-959. cited by other . McCloghrie, K., et al., "Definitions of Managed Objects for Administration of SNMP Parties," Network Working Group, Jul. 1992, pp. 1-17. cited by other . McCloghrie, K., et al., "Management Information Base for Network Management of TCP/IP-based Internets," Network Working Group, RFC 1156 (May 1990). cited by other . McCollum, C.J., et al., "Beyond the Pale of MAC and DAC-Defining New Forms of Access Control,", Unisys Defense Systems, 1990, pp. 190-200. cited by other . McGraw, G., et al., Java Security, John Wiley & Sons, Inc., 1997. cited by other . Medvinsky, G., et al., "NetCash: A Design for Practical Electronic Currency on the Internet," 1st Conference on Computer and Communication Security, Nov. 1993, pp. 102-106. cited by other . Merkle, Ralph C., "Protocols for Public Key Cryptosystems", IEEE, 1980. cited by other . Merkle, Ralph C., "Secure Communications Over Insecure Channels," Communications of the ACM, vol. 21, No. 4, Apr. 1978, pp. 294-296. cited by other . Meyer, C.H., et al., Cryptography: A New Dimension in Computer Data Security, John Wiley & Sons, Inc., 1982. cited by other . Microsoft Authenticode Technology, Microsoft Corporation, Oct. 1996. cited by other . Milbrandt, E., Document from the Internet: "Steganography Info and Archive," 1996, 2 pages. cited by other . Millen, J.K., et al., "Security for Object-Oriented Database Systems," Proceedings of the 1992 IEREE Computer Society Symposium on Research in Security and Privacy, May 4-6, 1992, Oakland, California, pp. 260-272. cited by other . Miller, S.P., et al., "Kerberos Authentication and Authorization System," Massachusetts Institute of Technology, Oct. 27, 1998, pp. 1-36. cited by other . Minear, S.E., "Providing Policy Control Over Operations in a Mach Based System," Secure Computing Corporation, Apr. 28, 1995, 15 pages. cited by other . Miscellaneous letter from Georges Van Slype at Bureau Van Dijik, Feb. 28, 1994. cited by other . Miscellaneous Letters from Georges Van Slype at Bureau Van Dijk, Apr. 19, 1994, Apr. 18, 1994, Apr. 11, 1994, Apr. 6, 1994.. cited by other . Miscellaneous Letters from Georges Van Slype at Bureau Van Dijk, Feb. 13, 1995 and Nov. 2, 1994. cited by other . Miscellaneous Letters from Georges Van Slype at Bureau Van Dijk, Feb. 9, 1994, Jan. 27, 1994, Jan. 19, 1994, Jan. 12, 1994, Dec. 22, 1993, Nov. 30, 1993, Nov. 22, 1993, Dec. 6, 1993, Nov. 16, 1993, Oct. 15, 1993, Oct. 7, 1993, Oct. 4, 1993, Sep. 20, 1993,. cited by other . Miscellaneous Letters from Georges Van Slype at Bureau Van Dijk, Mar. 30, 1994, Mar. 24, 1994, Feb. 10, 1994. cited by other . Miscellaneous Letters from Georges Van Slype at Bureau Van Dijk, Mar. 30, 1995. cited by other . Miscellaneous Letters from Georges Van Slype at Bureau Van Dijk, Sep. 12, 1994, May 11, 1994, May 10, 1994, May 6, 1994, May 4, 1994, Apr. 21, 1994, Apr. 20, 1994. cited by other . Moens, Jan, "Case of Application of the Generic Cited Model to the Citedisation of a Directory Database on CD-ROM, Ver. 2.0," ESPIRIT II, Project 5469, The Cited Consortium, Nov. 30, 1992. cited by other . Moens, Jan, "Report on the Users Requirements, Ver. 1.0," ESPIRIT II, Project 5469, The Cited Consortium, Nov. 27, 1991. cited by other . Moffett, Jonathan D., "Delegation of Authority Using Domain-Based Access Rules," thesis Imperial College of Science, Technology & Medicine, University of London, Jul. 1990. cited by other . Moffett, Jonathan D., "Specification of Management Policies and Discretionary Access Control," Department of Computer Science, University of York, Jun. 28, 1994, pp. 1-28. cited by other . Moffett, Jonathan D., et al., "An Introduction to Security Distributed Systems," Department of Computer Science, University of York, England, Aug. 1993, pp. 1-14. cited by other . Moffett, Jonathan D., et al., "Policy Hierarchies for Distributed Systems Management," IEEE JSAC Special Issue on Network Management, vol. 11, No. 9, Dec. 1993, pp. 1-4. cited by other . Moffett, Jonathan D., et al., "Specifying Discretionary Access Control Policy for Distributed Systems," Computer Communications, vol. 13, No. 9, Nov. 1990, pp. 1-17. cited by other . Moffett, Jonathan D., et al., "The Representation of Policies as System Objects," Proceedings of the Conference on Organizational Computer Systems (COCS '91), Atlanta, Georgia, Nov. 5-8, 1991, 16 pages. cited by other . Montini, G, et al., "Access Control Models and Office Structures," Computer Security: A Global Challenge, 1984, pp. 473-485. cited by other . Mori, R. et al., "Superdistribution: The Concept and the Architecture," The Transactions of the EIEICE, V, E73, No. 7, Tokyo, Japan, Jul. 1990, pp. 1133-1146. cited by other . Mossberg, W.S., "Personal Technology, Threats to Privacy On-Line Become More Worrisome," The Wall Street Journal, Oct. 24, 1996, 2 pages. cited by other . Motorola MC68030 Enhanced 32-bit Microprocessor User's Manual, 2nd Ed., Prentice-Hall, 1989. cited by other . MSDN-INF: LAN Manager 2.1 Server Autotuning (Part2), PSS ID No. 080078, Microsoft, Feb. 1993. cited by other . MSDN-Licence Service Application Programming Interface, API Specification v1.02, Micorsoft, Jan. 1993. cited by other . Muftic, Sead, Security Mechanisms for Computer Networks, Ellis Horwood Limited, 1989. cited by other . Mullender, S., Distributed Systems, ACM Press, 1989. cited by other . Multics, Home; viewed on Nov. 12, 2001 at <http://www.multicians.org> pp. 1-3. cited by other . Multimedia Mixed Object Envelopes Supporting a Graduated Fee Scheme Via Encryption, IBM Technical Disclosure Bulletin, vol. 37, No. 3, Mar. 1, 1994, pp. 413-417. cited by other . Multimedia System Services Ver. 1.0, Hewlett-Packard, IBM, & SunSoft, 1993. cited by other . National Semiconductor and EPR Partner for Information Metering/Data Security Cards, Press Release, (Mar. 4, 1994), 4 pages. cited by other . Negroponte, N., "Electronic Word of Mouth," Wired, Oct. 1996, p. 218. cited by other . Negroponte, N., "Some Thoughts on Likely and Expected Communications Scenarios: A Rebuttal," Telecommunications, Jan. 1993, pp. 41-42. cited by other . Neuman B.C., et al. "Kerberos: An Authentication Service for Computer Networks," IEEE Communications magazine, Sep. 1994. cited by other . Neuman, B.C., "Proxy-Based Authorization and Accounting for Distributed Systems," Information Sciences Institute, University of Southern California, 1993, pp. 283-291. cited by other . Neumann, P.G. et al., "A Provably Secure Operating System: The System, Its Applications, and Proofs," Computer Science Laboratory Report CSL-116, Second Edition, SRI International, Jun. 1980, 381 pages. cited by other . News from The Document Company Xerox, Xerox Announces Software Kit for Creating `Working Documents` with Dataglyphs, Nov. 6, 1995, 13 pages. cited by other . Nguyen, Thanh et al., "Guidelines for Validation of a Cited System," Cited 5469, SA-21-40-003, Jul. 4, 1994. cited by other . NSA Korean War 1950-1953 Commemoration, History Papers, National Security Agency, http://www.nsa.gov/korea/papers.htm, pp. 1-2. cited by other . O'Connor, MaryAnn, "New Distribution Option for Electronic Publishers," Information Access Co., Mar. 1994, pp. 1-6. cited by other . OLE 2.0 Draft Content: Object Linking & embedding, Microsoft, Jun. 5, 1991. cited by other . Olivier, M.S. et al., "A Taxonomy for Secure Object-oriented Databases," ACM Transactions on Database Systems, vol. 19, No. 1, Mar. 1994, pp. 3-46. cited by other . Olivier, M.S. et al., "DISCO: A Discretionary Security Model for Object-oriented Databases," in GG Gable and WJ Caelli, Eds., IT Security: The Need for International Cooperation, pp. 345-357, Elsevier Science Publishers B.V. (North Holland), 1992, 14 pagee. cited by other . Olivier, M.S. et al., "Secure Object-oriented Databases," Ph.D. Thesis, Rand Afrikaans University, Johannesburg, Dec. 1991, pp. i to xiv and 1-183. cited by other . Olivier, M.S., "A Multilevel Secure Federated Database," Database Security, VIII (A-60), 1994, pp. 183-198. cited by other . Olivier, M.S., et al., "Building a Secure Database using Self-protecting Objects," Computers & Security, vol. 11, No. 3, 259-271, 1992. cited by other . Olson, M.S., et al., "Concurrent Access Licensing," vol. 6, No. 9, Unix Review, 1988, pp. 67-74. cited by other . OMG Security Working Group, "OMG White Paper on Security," OMG Security Working Group, Apr. 1994, pp. 1-24. cited by other . OOPSLA 1993: Addendum to the Proceedings, "Security for Object-Oriented Systems," Sep. 26-Oct. 1, 1993, pp. 77-78. cited by other . Open System Environment Architectural Framework for National Information Infrastructure Services and Standards, in Support of National Class Distributed Systems, Distributed System Engineering Program Sponsor Group, Draft 1.0, Aug. 5, 1994, 34 pages. cited by other . Open Systems Interconnection: Security Architecture, ISO 7498/1, 1988. cited by other . Open Systems Interconnection: Security Architecture, ISO 7498/2, 1988. cited by other . OpenDoc vs. OLE 2.0: Superior by Design, IBM, Jan. 1994, pp. 1-4. cited by other . Orfali, R., et al., The Essential Distributed Objects Survival Guide, John Wiley & Sons, Inc., 1996. cited by other . Organick, E.I., The Multics System: An Examination of Its Structure, MIT Press, 1972. cited by other . OSF DCE Administration Guide-Core Components, Open Software Foundation, PTR Prentice Hall, 1993. cited by other . Paepcke, Andreas, "Summary of Stanford's Digital Library Testbed and Status," Stanford University, D-Lib Magazine, Jul. 1996. cited by other . Park, J.S., AS/400 Security in a Client/Server Environment, John Wiley & Sons, Inc., 1995. cited by other . Payment Systems; Strategic Choices for the Future, Hitachi Research Institute; Institute of Advanced Business Systems, Hitachi, Ltd., 1993. cited by other . Pelton, J.N., "Why Nicholas Negroponte is Wrong About the Future of Telecommunications," Telecommunications, Jan. 1993, pp. 35-40. cited by other . Perlman, Bill, "A Working Anti-Taping System for Cable Pay-Per-View," IEEE Trans. On Comsumer Electronics, vol. 35, No. 3, Aug. 1989. cited by other . Personal Identification Number (PIN) management and security--Part I: Basic Principles and Requirements for online PIN Handling in ATM and POS Systems; & -2 Approved Algorithm(s) for PIN Encipherment, ISO 9564-1 & -2, (Apr. 15, 2002 & Dec. 15, 1991. cited by other . Pethia et al., "Guidelines for the Secure Operation of the Internet," Network Working Group, RFC 1281, Nov. 1991. cited by other . Picciotto, J., et al., "Extended Labeling Policies for Enhanced Application Support," Computers & Security, vol. 13, No. 7, 1994, pp. 587-599. cited by other . Pietreck, M., Windows Internals: The Implementation of the Windows Operation Environment, Addison-Wesley, 1993. cited by other . Pijenborg, Mari F.J., "Auteursrecht En De Digitale Bibliotheek," 195 Open, Jan. 1995. cited by other . Pijnenborg, Mari F.J., "Cited Final Report," Elsevier Science B.V., Apr. 1994. cited by other . PKCS #1:RSA Encryption Standard, RSA Laboratories Technical Note, Ver. 1.5, revised Nov. 1, 1993. cited by other . PKCS #10: Certification Request Syntax Standard, An RSA Laboratories Technical Note, Ver. 1.0, Nov. 1, 1993. cited by other . PKCS #11: Crytographic Token Interface Standard, An RSA Laboratories Technical Note, Ver. 2.0, Apr. 15, 1997. cited by other . PKCS #12 v 1.0: Personal Information Exchange Syntax, RSA Laboratories, Jun. 24, 1999. cited by other . PKCS #13: Elliptic Curve Crytography Standard, RSA Security, Jan. 12, 1998. cited by other . PKCS #15 v 1.0: Cryptographic Token Information Format Standard, RSA Laboratories, Apr. 23, 1999. cited by other . PKCS #3: Duffie-Hellman Key-Agreement Standard, RSA Laboratories Technical Note, Ver. 1.4, revised Nov. 1, 1993. cited by other . PKCS #5: Password-Based Encryption Standard, An RSA Laboratories Technical Note, Ver. 1.5, 1991-1993, Revised Nov. 1, 1993. cited by other . PKCS #6: Extended-Certificate Syntax Standard, RSA Laboratories Technical Note, Ver. 1.5, revised Nov. 1, 1993. cited by other . PKCS #8: Private-Key Information Syntax Standard, An RSA Laboratories Technical Note, Ver. 1.2, 1991-1993, Revised Nov. 1, 1993. cited by other . PKCS #9: Selected Attribute Types, RSA Laboratories Technical Note, Ver. 1.1, revised Nov. 1, 1993. cited by other . Polk, T.W., "Approximating Clark-Wilson "Access Triples" with Basic UNIX Controls," Symposium Proceedings, Unix Security IV, Oct. 4-6, 1993, Santa Clara, California, pp. 145-154. cited by other . Popek, Gerald, J., et al., "Encryption and Secure Computer Networks," Computing Surveys, vol. 11, No. 4, Dec. 1979, pp. 331-356. cited by other . Portland Software's Ziplock, Internet Information, Copyright Portland Software 1995-1996, 11 pages. cited by other . Premenos Announces Templar 2.0--Next Generation Software for Secure Internet EDI, Jan. 17, 1996, 1 page. cited by other . Press, Jim, "Secure Transfer of Identity and Privilege Attributes in an Open Systems Environment," Computers & Security, vol. 10, No. 2, 1991, pp. 117-127. cited by other . Privacy and the NII: Safeguarding Telecommunications--Related Personal Information, U.S. Dept. of Commerce, Oct. 1995. cited by other . "Proceedings: Technological Strategies for Protecting Intellectual Property in the Networked Mulimedia Environment," Coalition for Networked Information, Interactive Multimedia Association, John F. Kennedy School of Government, 285 pp. 1994. cited by other . Proper Use of Consumer Information on the Internet, White Paper, Power Agent Inc., Menlo Park, CA, Jun. 1997, 9 pages. cited by other . Protecting Electronically Published Properties, Increasing Publishing Profits, Electronic Publishing Resources Inc., Chevy Chase, Maryland, 1991, 17 pages. cited by other . Purdy, G.B., et al., "A Software Protection Scheme," Proceedings of the 1982 Symposium on Security and Privacy, Apr. 26-28, 1982, Oakland California, pp. 99-103. cited by other . R01--Solving Critical Electronics Publishing Problems, Personal Library Software, 1987 or 1988, 4 pages. cited by other . R01, Personal Library Software, 1987 or 1988. cited by other . Rankine, G., "Thomas--A Complete Single-Chip RSA Device," Advances in Cryptography, Proceedings of Crypto 86, (A.M. Odiyzko Ed., Springer-Verlag) 1987, pp. 480-487. cited by other . Rashid, R.F., CMU Computer Science: A 25th Anniversary Commemorative, Addison-Wesley Publishing Company, 1991. cited by other . Reali, Patti, "Copy Protection: The answer to pay per view's Prayers?," TVRO Dealer, Dec. 1994. cited by other . Request for Technology: Multimedia System Services, Ver. 2.0, Interactive Multimedia Association Compatibility Project, Nov. 9, 1992. cited by other . Request for Technology: Multimedia System Services, Draft, Ver. 1.1, Interactive Multimedia Association Compatibility Project, Oct. 16, 1992. cited by other . Requirements for the Software License Management System, System Management Work Group, Rev. 3, Unix International, Jul. 23, 1992. cited by other . Rescorla, E., et al., "The Secure HyperText Transfer Protocol," Enterprise Integration Technologies, Jun. 1994, pp. 1-23. cited by other . Resnick, P., "Filtering Information on the Internet," Scientific American, Mar. 1997, pp. 62-64. cited by other . Resnick, P., et al., "Recommender Systems," Communications of the ACM, vol. 40, No. 3, Mar. 1997, pp. 56-58. cited by other . Richardson, D.W., Electronic Money: Evolution of an Electronic Funds-Transfer System, The MIT Press, 1970. cited by other . Rindfrey J., "Security in the World Wide Web," Fraunhofer Institute for Computer Graphics, Dec. 1996. cited by other . Rivest, Ronald L., "The MD5 Message-Digest Algorithm," Network Working Group, Apr. 1992, pp. 1-21. cited by other . Rivest, Ronald L., et al., "A Method for Obtaining Digital Signatures ans Public-Key Cryptosystems," Communications of the ACM, vol. 21, No. 2, Feb. 1978, pp. 120-126b. cited by other . Rivest, Ronald L., et al., "SDSI--A Simple Distributed Security Infrastructure", MIT and Microsoft Corporation, Apr. 30, 1996. cited by other . Roberts, R., et al., Compute!'s Computer Security, Compute! Publications, Inc., 1989. cited by other . Robinson et al., "Encoding Header Field for Internet Messages," Network Working Group RPC 1154, Apr. 1990. cited by other . Rose et al., "Structure and Identification of management Information for TCP/IP-based Internets," Network Working Group RFC 1155, May 1990. cited by other . Rose, L., Cyberspace and the Legal Matrix: Laws or Confusion?, 1991, pp. 43-52. cited by other . Rosenberry, W., et al., "Distributing Applications Across DCE and Windows NT," 1993. cited by other . Rosenberry, W., et al., Understanding DCE, O'Reilly & Associates, Inc., 1992. cited by other . Rosenthal, Doug, "EINet: A secure, Open Network for Electronic Commerce", IEEE, 1994. cited by other . Rosenthal, S., "Interactive Network: Viewers Get Involved," New Media, Dec. 1992, pp. 30-31. cited by other . Rosenthal, S., "Interactive TV: The Gold Rush is on," New Media, Dec. 1992, pp. 27-29. cited by other . Rosenthal, S., "Mega Channels," New Media, Sep. 1993, pp. 36-46. cited by other . Ross, P.E., "Cops versus robbers in cyberspace," Forbes, Sep. 9, 1996. cited by other . Rothstein, E., "Technology Connections, Making The Internet Come To You Through `Push` Technology," N.Y. Times, Jan. 20, 1997, p. D5. cited by other . RSA Enters Wireless Arena, RSA Security News, viewed at <http://rsasecurity.com/news/pr/940112-6.html.>, dated Jan. 12, 1994, pp. 1-2. cited by other . RSA Security; News; <http://rsasecurity.com/news/pr/9401.html.>, dated Jan. 12, 1994, pp. 1-2. cited by other . RSA's Developer's Suite for Secure Electronic transactions (SET), S/PAY, RSA Data Security, Inc., 1997. cited by other . Rubin et al., "Formal Methods for he Analysis of Authentication Protocols CITI Technical Report 93-7," Center for Information Technology Integration, Nov. 8, 1993. cited by other . Rubin et al., "Long Running Jobs in an Authenticated Environment," CITI Technical Report 93-1, Center for Information Technology Integration, Mar. 1993. cited by other . Rubin, A.D., "Trusted Distribution of Software Over the Internet," Bellcore, 1995, pp. 1-9. cited by other . Rucker, et al., "Personalized Navigation for the Web," Communications of the ACM, pp. 73-75, Mar. 1997. cited by other . Rushby, J.M., "Design and Verification of Secure Systems," ACM, 1981, pp. 12-21. cited by other . Russell, D., et al., Computer Security Basics, O' Reilly & Associates, Inc., 1991. cited by other . Russell, S., "Paradigms for Verification of Authorization at Source of Electronic Documents in an Integrated Environment," Computers & Security, vol. 12, No. 6, 1993, pp. 542-549. cited by other . Russell, S., "Planning for the EDI of Tomorrow Using Electronic Document Authorization," Computer Security (A-37), 1993, pp. 243-251. cited by other . Rutkowski, K., "PowerAgent Introduces First Internet `Informediary` to Empower and Protect Consumers," Tech Talk News Story, Aug. 4, 1997, 1 page. cited by other . Sager, I., "Bits & Bytes," Business Week, Sep. 23, 1996, p. 142E. cited by other . Sander, T. et al., "Protecting Mobile Agents Against Malicious Hosts," Mobile Agents and Security: Lecture Notes in Computer Science, Springer-Verlag, G. Vigna, Ed., vol. 1419, Nov. 11, 1997, 16 pages. cited by other . Sander, T. et al., "Towards Mobile Cryptography," IEEE Proceedings of Security and Privacy, May 1998, 10 pages. cited by other . Sandhu, Ravi S., "The Typed Access Matrix Model," Proceedings of the IEEE Symposium on Security and Privacy, Oakland California, May 4-6, 1992, pp. 122-136. cited by other . Sandhu, Ravi S., et al., "A Secure Kernelized Architecture for Multilevel Object-Oriented Databases," Proceedings of the IEEE Computer Security Foundations Workshop IV, Jun. 1991, Franconia, NH, pp. 139-152. cited by other . Sandhu, Ravi S., et al., "Data and Database Security and Controls," Handbook of Information Security Management, Auerbach Publishers, 1993, pp. 1-37. cited by other . Sandhu, Ravi, S., et al., "Implementation Considerations for the Typed Access Matrix Model in a Distributed Environment," Proceedings of the 15th NIST-SCSC National Computer Security Conference, Baltimore, Maryland, Oct. 1992, pp. 221-235. cited by other . Saydjari, O.S., et al., "Lock Trek: Navigating Unchartered Space," National Computer security Center, 1989, pp. 167-175. cited by other . Schaumueller-Bichl, I. et al., "A Method of Software Protection Based on the Use of Smart Cards and Cryptographic Techniques," Advances in Cryptography, Proceedings of Eurocrypt 84, Apr. 9-11, 1984, 9 pages. cited by other . Scherwin, Rich, Pay-per-view Web content Feb. 1997; PC Computing, vol. 10, No. 2, p. 288(1) Dialog copy, 1 page. cited by other . Schill, A.B., et al., "DC++: Distributed Object-Oriented System Support on top of OSF DCE," 1993. cited by other . Schill, A.B., et al., "DCE-The OSF Distributed Computing Environment Client Server Model and Beyond," Oct. 1993. cited by other . Schlossstein, S., "America: The G7's Comeback Kid, International Economy," Jun./Jul. 1993, 5 pages. cited by other . Schneier, B., "Description of New Variable-Length Key, 64-bit block cipher (Blowfish)," Fast Software Encryption, Cambridge Security Workshop Proceedings, 1994. cited by other . Schneier, Bruce, Applied Cryptography: Protocols, Algorithms, and Source Code in C, John Wiley & Sons, Inc., 1994. cited by other . Schulze, Dr. J., "Case of Application of the Generic Cited Model to the CiteDisation in the Software Distribution Process," ESPIRIT II, Project, Jan. 12, 1993. cited by other . Schurmann, J., "Pattern Classification, a Unified View of Statistical and Neural Approaches," John Wiley & Sons, Inc., 1996. cited by other . Schutzer, D., "A Need for a Common Infrastructure: Digital Libraries and Electronic Commerce," Citibank, D-Lib Magazine, Apr. 1996. cited by other . Secure Cryptographic Devices (retail)--Part I: Concepts, Requirements and Evaluation Methods, ISO 13491-1, Jun. 15, 1998. cited by other . Security Requirements for Cryptographic Modules, U.S. Department of Commerce (NIST), Jan. 11, 1994, pp. 1-53. cited by other . Serving the Community: A Public Interest Vision of the National Information Infrastructure, Computer Professionals for Social Responsibility, Executive Summary, Oct. 1993, 6 introductory pages, pp. 1-20 and Bibliography (pp. 21-23). cited by other . Shaffer, S.L., et al., Network Security, Academic Press, Inc., 1994. cited by other . Shear, Victor, "Solutions for CD-Rom Pricing and Data Security Problems," CD ROM Yearbook 1988-1989 (Microsoft Press 1988 or 1989) pp. 530-533. cited by other . Shirley, J., "Guide to Writing DCE Applications," 1st Ed. 1992. cited by other . Shirley, J., et al., "Guide to Writing DCE Applications," 2nd Ed. 1994. cited by other . Short, K.L., Microprocessors and Programmed Logic, Prentice-Hall, Inc., 1981. cited by other . Sibert, Olin, et al. "Digibox: A Self-Protecting Container for Information Commerce," Proceedings of the First Usenix Workshop on Electronic Commerce, New York, NY, Jul. 1995, pp. 1-13. cited by other . Sibert, Olin, et al., "Securing the Content, Not the Wire, for Information Commerce," InterTrust Technologies Corporation, 1996, 12 pages. cited by other . Sigsaly Secure Digital Voice Communications in World War II, National Security Agency, http://www.nsa.gov/wwii/papers/sigsaly.htm, Oct. 13, 2000, pp. 1-2. cited by other . Siuda, K., "Security Services in Telecommunications Networks," Seminar: Mapping New Applications Onto New Technologies, edited by B. Plattner and P. Gunzburger; Zurich, Mar. 8-10, 1988, pp. 45-52. cited by other . Smart Card 1993 Conference Proceedings, "Day 1: Communications and Marketing Systems & Market Overview," Lowndes Exhibition Organisers, Ltd., 1993, pp. 1-79. cited by other . Smith, Mary Grace, et al., "A New Set of Rules for Information Commerce: Rights-Protection Technologies and Personalized-Information Commerce Will Affect All Knowledge Workers", Communications Week, Nov. 6, 1995. cited by other . Smith, S. et al., "Signed Vector Timestamps: A Secure Protocol for Partial Order Time," CMU-93-116, School of Computer Science Carnegie Mellon University, Pittsburgh, Pennsylvania, Oct. 1991; version of Feb. 1993, 15 pages. cited by other . Solomon, Daniel, J., "Processing Multilevel Secure Objects," Proceedings of the 1981 Symposium on Security and Privacy, Apr. 27-29, 1981, Oakland, California, pp. 56-61. cited by other . Specification for Financial Message Exchange Between Card Acceptor and Acquirer, X9.15, American National Standard, American Banker's Association, 1990. cited by other . SSL 2.0 Protocol Specification, viewed at http://home.netscape.com/eng/security/SSL.2html, Jan. 23, 2003. cited by other . St. Johns, M., "Draft Revised IP Security Option", Network Working Group, RFC, 1038, Jan. 1998. cited by other . Stallings, W., Cryptography and Network Security: Principles and Practice, Prentice-Hall, Inc., 1999. cited by other . Starfish State of the Art Financial Services for the in Habitants of Isolated Areas--Project Profile, Information Society technologies, time schedule, Jan. 21, 2000-Jun. 30, 2002. cited by other . Stefik, M., "Chapter 7, Classification," Introduction to Knowledge Systems, Morgan Kaufmann Publishers, Inc., 1995, pp. 543-607. cited by other . Stefik, M., "Letting Loose the Light: Igniting Commerce in Electronic Publication," Internet Dreams: Archetypes, Myths, and Metaphors. Massachusetts Institute of Technology, 1996, pp. 219-253. cited by other . Stefik, M., "Letting Loose the Light: Igniting Commerce in Electronic Publication," Xerox PARC, Palo Alto, CA, 1994-1995, 35 pages. cited by other . Stefik, M., "Trusted Systems," Scientific American, Mar. 1997, pp. 78-81. cited by other . Stephenson, T., "The Info Infrastructure Initiative: Data Super Highways and You," Advanced Imaging, May 1993, pp. 73-74. cited by other . Stepney et. al., "Formal specification of an Access Control System," Software-Practice and Experience, vol. 17, No. 9, 1987. cited by other . Sterling, B., "Literary Freeware: Not for Commercial Use," Computers, Freedom and Private Conference IV, Chicago, IL, Mar. 26, 1994, pp. 51-55. cited by other . Strack, Hermann, "Extended Access Control in Unix System V-ACLs and Context," Usenix Association, Proceedings of the Unix Security II Workshop, Aug. 27-28, 1990, Portland, Oregon, pp. 87-101. cited by other . Struif, B., "The Use of Chipcards for Electronic Signatures and Encryption," Proceedings for the 1989 Conference on VSLI and Computer Peripherals, IEEE Computer Society Press, 1989, pp. 4-155-4-158. cited by other . Stubblebine, S.G., "Security Services for Multimedia Conferencing," Proceedings of the 16th National Computer Security Conference, Baltimore, Maryland, Sep. 20-23, 1993, pp. 1-5. cited by other . Talisman: Tracing Authors' Rights by Labeling Image Services and Monitoring Access Network, ACTS, Swiss Participation in European Research Programs, Sep. 1, 1995, Aug. 31, 1998. cited by other . Tanenbaum, A.S., et al., "Amoeba System," Communications of the ACM, vol. 33, No. 12, Dec. 1990. cited by other . Tanenbaum, A.S., et al., "Distributed Operating Systems," Computing Surveys, vol. 17, No. 4, Dec. 1985, pp. 419-470. cited by other . Tanenbaum, A.S., et al., "Experiences with the Amoeba Distributed Operating System," Vrije Universiteit and Centrum voor Wiskunde en Informatica, 1990. cited by other . Tanenbaum, A.S., et al., "The Amoeba Distributed Operating System," 1990. cited by other . Tanenbaum, A.S., et al., "The Amoeba Distributed Operating System-A Status Report," 1991. cited by other . Tanenbaum, A.S., Modern Operating Systems, Prentice-Hall, Inc. 1992. cited by other . Tanenbaum, A.S., Operating Systems: Design and Implementation, Prentice-Hall, Inc. 1987. cited by other . Technical Description: Pay-Per-View Copy Protection, Macrovision, Jun. 1994. cited by other . Technical Rationale Behind CSC-STD-003-85: Computer Security Requirements, http://www.radium.ncsc.mil/tpep/library/rainbow/CSC-STD-004-85.html, Jun. 25, 1985, pp. 1-40. cited by other . Technical Strategies for Protecting Intellectual Property in the Networked Multimedia Environment, IMA Intellectual Property Proceedings, vol. I, Issue 1, Jan. 1994. cited by other . Telenet TELEtraining Platform (on NETworks)--Project Profile, Information Society Technologies, time schedule, Mar. 6, 2000-Mar. 30, 2000. cited by other . The Benefits of ROI for database Protection and Usage Based Billing, Personal Library Software, 1987 or 1988, 5 pages. cited by other . The First UsenixWorkshop on Electronic Commerce Proceedings, New York, New York, Jul. 11-12, 1995, Usenix Association. cited by other . The Future of Cited: A Feasibility Study, ESPIRIT II, Project 5469, Cited Project Review, Apr. 15, 1994. cited by other . The New Alexandria No. 1, Alexandria Institute, Jul.-Aug. 1986, 12 pages. cited by other . The PowerTV White Paper, powertv.com website, Oct. 11, 1996. cited by other . The Risks Digest, "Forum on Risks to the Public in Computers and Related Systems," vol. 15; Issue 39, Jan. 21, 1994, pp. 1-12. cited by other . The Risks Digest, "Forum on Risks to the Public in Computers and Related Systems," vol. 15; Issue 47, Feb. 9, 1994, pp. 1-12. cited by other . The Standard Business: Time for Change, European Commission DG111 Espirit Project 5th Consensus Forum, Nov. 3-4, 1998. cited by other . Think C: Object-Oriented Programming Manual, Symantec Corporation, 1989. cited by other . Think Pascal: The Fastest Way to Finished Software, Symantec Corporation, 1990, pp. 93-123. cited by other . Thomas, R.K., et al., "Implementing the Message Filter Object-Oriented Security Model without Trusted Subjects," Proceedings of the IFIP Workshop on Database Security, Aug. 19-21, 1992, Vancouver, Canada, 21 pages. cited by other . Thompson, Victoria P., et al., "A Concept for Certification of an Army MLS Management Information System" , Proceedings of the 16th National Computer Security Conference, Sep. 20-23, 1993. cited by other . Thuraisingham, M.B., "Mandatory Security in Object-Oriented Database Systems," OOPSLA '89 Proceedings, Oct. 1-6, 1989, pp. 203-210. cited by other . Thuraisingham, M.B., et al., "Parallel Processing and Trusted Database Management Systems," ACM, 1993. cited by other . Ting, T.C., et al., "Requirements, Capabilities and Functionalities of User Role Based Security for an Object-Oriented Design Model," Database Security, V: Staus and Prospectus, 1992, pp. 275-297. cited by other . Toohey, J., Using OLE 2.X in Application Development, Que Corporation, 1994. cited by other . Townsend, J.E., "NIST on Internet Security," Mar. 22, 1994, pp. 1-15. cited by other . Transformer Rules Strategy for Software Distribution Mechanism-Support Products, IBM Technical Disclosure Bulletin, vol. 37, No. 48, Apr. 1994, pp. 523-525. cited by other . Trusted Unix Working Group (TRUSIX) Rationale for Selecting Access Control List Features for the UNIX (R) System, National Computer Security Center, Aug. 18, 1989. cited by other . Tuck, Bill, "Electronic Copyright Management Systems: Final Report of a Scoping Study for Elib," Jul. 1996. cited by other . Tulip Final Report, ISBN 0-444-82540-1, 1991, revised Sep. 18, 1996. cited by other . Tygar, J.D. et al., "Dyad: A System for Using Physically Secure Coprocessors," School of Computer Science, Carnegie Mellon University, Pittsburgh, PA, May 1991, 121-152 pages. cited by other . Tygar, J.D. et al., "Strongbox: A System for Self Securing Programs," CMU Computer Science: 25th Anniversary Commemorative, R. Rashid (ed.) Addison-Wesley, 1991, pp. 163-197. cited by other . Tygar, J.D., et al., "Cryptography: It's Not Just for Electronic Mail Anymore," CMU-CS-93-107, School of Computer Science Carnegie Mellon University, Pittsburgh, PA, Mar. 1, 1993, pp. 1-21. cited by other . Uhler, Stephen A., "PhoneStation, Moving the Telephone onto the Virtual Destop," 1993 Winter USENIX, San Diego, California, Jan. 25-29, 1993, pp. 131-140. cited by other . UniverCD: The InterActive, Online Library of Product Information From Cisco Systems, Cisco Systems 1993. cited by other . Unix System v. Release 3.2. Programmer's Guide. vol. II, At&T, Prentice Hall, 1989. cited by other . van Gilluwe, F., The Undocumented PC: A Programmer's Guide to I/O, Cpus, and Fixed Memory Areas, Addison-Wesley Publishing Company, 1994. cited by other . Van Slype, Georges et al, "The Future of Cited; a Feasibility Study," ESPRIT II, Project 5469, The Cited Consortium, Nov. 15, 1993. cited by other . Van Slype, Georges et al., "Natural Language Version of the Generic Cited Model, Ver. 4.2, vol. I: Presentation of the Generic Model," ESPRIT II, Project 5469, The Cited Consortium, May 8, 1995. cited by other . Van Slype, Georges et al., "The Future of Cited: A Feasibility Study, Ver. 1.0, vol. II: Full Report," ESPRIT II, Project 5469, The Cited Consortium, Feb. 28, 1994. cited by other . Van Slype, Georges, "Draft Cited Interchange Formats, Ver. 1.0", ESPRIT II, Project 5469, the Cited Consortium, Jan. 28, 1994. cited by other . Van Slype, Georges, "Natural Language Version of the Generic Cited Model, Ver. 2.1, vol. II ECMS (Electric Copyright Management System) Design for Computer Based Applications" ESPIRIT II, Project 5469, The Cited Consortium, May 8, 1995. cited by other . Van Slype, Georges, "PL4 RACE/ACCOPI Workshop on Conditional Access and Copyright Protection," ESPRIT II, Project 5469, Presentation of the Cited, Nov. 9, 1994. cited by other . Van Slype, Georges, "PL4 RACE/ACCOPI Workshop on Conditional Access and Copyright Protection," ESPRIT II, Project 5469, The Cited Consortium, Nov. 9, 1994. cited by other . Van Slype, Georges, "The Cited Approach, Ver. 4.0," ESPRIT II, Project 5469, The Cited Consortium, Apr. 20, 1994. cited by other . Van Slype, Georges, "The Future of Cited: A Feasibility Study, Ver. 1.0, vol. I: Summary Report and Recommendations," ESPRIT II, Project 5469, The Cited Consortium, Feb. 28, 1994. cited by other . Van Slype, Georges, "The Future of Cited: A Feasibility Study, Ver. 1.1, vol. I: Summary Report and Recommendations," ESPRIT II, Project 5469, The Cited Consortium, Mar. 28, 1994. cited by other . Van Slype, Georges, "The Future of Cited: A Feasibility Study, Ver. 1.1, vol. III: Draft Cited Interchange Formats," ESPRIT II, Project 5469, The Cited Consortium, Feb. 28, 1994. cited by other . Vittal, J., "Active Message Processing: Messages as Messengers," Bolt, Beranek and Newman, Inc., 1980, pp. 175-195. cited by other . Voight, J., "Beyond the Banner," Wired, Dec. 1996, 6 pages. cited by other . Voydock, V.L., et al., "Security Mechanisms in High-Level Network Protocols," Computing Surveys, vol. 15, No. 2, Jun. 1983, pp. 135-171. cited by other . Wagner, N. "Fingerprinting," Drexel University, IEEE Symp. On Info. and Privacy, Apr. 1993. cited by other . Walker, Bruce, J., et al., Computer Security and Protection Structures, Dowden, Hutchinson, & Ross, Inc., 1977. cited by other . Walker, S., "Notes from RSA Data Security Conference," Jan. 18, 1994, pp. 1-3. cited by other . Ware, W., Chairman RAND Corporation "Panel: The InterTrust Commerce Architecture," 1997, 6 pages. cited by other . Wayner, P., "Agents Away," Byte.com, May 1994, pp. 1-9. cited by other . Wayner, Peter, Digital Copyright Protection, Academic Press, 1997. cited by other . Weadon, P.D., "The SIGSALY Story," Dec. 10, 2002. cited by other . Weber, Robert, "Digital Rights Management Technologies," A Report to the International Federation of Reproduction Rights Organisations, Northeast Consulting Resources, Inc., Oct. 1995, 49 pages. cited by other . Weber, Robert, "Metering Technologies for Digital Intellectual Property," A Report to the International Federation of Reproduction Rights Organisations (Boston, MA), International Federation of Reproduction on Rights Organisations, Northeast Consulting Reesources, Inc., Oct. 1994, 29 pages. cited by other . Weingart, S.H., "Physical Security for the ABYSS System," (IBM Thomas J. Watson Research Center, Yorktown Heights, NY), 1987, pp. 52-58. cited by other . Weitzner, D.J., "A Statement on EFF's Open Platform Campaign as of Nov.," 1993, 3 pages. cited by other . Wells, Rob, Odyssey of Plastic Purchase; 20-Second Round Trip, Associated Press, Dec. 1993. cited by other . WEPIN Store, Stenography (Hidden Writing), Common Law, 1995, 1 page. cited by other . What is Firefly?, <www.ffly.com,> Firefly Network, Inc., Firefly revision: 41.4, Copyright 1995, 1996, 1 page. cited by other . What the Experts Are Reporting on PowerAgent, PowerAgent Press Releases, Aug. 13, 1997, 6 pages. cited by other . What the Experts are Reporting on PowerAgent, PowerAgent Press Releases, Aug. 4, 1997, 5 pages. cited by other . White Paper: The Future of Electronic Commerce, A Supplement to Midrange Systems, Premenos Corp. Document from Internet: <firstname.lastname@example.com>, Aug. 1995, 4 pages. cited by other . White, J.E., "Telescript Technology: The Foundation for the Electronic Marketplace," General Magic, 1994. cited by other . White, James E., "Telescript: The Foundation for the Electronic Marketplace", Ver. 5.0, General Magic, Inc., Nov. 30, 1993, pp. 1-13. cited by other . White, S.R., et al., "ABYSS: A Trusted Architecture for Software Protection," (IBM Thomas J. Watson Research Center, Yorktown Heights, NY), 1987, pp. 38-50. cited by other . White, Steve R., et al., "ABYSS: An Architecture for Software Protection", IEEE Transactions on Software Engineering, vol. 16, No. 6, Jun. 1990. cited by other . Willett, S., "Metered PCs: Is Your System Watching You?, Wave Systems Beta Tests New Technology," IDG Communications, Inc., May 2, 1994, pp. 1-6. cited by other . Williams, S., "An MSJ Interview with Microsoft's Chief Architect of OLE, Tony Williams," Microsoft Systems Journal, Oct. 1993, pp. 55-66. cited by other . Williams, Tony, "Microsoft Object Strategy", Microsoft PowerPoint Presentation, 1990. cited by other . Winslet et al., "Formal Query Languages for Secure Relational Databases," ACM Transactions on Database Systems, vol. 19, No. 4, Dec. 1994. cited by other . Wobber, Edward, et al., "Authentication in the Taos Operating System", Digital Equipment Corporation, Dec. 10, 1993, 68 pages. cited by other . Wong, R., et al., "The SIDOS System: A Secure Distributed Operating System Prototype," Odyssey Research Associates, Oct. 1989, pp. 172-183. cited by other . Woo, Thomas, Y.C., et al., "A Framework for Distributed Authorization," Proceedings of the 1st Conference Computer and Communication Security Nov. 1993, pp. 112-118. cited by other . Wood, P.H., et al., UNIX System Security, Pipeline Associates, Inc., 1985. cited by other . Working with Windows Objects, Microsoft Press, OLE 2 Programmer's Reference; vol. 1, 1994. cited by other . XIWT Cross Industry Working Team, Jul. 1994, 5 pages. cited by other . Yee, B., "Using Secure Coprocessors," CMU-CS-94-149, School of Computer Science, Carnegie Mellon University, Pittsburgh, PA, 1994, 94 pages. cited by other . Yee, B., et al., "Secure Coprocessors in Electronic Commerce Applications," Proceedings of the First Usenix Workshop on Electornic Commerce, New York, New York, Jul. 1995, 16 pages. cited by other . Yellin, F., Document from the Internet: "Low Level Security in Java," Sun Microsystems, 1996, 8 pages. cited by other . Young, W.D., "Verifiable Computer Security and Hardware: Issues," Technical Report, Computational Logic Inc., Sep. 1991, 43 pages. cited by other . Zeleznick, M.P., "Security Design in Distributed Computing Applications," Department of Computer Science, University of Utah, Dec. 1993, 16 pages. cited by other . Zelnick, Nate, "Keeping Business Safe on the Internet," PC Magazine, Apr. 25, 1995, pp. 1-2. cited by other . Zurko, M.E., "Panels at the 1997 IEEE Symposium on Security and Privacy," Oakland, CA, May 1997, 12 pages. cited by other . Office Action mailed Jun. 23, 1998, in U.S. Appl. No. 08/699,711. cited by other . Final Office Action mailed Apr. 8, 1999, in U.S. Appl. No. 08/699,711. cited by other . Office Action mailed Nov. 12, 1999, in U.S. Appl. No. 09/221,479. cited by other . Office Action mailed Mar. 25, 2005, in U.S. Appl. No. 09/632,944. cited by other . Abadi, M., et al., "A Calculus for Access Control in Distributed Systems", Digital Equipment Corporation, Feb. 28, 1991, revised Aug. 28, 1991. cited by other . About the Digital Notary Service, Surety Technologies, 1994-5, 6 pages. cited by other . Abrams, Marshall D, "Renewed Understanding of Access Control Policies", Proceedings of the 16th Computing Natioal Security Conference, 1993. cited by other . Access Control and Copyright Protection for Images Security Technology for Graphics and Communication Systems--RACE M1005: ACCOPI, webpage, Security Projects at Fraunhofer 1GD, 2002. cited by other . Achievements Archive, www.imprimatur.net/ web pages, no date. cited by other . Anderson, R., "Why Cryptosystems Fail," University Computer Laboratory, Cambridge, Massachusetts, (undated), pp. 1-34. cited by other . Antonelli et al, "Access Control in a Workstation-Based Distributed Computing Environment," CITI Technical Report 90-2, Jul. 17, 1990. cited by other . Argent Information, Q&A Sheet, Document from the Internet: <http://www.digital-watermark.com/>, Copyright 1995, The DICE Company, (last modified Jun. 16, 1996), 7 pages. cited by other . Arms, W.Y., "Key Concepts in the Architecture of the Digital Library," D-Lib Magazine, Jul. 1995. cited by other . Arneke, D. et al., "AT&T Encryption System Protects Information Services," (News Release), Jan. 9, 1995, 1 page. cited by other . Atkinson, R., "Security Architecture for the Internet Protocol," Network Working Group RFC 1825, Aug. 1995. cited by other . Aucsmith, D., et al., "Common Data Security Architecture," Intel Architecture lab, Presentation Material, Jan. 22, 1996, pp. 1-16. cited by other . Aucsmith, David, "Tamper Resistant Software: An Implementation", IAL. cited by other . Authentification dans les environnements de traitement distributes, Information Systems Audit and Control Association-Montreal Chapter, viewed on Mar. 25, 2002 at <http://www.apvcsi-montreal.ca/en/publications/contact133.html> pp. 1-15. cited by other. Primary Examiner: Barron, Jr.; Gilberto Assistant Examiner: Wyszynski; Aubrey H Attorney, Agent or Firm: Finnegan, Henderson, Farabow, Garrett & Dunner, L.L.P. Parent Case Text CROSS-REFERENCE TO RELATED APPLICATIONS This is a division of application Ser. No. 09/632,944, filed Aug. 4, 2000, pending, which is a continuation of application Ser. No. 09/221,479, filed Dec. 28, 1998, now U.S. Pat. No. 6,185,683, which is a continuation of application Ser. No. 08/699,711, filed Aug. 12, 1996, now abandoned, which is a continuation-in-part of application Ser. No. 08/388,107, filed Feb. 13, 1995, now abandoned, all of which are incorporated herein by reference. This application is related to concurrently filed commonly assigned copending application Ser. No. 08/699,712 of Ginter et al. entitled "Trusted Infrastructure Support Systems, Methods and Techniques, Commerce Process Control and Automation, Distributed Computing, and Rights Management" (hereafter referred to as "Shear et al" to avoid confusion with the "Ginter et al" reference in the paragraph above). The entire disclosure (including the drawings) of this related Shear et al. patent application is incorporated by reference into this specification as if expressly set forth in this specification. Claims What is claimed is: 1. A system for governing access to or other use of electronic data, the system comprising: a first apparatus including: user controls, a communications port, a processor, and a memory containing: a first rule, a first secure container containing a file, the file including at least one of audio data, video data, image data, or text data, the first secure container having an associated second rule, the second rule governing, at least in part, access to or other use of at least a portion of the file; and at least one digital signature, the digital signature including data for use in validating the file; at least one of hardware or software capable of receiving and opening secure containers, at least some of said secure containers including the capacity to contain at least one governed item, and having at least one rule associated therewith; a protected processing environment containing information, the protected processing environment at least in part protecting at least some of the contained information from tampering by a user of said first apparatus, said protected processing environment including at least one of hardware or software capable of applying said first rule and said second rule in combination to at least in part govern at least one aspect of access to or use of said file; and at least one of hardware and software capable of at least one of: transmission of secure containers to other apparatuses, or the receipt of secure containers from other apparatuses. 2. A system as in claim 1, said first apparatus including at least one of signature affixation hardware and signature affixation software. 3. A system as in claim 1, said digital signature being stored in a secure container. 4. A system as in claim 3, said secure container including at least one cryptographic key. 5. A system as in claim 4, said secure container in which said digital signature is stored being a second secure container, different from said first secure container. 6. A system as in claim 5, wherein said memory further contains a third rule, the third rule at least in part governing at least one aspect of access to or use of said digital signature. 7. A system as in claim 3, said memory storing at least one rule at least in part governing at least one aspect of access to or use of said digital signature. 8. A system for governing access to or other use of electronic data, the system comprising: a first apparatus including: user controls, a communications port, a processor, and a memory containing: a first rule, a first secure container containing a file, the file including at least one of audio data, video data, image data, or text data, the first secure container having an associated second rule, the second rule governing, at least in part, access to or other use of at least a portion of the file; and at least one first electronic seal; at least one of hardware or software capable of receiving and opening secure containers, at least some of said secure containers including the capacity to contain at least one governed item, and having at least one rule associated therewith; a protected processing environment containing information, the protected processing environment at least in part protecting at least some of the contained information from tampering by a user of said first apparatus, said protected processing environment including at least one of hardware or software capable of applying said first rule and said second rule in combination to at least in part govern at least one aspect of access to or use of said file; and at least one of hardware or software capable of at least one of: transmission of secure containers to other apparatuses, or the receipt of secure containers from other apparatuses. 9. A system as in claim 8, said electronic seal including a digital representation of a handwritten signature. 10. A system as in claim 8, said electronic seal including receipt information. 11. A system as in claim 8, said electronic seal including usage information. 12. A system as in claim 8, said electronic seal including at least one image designed to allow for visual recognition of said seal. 13. A system as in claim 8, said seal including encoded information. 14. A system as in claim 13, said encoded information being stenographically encoded in said seal. 15. A system as in claim 8, said electronic seal including a digital signature. 16. A system as in claim 8, said electronic seal including validation information. 17. A system as in claim 8, said electronic seal including information regarding at least one transmission of said first secure container. 18. A system as in claim 17, said transmission information including information regarding the transmitter of said first secure container. 19. A system as in claim 8, said electronic seal including at least one electronic seal rule. 20. A system as in claim 19, said at least one electronic seal rule governing, at least in part, at least one aspect of access to or use of said first secure container contents. 21. A system as in claim 8, said electronic seal including a representation of at least one aspect of said first secure container contents. 22. A system as in claim 21, said representation including a hash of at least a portion of said first secure container contents. 23. A system as in claim 22, said hash comprising a hash of at least a portion of said file after normalization of said portion. 24. A system as in claim 22, said electronic seal further including a time value. 25. A system as in claim 22, said electronic seal further including a certificate value obtained from a digital certificate. 26. A system as in claim 8, said electronic seal including encrypted information. 27. A system as in claim 26, said encrypted information being encrypted, at least in part, using a key from a public/private key pair. 28. A system as in claim 27, said encryption key belonging to at least one individual or entity responsible at least in part for at least one transmission of said file. 29. A system as in claim 8, said electronic seal further including at least one error correction code. 30. A system as in claim 29, said error correction code being derived from at least a portion of said first secure container contents. 31. A system as in claim 8, said electronic seal being stored in a secure container. 32. A system as in claim 31, said secure container in which said electronic seal is stored being a second secure container, different from said first secure container. 33. A system as in claim 32, said memory storing at least one rule at least in part governing at least one aspect of access to or use of said electronic seal. 34. A system as in claim 8, said file including at least one second electronic seal. 35. A system as in claim 34, said at least one second electronic seal being stored in said first secure container. 36. A system for governing access to or other use of electronic data, the system comprising: a first apparatus including: user controls, a communications port, a processor, and a memory containing: a first rule, a first secure container containing a file, the file including at least one of audio data, video data, image data, or text data, the first secure container having associated a second rule, the second rule governing, at least in part, access to or other use of at least a portion of the file; and at least one electronic fingerprint; at least one of hardware or software capable of receiving and opening secure containers, at least some of said secure containers including the capacity to contain at least one governed item, and having at least one rule associated therewith; a protected processing environment containing information, the protected processing environment at least in part protecting at least some of the contained information from tampering by a user of said first apparatus, said protected processing environment including at least one of hardware or software capable of applying said first rule and said second rule in combination to at least in part govern at least one aspect of access to or use of said file; and at least one of hardware or software capable of at least one of: transmission of secure containers to other apparatuses, or the receipt of secure containers from other apparatuses. 37. A system as in claim 36, the at least one electronic fingerprint being stored in a secure container. 38. A system as in claim 37, said secure container in which said electronic fingerprint is stored being a second secure container, different from said first secure container. Description FIELD OF THE INVENTION(S) These inventions relate to secure and trusted delivery of digital information. More specifically, these inventions pertain to techniques, methods and systems for providing reliable, trusted, verifiable delivery, handling, creation and/or execution of digital items such as documents, executable code (e.g., Java applets), and/or any other information capable of being represented in digital form. The present invention also relates to commercial and other electronic activities involving a trusted third party electronic go-between (such as a computer controlled process) to audit, validate, and/or direct electronic transactions, executions and/or delivery and/or to archive information representing and/or at least in part comprising securely communicated digital information. BACKGROUND AND SUMMARY OF THE INVENTIONS There is a great need for convenient, cost effective techniques to securely handle and deliver documents and other items. Existing methods such as express and personal couriers, registered mail, facsimile and electronic mail fulfill some of these needs but these techniques each have their problems and are deficient in important ways. Trusted Personal Couriers Perhaps the ultimate in secure document handling is the personal trusted courier. Many of us have seen spy films showing a trusted courier delivering documents containing state secrets. In such scenarios, the document sender places the document or other item into a lockable attache case. The sender seals and locks the case with a key or combination that only he and the recipient have. The courier handcuffs the case to his or her wrist, boards an airplane and flies to the required destination--all the while carefully guarding the attache case and its contents. Upon arriving at the destination, the courier personally delivers the case to the intended recipient. The recipient unlocks the case and retrieves its contents, all the while having a high degree of assurance that the contents have been kept secret. The confidentiality, security and reliability provided by a personal trusted document courier has never really been matched by any other form of document delivery. Even though we sometimes might want or need the services of a personal trusted document courier, it is likely that practical reasons (such as cost and availability) require us to use less trusted forms of delivery for even our most important and confidential documents or other items. Moreover, even the trusted courier technique does not provide a reliable means of later providing how and when the information was used by the recipient and/or subsequently handled by others to whom the recipient may pass the information and what information was actually sent. This approach also cannot provide the degree of interactivity between the sender and the recipient possible in a world of near instantaneous communications, including seamlessly supporting processes related to rights management, and document creation and dissemination. As discussed below, existing alternatives to the trusted courier are more practical and less expensive, and some offer advantages such as instantaneous communications and interactivity--but all suffer from various disadvantages. Express Courier Services Federal Express and other express courier services provide rapid (for example, overnight) delivery services at a relatively high degree of trustedness. In the typical case, the sender places the items to be delivered into a special, tear resistant sealed envelope, and fills out an "air bill" that lists the sender's name, address and telephone number, and the intended recipient's name, address and telephone number. The "air bill" also lists options such as, for example, the type of delivery service required (i.e., delivery next business morning, next business afternoon, or second business day), whether the sender requires Federal Express to obtain the recipient's signature, the payment method, and a unique "tracking number" used to uniquely identify the package. Once the package is complete and ready to send, the sender may provide it to Federal Express through a number of different methods: the sender may take the package to a Federal Express office and personally hand it to a clerk, the sender may drop the completed envelope in any one of many pervasive Federal Express drop off boxes, and someone will come and collect the envelopes from the boxes sometime before the end of the business day and deliver them to a Federal Express office, or the sender can call Federal Express and arrange for a delivery person to come and pick up the package. Federal Express maintains a fleet of aircraft that shuttle most packages to a central sorting and routing facility for subsequent dispatch to various destinations across the United States and the world. A fleet of delivery trucks deliver the packages from local airports to each recipient. At the sender's option, a delivery person may obtain a recipient's signature at the time she delivers the package--providing documentation that may later be used to prove the package was in fact received by the intended recipient or someone at his or her home or office. Federal Express uses automated computer tracking and package handling equipment to route individual packages to their destinations. Delivery information is put into the tracking computer to allow customers and service people to automatically retrieve information about when and to whom particular packages were actually delivered, or where the package happens to be at the moment. Federal Express and other similar document delivery services have been highly successful because they cost-effectively ensure reliable delivery of original documents and other items. Nevertheless, they do have some significant disadvantages and limitations. For example: They are much more expensive than other delivery mechanisms at least in part because of the high labor, transportation, and infrastructure (many offices, planes, etc.) costs involved. They do not provide the very high degree of confidentiality desired for certain confidential business or other documents. They generally can only reliably verify that the package was delivered to the intended recipient (or his or her home or place of business)--and not that the intended recipient opened the package or read or saw or used the document. The one (or two) day delay they introduce may be too great for time sensitive or time pressing items. These problems are exacerbated when several individuals and/or organizations in different geographical locations are all parties to a transaction--a complex, multiparty contract, for example--and all must sign or otherwise process and/or execute one or more related documents. Registered Mail A relatively more secure delivery technique is registered mail. Registered mail correspondents can have a high degree of confidence that their packages will arrive at their required destinations--but may not like the time delays and additional expense associated with this special form of mail handling. To use registered mail, the sender places her document or other items into a sealed envelope or package and takes her package to the nearest Post Office. For security, the Post Office may prohibit the use of resealable tape and mailing labels, and instead require the package to be sealed with paper tape and the address to be written directly on the package. These safeguards help to ensure that any attempts to tamper with the package or its contents will be detected. The Post Office securely transports the registered mail package to the recipient, requiring each postal employee who accepts custody of the package along its journey to sign and time stamp a custody record. The postal carrier at the recipient's end personally delivers the package to the recipient--who also has to sign for it and may be asked to produce proof of identification. The custody record establishes a chain of custody, listing every person who has had custody of the package on its journey from sender to recipient. As discussed above, registered mail is relatively secure and confidential but delivery takes a long time and is very labor and infrastructure intensive. Facsimile Facsimile is an electronic-based technology that provides virtually instantaneous document delivery. A facsimile machine typically includes a document scanner, a document printer, and electronic circuits that convert document images to and from a form in which they can be sent over a telephone line. Facsimile requires each of the sender and the intended recipient to have a facsimile machine. The sender typically places the document to be sent into a document feeder attached to a facsimile machine. The sender then typically keys in the telephone number of the intended recipient's facsimile machine and presses a "start" button. The sender's facsimile machine automatically dials and establishes contact with the recipient's facsimile machine. Once a good connection is established, the sender's facsimile machine begins to optically scan the document one page at a time and convert it into digital information bits. The sender's facsimile machine converts the digital bits into a form that can be transmitted over a telephone line, and sends the bits to the intended recipient's facsimile machine. The sender's facsimile machine may also send as part of the document, a "header" on the top of each page stating the sender's identity, the page number of the transmission, and the transmission time. However, these headers can be changed at will by the sender and therefore cannot be trusted. Since the recipient's facsimile machine receives the transmitted information at the same time the sender's facsimile machine is sending it, delivery is virtually instantaneous. However, sending a document to an unattended facsimile machine in an insecure location may result in the document falling into the wrong hands. Another common scenario is that the facsimile machine operator, through human error, dials the wrong telephone number and ends up delivering a confidential document to the wrong person (for example, the local grocery store down the street, or in some unfortunate cases, the opposing side of a negotiation, legal proceeding or other pitched battle). Thousands of faxes are lost every day in a "black hole"--never arriving at their desired destinations but possibly arriving at completely different destinations instead. Some secure facsimile machines such as those used by government and military organizations, or by companies needing a significantly higher level of security provide an extra security/authentication step to ensure that the intended recipient is physically present at the receiving facsimile machine before the sender's machine will transmit the document. In addition, it is possible to use encryption to prevent the facsimile transmitted information from being understood by electronic eavesdroppers. However, such specially equipped facsimile machines tend to be very expensive and are not generally available for common commercial facsimile traffic. Moreover, facsimile machines typically can send and receive documents only--and therefore are not very versatile. They do not, for example, handle digital items such as audio, video, multimedia, and executables, yet these are increasingly part and parcel of communications for commerce and other purposes. Thus, despite its many advantages, facsimile transmissions do not provide the very high degree of trustedness and confidence required by extremely confidential documents, nor do they provide the degree of flexibility required by modern digital communications. As with Express Courier Services and Registered Mail, faxing can only indicate that the package was delivered to the intended recipient (or his or her home or place of business)--and not that the intended recipient opened the package or read or saw or used the document. Electronic Mail More and more, people are using electronic mail to send documents, messages, and/or other digital items. The "Internet explosion" has connected millions of new users to the Internet. Whereas Internet electronic mail was previously restricted primarily to the academic world, most corporations and computer-savvy individuals can now correspond regularly over the Internet. Currently, Internet electronic mail provides great advantages in terms of timeliness (nearly instantaneous delivery) and flexibility (any type of digital information can be sent), but suffers from an inherent lack of security and trustedness. Internet messages must typically pass through a number of different computers to get from sender to recipient, regardless of whether these computers are located within a single company on an "Intranet" for example, or on Internet attached computers belonging to a multitude of organizations. Unfortunately, any one of those computers can potentially intercept the message and/or keep a copy of it. Moreover, even though some of these systems have limited "return receipt" capabilities, the message carrying the receipt suffers from the same security and reliability problems as the original message. Cryptography (a special mathematical-based technique for keeping messages secret and authenticating messages) is now beginning to be used to prevent eavesdroppers from reading intercepted messages, but the widespread use of such cryptography techniques alone will not solve electronic mail's inherent lack of trustedness. These electronic mail messages, documents and other items (e.g., executable computer programs or program fragments) that might have been sent with them as "attachments," remain vulnerable to tampering and other unauthorized operations and uses once decrypted and while delivery may be reported, actual use can not be demonstrated. Some people have tried to develop "privacy enhanced" electronic mail, but prior systems have only provided limited improvements in reliability, efficiency and/or security. The Present Inventions Solve These and Other Problems As discussed above, a wide variety of techniques are currently being used to provide secure, trusted confidential delivery of documents and other items. Unfortunately, none of these previously existing mechanisms provide truly trusted, virtually instantaneous delivery on a cost-effective, convenient basis and none provide rights management and auditing through persistent, secure, digital information protection. In contrast, the present inventions provide the trustedness, confidentiality and security of a personal trusted courier on a virtually instantaneous and highly cost-effective basis. They provide techniques, systems and methods that can bring to any form of electronic communications (including, but not limited to Internet and internal company electronic mail) an extremely high degree of trustedness, confidence and security approaching or exceeding that provided by a trusted personal courier. They also provide a wide variety of benefits that flow from rights management and secure chain of handling and control. The present inventions preferred embodiment make use of a digital Virtual Distribution Environment (VDE) as a major portion of its operating foundation, providing unique, powerful capabilities instrumental to the development of secure, distributed transaction-based electronic commerce and digital content handling, distribution, processing, and usage management. This Virtual Distribution Environment technology can flexibly enable a wide variety of new business models and business practices while also supporting existing business models and practices. The Virtual Distribution Environment provides comprehensive overall systems, and wide arrays of methods, techniques, structures and arrangements, that enable secure, efficient electronic commerce and rights management on the Internet and other information superhighways and on internal corporate networks such as "Intranets". The present inventions use (and in some cases, build upon and enhances) this fundamental Virtual Distribution Environment technology to provide still additional flexibility, capabilities, features and advantages. The present invention, in its preferred embodiment, is intended to be used in combination a broad array of the features described in Ginter, et al, including any combination of the following: A. VDE chain of handling and control, B. security trusted internodal communication, C. secure database, D. authentication, E. cryptographic, F. fingerprinting, G. other VDE security and communication techniques, H. rights operating system, I. object design and secure container techniques, J. container control structures, K. ARPML rights and process control language, L. electronic negotiation, M. secure hardware, and N. smart agent (smart object) techniques. For example, parties using the Virtual Distribution Environment can participate in commerce and other transactions in accordance with a persistent set of rules they electronically define. Such techniques, systems and arrangements bring about an unparalleled degree of security, reliability, efficiency and flexibility to electronic commerce, electronic rights management and other important business models. The present inventions make use of these persistent electronic rules to provide secure, automated, cost-effective electronic control for electronic document and other digital item handling and/or delivery, and for the electronic formation and negotiation of legal contracts and other documents. By way of non-exhaustive summary, these present inventions provide a highly secure and trusted item delivery and agreement execution services providing the following features and functions: Trustedness and security approaching or exceeding that of a personal trusted courier. Instant or nearly instant delivery. Optional delayed delivery ("store and forward"). Broadcasting to multiple parties. Highly cost effective. Trusted validation of item contents and delivery. Value Added Delivery and other features selectable by the sender and/or recipient. Provides electronic transmission trusted auditing and validating. Allows people to communicate quickly, securely, and confidentially. Communications can later be proved through reliable evidence of the communications transaction--providing non-repudiatable, certain, admissible proof that a particular communications transaction occurred. Provides non-repudiation of use and may record specific forms of use such as viewing, editing, extracting, copying, redistributing (including to what one or more parties), and/or saving. Supports persistent rights and rules based document workflow management at recipient sites. System may operate on the Internet, on internal organization and/or corporate networks ("Intranets" irrespective of whether they use or offer Internet services internally), private data networks, and/or using any other form of electronic communications. System may operate in non-networked and/or intermittently networked environments. Legal contract execution can be performed in real time, with or without face to face or ear-to-ear personal interactions (such as audiovisual teleconferencing, automated electronic negotiations, or any combination of such interactions) for any number of distributed individuals and/or organizations using any mixture of interactions. The items delivered and/or processed may be any "object" in digital format, including, but not limited to, objects containing or representing data types such as text, images, video, linear motion pictures in digital format, sound recordings and other audio information, computer software, smart agents, multimedia, and/or objects any combination of two or more data types contained within or representing a single compound object. Content (executables for example) delivered with proof of delivery and/or execution or other use. Secure electronic containers can be delivered. The containers can maintain control, audit, receipt and other information and protection securely and persistently in association with one or more items. Trustedness provides non-repudiation for legal and other transactions. Can handle and send any digital information (for example, analog or digital information representing text, graphics, movies, animation, images, video, digital linear motion pictures, sound and sound recordings, still images, software computer programs or program fragments, executables, data, and including multiple, independent pieces of text; sound clips, software for interpreting and presenting other elements of content, and anything else that is electronically representable). Provides automatic electronic mechanisms that associate transactions automatically with other transactions. System can automatically insert or embed a variety of visible or invisible "signatures" such as images of handwritten signatures, seals, and electronic "fingerprints" indicating who has "touched" (used or other interacted with in any monitorable manner) the item. System can affix visible seals on printed items such as documents for use both in encoding receipt and other receipt and/or usage related information and for establishing a visible presence and impact regarding the authenticity, and ease of checking the authenticity, of the item. Seals can indicate who originated, sent, received, previously received and redistributed, electronicallyview, and/or printed and/or otherwise used the item. Seals can encode digital signatures and validation information providing time, location, sender and/or other information and/or providing means for item authentication and integrity check. Scanning and decoding of item seals can provide authenticity/integrity check of entire item(s) or part of an item (e.g., based on number of words, format, layout, image--picture and/or text--composition, etc.). Seals can be used to automatically associate electronic control sets for use in further item handling. System can hide additional information within the item using "steganography" for later retrieval and analysis. Steganography can be used to encode electronic fingerprints and/or other information into an item to prevent deletion. Multiple steganographic storage of the same fingerprint information may be employed reflecting "more" public and "less" public modes so that a less restricted steganographic mode (different encryption algorithm, keys, and/or embedding techniques) can be used to assist easy recognition by an authorized party and a more private (confidential) mode may be readable by only a few parties (or only one party) and comprise of the less restricted mode may not affect the security of the more private mode. Items such as documents can be electronically, optically scanned at the sender's end--and printed out in original, printed form at the recipient's end. Document handlers and processors can integrate document scanning and delivery. Can be directly integrated into enterprise and Internet (and similar network) wide document workflow systems and applications. Secure, tamper-resistant electronic appliance, which may employ VDE SPUs, used to handle items at both sender and recipient ends. "Original" item(s) can automatically be destroyed at the sender's end and reconstituted at the recipient's end to prevent two originals from existing simultaneously. Secure, non-repudiable authentication of the identification of a recipient before delivery using any number of different authentication techniques including but not limited to biometric techniques (such as palm print scan, signature scan, voice scan, retina scan, iris scan, biometric fingerprint and/or handprint scan, and/or face profile) and/or presentation of a secure identity "token." Non-repudiation provided through secure authentication used to condition events (e.g., a signature is affixed onto a document only if the system securely authenticates the sender and her intention to agree to its contents). Variety of return receipt options including but not limited to a receipt indicating who opened a document, when, where, and the disposition of the document (stored, redistributed, copied, etc.). These receipts can later be used in legal proceedings and/or other contexts to prove item delivery, receipt and/or knowledge. Audit, receipt, and other information can be delivered independently from item delivery, and become securely associated with an item within a protected processing environment. Secure electronic controls can specify how an item is to be processed or otherwise handled (e.g., document can't be modified, can be distributed only to specified persons, collections of persons, organizations, can be edited only by certain persons and/or in certain manners, can only be viewed and will be "destroyed" after a certain elapse of time or real time or after a certain number of handlings, etc.) Persistent secure electronic controls can continue to supervise item workflow even after it has been received and "read." Use of secure electronic containers to transport items provides an unprecedented degree of security, trustedness and flexibility. Secure controls can be used in conjunction with digital electronic certificates certifying as to identity, class (age, organization membership, jurisdiction, etc.) of the sender and/or receiver and/or user of communicated information. Efficiently handles payment and electronic addressing arrangements through use of support and administrative services such as a Distributed Commerce Utility as more fully described in the copending Shear, et al. application. Compatible with use of smart cards, including, for example, VDE enabled smart cards, for secure personal identification and/or for payment. Transactions may be one or more component transactions of any distributed chain of handling and control process including Electronic Data Interchange (EDI) system, electronic trading system, document workflow sequence, and banking and other financial communication sequences, etc. The present inventions also provide for the use of a trusted third party electronic go-between or intermediary in various forms, including the "virtual presence" of such go-between through the rules and controls it contributes for distributed governance of transactions described in the present invention, and further through the use of a distributed, go-between system operating in on-line and/or off-line modes at various user and/or go-between sites. Such a trusted third-party go-between can provide enhanced and automated functionality, features and other advantages such as, for example: Third party go-between can provide an independent, objective third party assurance of item authenticity, integrity, delivery and/or other actions and/or events. Third party go-between can support non-repudiation of items having legal and/or other important consequences. Third-party go-between can perform auditing, notarizing, authentication, integrity checking, archiving, routing, distributed chain of handling and control processing, and/or other processing. Third party can provide store and forward capabilities. Trusted go-between can supervise execution of legal items such as documents--ensuring that all required conditions are satisfied and that all parties agree before permitting a document to be executed and informing parties of any as-yet-unsatisfied requirements and allow parties to view completed documents on-screen and/or in printed form with "draft, not enforceable" or the like printed on the pages, before final agreement to commit. Actual execution (closing) occurs, for example, as the third party system verifies final, electronically asserted agreement and execution by all parties. Such "atomic" transactions are especially useful in supporting "closings" or the like. Third party go-between can securely audit, manager supervise, and/or control automated electronic negotiations, contract agreement, contract execution, contract notariziation, and/or archiving of contracts, notarized contracts, and/or at least one VDE control set utilized in an electronic negotiation regardless whether or not that negotiation resulted in an executed contract, and regardless of whether or not the entire negotiation was conducted by electronic means. Secure electronic controls can direct tasks to be performed by the third party go-between. Third party go-between can provide a digital time stamp service to certify that a certain version of a certain document existed and was delivered to it at a certain day and time. Third party go-between can legally notarize the item(s) if desired, and can also "notarize" electronic control structures associated with the item(s). Third party go-between can authenticate an item by, for example, opening (e.g. decrypting content) one or more containers; digitally or otherwise "signing" one or mote items to indicate the third party has seen the item(s); verifying the integrity of the item(s) (e.g., using a one way hash function); affixing its own distinctive seal and/or other information to the item; generating audit information for item tracking purposes; and collecting payment based on the services it has performed. Third party go-between can maintain a secure archive of the item(s) and/or identification/authentication information associated with the item(s) (e.g., a "one way hash" value of item contents or portions thereof). A portion or all of such archive (e.g., a "one way hash") may be stored within the affixed, visible seal applied described above. Go-between can also serve as an archive of controls relating to certain items or item types (e.g., to allow a sender to access common controls and/or templates from any of various electronic appliances). Secure electronic controls can provide a message digest that can be delivered to and registered by a trusted go-between as part of the object registry/archiving process. Third party go-between can deliver item(s) to an intended recipient, or simply oversee the delivery transaction as an impartial third party observer. Trusted go-between can deliver a copy and/or the original of an item with or without a seal affixed by the go-between. Trusted third party go-between can maintain or exert control over an item, distributed chain of handling and control process(s), and/or other processes or workflow associated with it. Trusted go-between can support governmental regulatory requirements by acting as a cryptographic key repository for encrypted communications; such secure communications may be accessed by governmental authorities, for example, through a warrant process to provide court or otherwise mandated access to specific communications or communications related information (e.g., for encrypted communications employing long key lengths). Trusted go-between can act as a user rights authority clearinghouse for additional and/or alternative rights which may, for example, be available to particular classes, specific users, at a certain cost, or as specified by the sender. Trusted go-between may also mediate between sender(s) and recipient(s) in response to recipient's request for new, different and/or modified rights or sender's and/or receiver's request for third party archived information (which may require the agreement by only one, expressly either one, or both sender(s) and recipient(s). In addition to multiple individuals and/or parties in several organizations, a trusted go-between may also provide services to parties within a single organization, thus enhancing the security, reliability, auditability, authentication, efficiency, and timeliness of secure document delivery and secure transaction facilitation within a given organization. Trusted go-between may provide services both on public networks, such as the Internet, on internal corporate networks ("Intranets"--irrespective of whether or not they use Internet type conventions), and on private networks connecting two or more individuals and/or organizations exchanging, documents and other content in digital format and/or participating together in various transactions. A third party go-between can provide a communications switching integration. For example, a communications service provider may automatically provide the go-between services for a connection. For example, certain telephone numbers might be offered that have these services built in to the switching network, or a special dialing sequence might be used to access a communications channel with these characteristics. This can provide data links for networks, or be integrated with traditional fax lines, or even voice lines. For example, a fax transmission might be archived, have a seal inserted during transmission, and/or have a hash value stored for later reference. A voice transmission could be similarly managed. Both of these examples have the advantage of compatibility with the existing infrastructure (albeit at the cost of lacking persistent control after delivery). Using this infrastructure for data links has the added advantage of transparency. A third party go-between can provide Transaction Authority services as described in the copending concurrently filed Ginter et al patent application BRIEF DESCRIPTION OF THE DRAWINGS These and other features and advantages provided by the present invention will become better and more completely understood by studying the following detailed description of presently preferred exemplary embodiments in conjunction with the drawings, of which: FIG. 1 illustrates an example of a "Virtual Distribution Environment"; FIG. 1A is a more detailed illustration of an example of the "Information Utility" shown in FIG. 1; FIG. 2 illustrates an example of a chain of handling and control; FIG. 2A illustrates one example of how rules and control information may persist from one participant to another in the FIG. 2 chain of handling and control; FIG. 3 shows one example of different control information that may be provided; FIG. 4 illustrates examples of some different types of rules and/or control information; FIGS. 5A and 5B show an example of an "object"; FIG. 6 shows an example of a Secure Processing Unit ("SPU"); FIG. 7 shows an example of an electronic appliance; FIG. 8 is a more detailed block diagram of an example of the electronic appliance shown in FIG. 7; FIG. 9 is a detailed view of an example of the Secure Processing Unit (SPU) shown in FIGS. 6 and 8; FIG. 10 shows an example of a "Rights Operating System" ("ROS") architecture provided by the Virtual Distribution Environment; FIGS. 11A-11C show examples of functional relationship(s) between applications and the Rights Operating System; FIGS. 11D-11J show examples of "components" and "component assemblies"; FIG. 12 is a more detailed diagram of an example of the Rights Operating System shown in FIG. 10; FIG. 12A shows an example of how "objects" can be created; FIG. 13 is a detailed block diagram of an example the software architecture for a "protected processing environment" shown in FIG. 12; FIGS. 14A-14C are examples of SPU memory maps provided by the protected processing environment shown in FIG. 13; FIG. 15 illustrates an example of how the channel services manager and load module execution manager of FIG. 13 can support a channel; FIG. 15A is an example of a channel header and channel detail records shown in FIG. 15; FIG. 15B is a flowchart of an example of program control steps that may be performed by the FIG. 13 protected processing environment to create a channel; FIG. 16 is a block diagram of an example of a secure data base structure; FIG. 17 is an illustration of an example of a logical object structure; FIG. 18 shows an example of a stationary object structure; FIG. 19 shows an example of a traveling object structure; FIG. 20 shows an example of a content object structure; FIG. 21 shows an example of an administrative object structure; FIG. 22 shows an example of a method core structure; FIG. 23 shows an example of a load module structure; FIG. 24 shows an example of a User Data Element (UDE) and/or Method Data Element (MDE) structure; FIGS. 25A-25C show examples of "map meters"; FIG. 26 shows an example of a permissions record (PERC) structure; FIGS. 26A and 26B together show a more detailed example of a permissions record structure; FIG. 27 shows an example of a shipping table structure; FIG. 28 shows an example of a receiving table structure; FIG. 29 shows an example of an administrative event log structure; FIG. 30 shows an example inter-relationship between and use of the object registration table, subject table and user rights table shown in the FIG. 16 secure database; FIG. 31 is a more detailed example of an object registration table shown in FIG. 16; FIG. 32 is a more detailed example of subject table shown in FIG. 16; FIG. 33 is a more detailed example of a user rights table shown in FIG. 16; FIG. 34 shows a specific example of how a site record table and group record table may track portions of the secure database shown in FIG. 16; FIG. 34A is an example of a FIG. 34 site record table structure, FIG. 34B is an example of a FIG. 34 group record table structure; FIG. 35 shows an example of a process for updating the secure database; FIG. 36 shows an example of how new elements may be inserted into the FIG. 16 secure data base; FIG. 37 shows an example of how an element of the secure database may be accessed; FIG. 38 is a flowchart example of how to protect a secure database element; FIG. 39 is a flowchart example of how to back up a secure database; FIG. 40 is a flowchart example of how to recover a secure database from a backup; FIGS. 41A-41D are a set of examples showing how a "chain of handling and control" may be enabled using "reciprocal methods"; FIGS. 42A-42D show an example of a "reciprocal" BUDGET method; FIGS. 43A-43D show an example of a "reciprocal" REGISTER method; FIGS. 44A-44C show an example of a "reciprocal" AUDIT method; FIGS. 45-48 show examples of several methods being used together to control release of content or other information; FIGS. 49, 49A-49F show an example OPEN method; FIGS. 50, 50A-50F show an example of a READ method; FIGS. 51, 51A-51F show an example of a WRITE method; FIG. 52 shows an example of a CLOSE method; FIGS. 53A-53B show an example of an EVENT method; FIG. 53C shows an example of a BILLING method; FIG. 54. shows an example of an ACCESS method; FIGS. 55A-55B show examples of DECRYPT and ENCRYPT methods; FIG. 56 shows an example of a CONTENT method; FIGS. 57A and 57B show examples of EXTRACT and EMBED methods; FIG. 58A shows an example of an OBSCURE method; FIGS. 58B, 58C show examples of a ELECTRONIC FINGERPRINT method; FIG. 59 shows an example of a DESTROY method; FIG. 60 shows an example of a PANIC method; FIG. 61 shows an example of a METER method; FIG. 62 shows an example of a key "convolution" process; FIG. 63 shows an example of how different keys may be generated using a key convolution process to determine a "true" key; FIGS. 64 and 65 show an example of how protected processing environment keys may be initialized; FIGS. 66 and 67 show example processes for decrypting information contained within stationary and traveling objects, respectively; FIG. 68 shows an example of how a protected processing environment may be initialized; FIG. 69 shows an example of how firmware may be downloaded into a protected processing environment; FIG. 70 shows an example of multiple VDE electronic appliances connected together with a network or other communications means; FIG. 71 shows an example of a portable VDE electronic appliance; FIGS. 72A-72D show examples of "pop-up" displays that may be generated by the user notification and exception interface; FIG. 73 shows an example of a "smart object"; FIG. 74 shows an example of a process using "smart objects"; FIGS. 75A-75D show examples of data structures used for electronic negotiation; FIGS. 75E-75F show example structures relating to an electronic agreement; FIGS. 76A-76B show examples of electronic negotiation processes; FIG. 77 shows a further example of a chain of handling and control; FIG. 78 shows an example of a VDE "repository"; FIGS. 79-83 show an example illustrating a chain of handling and control to evolve and transform VDE managed content and control information; FIG. 84 shows a further example of a chain of handling and control involving several categories of VDE participants; FIG. 85 shows a further example of a chain of distribution and handling within an organization; FIGS. 86 and 86A show a further example of a chain of handling and control; and FIG. 87 shows an example of a virtual silicon container model. FIG. 88 shows an example trusted electronic delivery system; FIGS. 89 shows a detailed view of an example electronic intelligent kiosk appliance; FIGS. 90A and 90B show example options the sender can select for electronic delivery; FIG. 91A shows example steps to send an item; FIG. 91B shows example steps to receive an item; FIGS. 92 and 92A show example trusted electronic delivery providing a return receipt; FIG. 93 shows example trusted item delivery from an intelligent kiosk to a personal computer; FIGS. 94 & 95 show examples of trusted electronic delivery between personal computers; FIG. 96 shows an example trusted item handling and delivery within an organization; FIG. 97 shows an example trusted electronic document execution; FIG. 98 shows an example multi-party electronic document execution; FIG. 99 shows an example trusted electronic go-between; FIG. 100 shows an example use of the trusted electronic go-between for notarizing and/or archiving; FIG. 101 shows an example electronic legal contract execution using a trusted electronic go-between; FIG. 101A shows an example electronic requirements list; FIG. 101B shows an example multi-party electronic legal contract execution using a trusted electronic go-between; FIG. 102 shows example use of trusted electronic go-betweens within and outside of organizations; FIG. 103 illustrates an example secure object; FIG. 104 shows example electronically-generated signatures, seals and electronic fingerprints; FIG. 105A shows an example way of hiding information within line spacing; FIG. 105B shows an example way of hiding information within letter spacing; FIG. 105C shows an example electronic fingerprint; FIGS. 106A-106C show example electronically generated seals; FIGS. 107A and 107B show detailed electronically generated seal examples; FIG. 108 shows an example process for creating digital information for encoding into an item or item seal; FIG. 109 shows an example electronic appliance; FIGS. 110-113 show example processes for securely sending an item; FIG. 113A shows an example routing slip data structure; FIG. 113B shows an example audit trail data structure; FIG. 114A-118 show example processes for securely receiving an item; FIG. 119 shows an example architecture for a trusted electronic go-between; FIGS. 120A-120B show example reciprocal control set usage to provide a trusted electronic go-between having secure electronic notarization capabilities; FIG. 121 shows example steps performed by a trusted third party go-between to receive an item; FIGS. 122 and 123 show example trusted go-between processes; FIGS. 124A-124B and 125A-125B show example contract execution processes; FIG. 126 shows an example automobile purchase providing electronic contract execution through a trusted electronic go-between; FIG. 127 shows an example use of a trusted electronic go-between to provide electronic item notarization; FIG. 128 shows an example secure item delivery with real time teleconferencing capabilities; FIG. 129 shows a health insurance example; FIG. 130 shows an example real estate "atomic" settlement; FIG. 130A shows example transaction rules; FIG. 131 shows an example judicial electronic data interchange (EDI); FIG. 132 shows an example Patent Office automation; FIG. 133 shows an example tax filing; and FIG. 134 shows an example using facsimile transmission. DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS The entire disclosure of the above-referenced Ginter et al. patent specification is incorporated by reference in connection with FIGS. 1-87. FIG. 88 shows an electronic trusted delivery system 4050. In this example, sender 4052 is sending an item 4054 to a recipient 4056 over an electronic network 4058. In this example, electronic delivery over network 4058 is by way of a secure, trusted electronic delivery virtual distribution environment transport mechanism 4060 which is shown for purposes of illustration as an electronic delivery person. Delivery person 4060 is shown as a human being for purposes of illustration, but in the example is actually an automatic, trusted electronic delivery means supported and provided by virtual distribution environment 100. Item 4054 might be a document such as a handwritten or typed letter, or it could be a legal document such as a contract. It could have both text and pictures, just text or just pictures. It could be a sound recording, a multimedia presentation, or a visual work such as a film or television program. Item 4054 could be any item or information capable of being represented in digital form. The item 4054 can be initially presented to the appliance 600 in electronic form (for example, on a diskette), or the appliance can convert it from some other form into electronic form. Electronic delivery person 4060 receives item 4054 in digital form and places it into a secure electronic container 302--thus forming a digital "object" 300. A digital object 300 may in this case be, for example, as shown in FIGS. 5A and 5B, and may include one or more containers 302 containing item 4054. FIG. 88 illustrates secure electronic container 302 as an attache case handcuffed to the secure delivery person's wrist. Once again, container is shown as a physical thing for purposes of illustration only--in the example it is preferably electronic rather than physical, and comprises digital information having a well-defined structure (see FIG. 5A). Special mathematical techniques known as "cryptography" can be used to make electronic container 302 secure so that only intended recipient 4056 can open the container and access the electronic document (or other item) 4054 it contains. In this example, sender 4052 sends item 4054 by supplying the document to an electronic appliance 600A. In this example, electronic appliance 600A is an intelligent electronic walk-up kiosk that may be located in a public place or on private property, such as the offices or work areas of a firm. Appliance 600A in this example has a document slot 4102 into which sender 4052 can feed item 4054. Electronic appliance 600A can automatically, optically scan the item 4054 and convert it into digital information for sending over an electronic connection or network 4058 (such as, for example, electronic highway 108 shown in FIG. 2). The item 4054 can be sent to one or many recipients specified by sender 4052. FIG. 89 shows an example appliance 600A in the form of an intelligent walk-up kiosk. This example kiosk appliance 600A could be installed in an office building lobby, shopping mall, office supply store, or other public place for walk-up use by members of the public. It could also be installed in a location within a corporate or business office (e.g., a mail room) for use by company employees. The kiosk appliance 600A is an example. Aspects of the present invention can be used with other types of electronic appliances such as personal computers or computer workstations for example (see FIGS. 7 and 8, and 93-93C for example). Referring to FIG. 89, the example kiosk appliance 600A can include a computer screen 4104 for displaying informational messages, and user operable controls 4106 such as push buttons for allowing sender 4052 to select between delivery options. Appliance 600 in this example may also include a card reader 4108 for reading a credit card or other kind of card provided by the sender 4052. Additionally, if desired, electronic appliance 600A may include a telephone receiver 4110 and telephone dialing keypad 4112 (or other input devices) to allow sender 4052 to get information and assistance or give additional instructions. Electronic appliance 600A may optionally include a keyboard for entering textual and other information (not shown). Also as shown in FIG. 89, electronic appliance 600A may optionally include a video camera 4124 and may display remote video in a "window" 4126 on screen 4104 (or on an optionally separate screen not shown). Camera 4124 allows appliance 600 to take a photograph of sender 4052 and/or recipient 4056. It may also allow sender 4052 and recipient 4056 to see each other in order to simultaneously authenticate each other's identity visually--and to have a "teleconference" discussion about item 4054 or other matters. The electronic appliance 600 may also have a microphone/speaker 4140 perhaps to coordinate details of the pending transaction. Appliance 600A might also include a media reader 4132 to read from a floppy diskette, smart card or other digital storage device. The appliance 600 can include, in addition, a document shredder/destroyer 4115. Also as shown in FIGS. 88 and 89, appliance 600A in this example has a secure processing unit (SPU) 500 (see FIG. 6). SPU 500 provides a tamper-resistant protected processing environment ("PPE") in which processes and transactions can take place securely and in a trusted fashion. FIG. 91A shows example steps for sending an item such as item 4054. To send item. 4054 to recipient 4056, sender 4032 may first press buttons 4106 and read display 4104 to select between different delivery options (see FIG. 91A, step 4090A). FIG. 90A shows some example service options, and FIG. 90B shows some more detailed delivery options. For example, sender 4052 might press a button corresponding to "delivery options," which might cause appliance 600A to display the FIG. 90A menu screen of various delivery options. These delivery options could include, for example: receipt options (what kind of receipt, if any, sender 4052 wishes to receive documenting delivery of item 4054 to intended recipient 4056); integrity guarantee options (providing high levels of assurance that item 4054 was delivered in its entirety without any errors, and without any accidental or intentional modifications); privacy options (for example, whether recipient 4056 is to know who sender 4052 is or where she has sent the document from); and more options. Electronic appliance 600A may also ask the user to identify intended recipient 4056 (FIG. 91A, step 4090B). Sender 4052 may select different ways to identify recipient 4056 based on the confidentiality of the document and the level of security the sender is willing to pay for. In one example, sender 4052 might require the recipient's appliance 600B to require recipient 4056 to prove that he is who he says he is. This secure "authentication" function might be met by, for example, requiring recipient 4056 to input a password, present digital proof of identity using, for example: a digital document or "certificate" issued by a trusted third party, and/or have appliance 600 measure a biometric characteristic of the recipient such as, for example, taking the recipient's photograph (and possibly automatically compare it with a known photograph of the recipient supplied by sender 4052 or system 4050) or using any other biometric sensing technique. Sender 4052 may also specify the electronic address of recipient 4056, or it might let system 4050 automatically, securely and confidentially locate the recipient using a secure directory service as described in the copending Shear et al. application. Once sender 4052 has selected the service options she desires, appliance 600 may next display a message on computer screen 4104 asking sender 4052 to insert item 4054 into document slot 102 for electronic scanning. When the sender 4052 inserts the document 4054 or other item (FIG. 91A, block 4030C), electronic appliance. 600 may (if necessary) automatically, optically scan item 4054 to create an electronic, digital form of the document (using conventional optical scanning and optical character recognition technology, for example). During this scanning process, appliance 600 might display a message on computer screen 4104 such as "I am scanning your document now . . . " Instead of feeding in a document, the sender might provide the document or other item in digital form by inserting a floppy diskette or smart card into reader 4132, or by connecting a portable computer up to port 4130 and having the portable computer "upload" the document into appliance 600. The item 4054 to be sent need not be a document, but could be any type of item capable of being transformed into digital form such as, for example: pictures or other graphical information; sound information such as voice, music or both; executable computer program or other code; video, film or other moving image sequences; multimedia, video games and the like; any combination or subcombination of the above. After appliance 600 has scanned or otherwise received the entirety of document 4054 or other item, appliance 600 may calculate and display a total price on computer screen 4104 and ask sender 4052 to pay for the service (FIG. 91A, block 4090D). The calculated price may, for example, depend in part on the size and/or number of items to be securely delivered. The appliance may then ask sender 4052 to confirm she wishes to send the document to the recipient 4056 (FIG. 91A, block 4090E). Upon receiving that confirmation (FIG. 91A, "y" exit to decision block 4090E), appliance 600 may request sender 4052 to pay, for example, by inserting her credit card into card reader 4108 as a form of payment, or it might use other payment arrangements (FIG. 9aA, block 4090F). Appliance 600 may then package the digital form of document into secure electronic container 302 and send it over electronic network 4058 for secure delivery to recipient 4056 (FIG. 91A, block 4090F). Because system 4050 uses the secure "virtual distribution environment" 100, sender 4052 can have a high degree of confidence and trust that item 4054 will be usable only by intended recipient(s) 4056 and to no one else. FIG. 91B shows example steps for receiving an item. Intended recipient 4056 may receive delivery of the document by walking up to the same or different electronic appliance intelligent kiosk 600B and operate controls 4106 instructing the appliance to deliver the document to him (FIG. 91B, block 4092A). Depending upon the delivery options sender 4052 selected, appliance 600 may require recipient 4056 to prove he is who he says he is (FIG. 91B, block 4092B). For example, appliance 600B may require recipient 4056 to provide a secret password and/or it may require the recipient to insert a special card into card reader 108. This special card may certify the identity of recipient 4056. Appliance 600B might also take the recipient's picture using camera 4124, and automatically compare the picture with a known photographic image of the recipient to see if they match. Once appliance 600 is satisfied regarding the identity of recipient 4056, it may require the recipient to pay (FIG. 91B, block 4092C)--such as for example in a "collect on delivery" model. The appliance 600 may then open the secure electronic container ("attache case") 302 and deliver the item it contains to recipient 4056 (FIG. 91B, block 4092D). For example, if the container 302 contains item 4054, prints the copy of the document, and provides the printed copy through document slot 4102. It could also give recipient 4056 a digital copy of the item 4054 (such as a document) via media drive 4132 and/or port 4130. Appliance 600B may deliver the digital copy of item 4054 within a container 302 and/or may protect the item with seals, electronic fingerprints, watermarks and/or other visible and/or hidden markings to provide a "virtual container" or some of the security or other characteristics of a container (for example, the ability to associate electronic controls with the item). EXAMPLE ELECTRONIC DELIVERY AND RETURN RECEIPT FIG. 92 illustrates one example delivery of item 4054 to recipient 4056. In this example, the virtual electronic delivery person 4060 demands to see a certificate or token 4064 proving that recipient 4056 is the same person sender 4052 designated to receive item 4054 (FIG. 91B, block 4092B). Recipient 4056 could provide this certificate 4064 by, for example, supplying a "smart" electronic card containing the certificate in digital form. Alternatively or in addition, if sender 4052 so required, electronic delivery person 4060 might require stronger forms of personal authentication such as, for example, a voice print, fingerprint or handprint test, identification based on other physical (biometric) characteristics such as face profile, retinal or iris patterns of the eye, or the like. There are advantages to using multiple authentication techniques in combination. For example, a well made certificate is essentially unforgeable (which is to say, it would be easier to fabricate a electronic fingerprint carrying device, for example, than a well made certificate 4064 barring unforeseen advances in mathematics), but the trouble with certificates is the weakness of correlation between physical access (e.g., holding the card, or sitting at the appliance) and permission to use. Passwords are a weak form of authentication--that is, establishing this correlation. Biometric techniques, particularly iris and retinal scans, are stronger forms of authentication. It is possible for biometric information to be encoded in a field of a certificate 4064, and for the software controlling the card to confirm that the biometric input is consistent with the field in the certificate prior to authorizing use of the certificate or the card in general. This authentication may be limited in time (e.g., using an inactivity time out, each time the card is inserted, etc.) In addition, a transaction might require this authentication to occur simultaneous with use (rather than for an entire session, even if the card only requires one authentication per session). After payment has been arranged (FIG. 91B, block 4092C), electronic delivery person 4060 will open secure container 302 and give recipient 4056 a printed and/or electronic copy of item 4054 only once he is satisfied--to the degree required by sender 4052--that the recipient 4056 is the correct person. Electronic delivery person 4060 may also note various information about the delivery (illustrated here by having him write the information down on a clipboard 4066, but implemented in practice by electronically storing an "audit" trail). System 4050 may--based on the particular receipt options sender 4052 requested--provide the sender with an electronic and/or paper receipt of the type shown in FIG. 92A, for example (FIG. 91B, step 4092D). Such an example receipt 4066 might specify, for example: item and/or transaction number; name of actual recipient 4056 to whom the item was delivered; the company recipient 4056 works for; day, date and time of day of delivery; who actually opened and read or used an item 4054; when (day, date and time of day) item 4054 was actually opened and read, and the public key of the trusted third party that issued the digital certificate 4064 attesting to the identity of recipient 4056. The sender's electronic appliance 600A and the recipient's electronic appliance 600B can report their respective "audit trails" periodically or upon completion of delivery or some other event. They can report the audit information to a support facility such as information utility usage analyst 200C (see FIG. 1A). Usage analyst 200C can work with report creator 200D to issue a written or electronic report to sender 4052. Alternatively, since electronic appliances 600A, 600B are secure, the electronic appliances can maintain copies of the audit trail(s) and produce them in secure form on demand at a later date to evidence or prove that the document was sent and delivered (for example, so sender 4052 can't deny she sent the item and recipient 4056 can't deny he received the item). The appliances 600A, 600B could store an entire copy of the item 4054, or they could instead store a "message digest" that could later be used to securely prove which item was sent. Other Types of Electronic Appliances can be Used As mentioned above, the kiosk appliances 600 shown in FIGS. 88 and 89 are just one example of electronic appliances that can be used for secure document delivery. Secure electronic delivery can also be from one personal computer 4116 to another. FIGS. 93-96 show that system 4050 can be used to deliver documents securely between various different kinds of electronic appliances--personal computers, for example. FIG. 93 shows that electronic kiosk appliance 600A may send item 4054 to a different type of electronic appliance 600C such as a personal computer 4116 having a display 4120, a keyboard 4118 and a pointer 4122. Personal computer 4116 in this example is also provided with a secure processing unit 500 or software based HPE 655 (See FIG. 12) to provide secure, tamper-resistant trusted processing. In this example, kiosk appliance 600A and personal computer appliance 600C are both part of virtual distribution environment 100 and are interoperable with one another in a secure fashion. Secure delivery can also be from one personal computer 4116 to another. FIG. 94 shows a sender 4052 inputting item 4054 into an optical scanner 4114 connected to a personal computer 4116'. Electronic delivery person 4060 can deliver the electronic version of item 4054 within secure container attache case 302 from personal computer 4116' to another personal computer 4116 operated by recipient 4056. FIG. 95 shows that the item 4054 delivered by electronic delivery person 4060 need not ever exist in paper form. For example, sender 4052 might input digital information directly into personal computer 4116' through keyboard 4118--or the item could originate from any other secure or non-secure digital source. Sender 4052 may then cause electronic delivery person 4060 to deliver this digital item 4054 to the recipient 4056's personal computer 4116 for viewing on display 4120 and/or printing on printer 4122. Item 4054 can also be inputted from and/or outputted to a floppy diskette or other portable storage medium, if desired. As mentioned above, item 4054 can be any sort of digital information such as, for example text, graphics, sound, multi-media, video, computer software. The electronic delivery functions can be provided by software integrated with other software applications (e.g., electronic mail or word processing) executing on personal computer 4116. FIG. 96 shows an example in which multiple electronic appliances 600(1), . . . , 600(N), 600A and 600B communicate with a secure electronic delivery computer "server" 4150 over a network 4152. For example, appliances 600(1), . . . , 600(N) may each be a personal computer or other workstation 4116. Appliance 600A may be, for example, a network facsimile device including a document scanner and document printer. Appliance 600B may be one or more additional "servers" of various types. Each of these various appliances 600 may use secure electronic delivery server 4150 to provide secure electronic item delivery and handling services. Server 4150 may include a secure processing unit 500 (PPE) interoperable with other VDE-capable electronic appliances, and may communicate with such other electronic appliances over a communications link 4154 such as the Internet or other electronic network. Each of the other appliances 600 may also include an SPU 500 (PPE) if desired to provide security and interoperability with other VDE-capable devices over network 4152. Electronic Execution of a Legal Document FIG. 97 shows that trusted delivery system 4050 can also be used to electronically execute a legal contract 4068. In many cases it may be very inconvenient for the parties 4070A, 470B to a legal contract 4068 to meet face-to-face and physically sign the contract. For example, one of the contracting parties may be geographically distant from the other. It may nevertheless be important for the contract 4068 to be finalized and executed rapidly, reliably and in a manner that cannot be repudiated by either party. System 4050 supports "simultaneous" as well as non-simultaneous contract or other document execution among contracting parties 4070. Simultaneous completion allows multiple parties located in physically different locations to directly and simultaneously participate in the execution of legal documents and/or other transactions that require authorizations. Currently, businesses often prefer simultaneous execution of documents at what is called a "closing." Such closings for important documents frequently require the presence of all participants at the same location to simultaneously sign all necessary legal documents. Business executives are often reluctant to sign a set of documents and then send them to the next party to sign, since special legal language may be required to release the first (or early) signing party if the documents are not quickly signed by other participants and since certain liabilities may exist during this interim period. FIG. 97 shows an example in which two contracting parties 4070A, 4070B each simultaneously sit down in front of an electronic appliance 600 such as a personal computer or intelligent electronic kiosk. Each of the contracting parties 4070 may be required to securely identify themselves by, for example, inserting a card 4109 into a card reader 4108 and/or by allowing a biometric sensor 4124 to scan a part of their body such as a finger print or a retina pattern--thereby proving that they are who they say they are. One relatively weak form of authentication is physical possession of the card 4109. Nonetheless, if some form of weak authentication is used and biometric information is gathered in real time by sensor 4124, it may be correlated with some trusted record stored elsewhere, and/or delivered along with the item 4054. If biometric information is codelivered with the item 4054, and, it is ever actually used, it must be correlated with a trusted record (this trusted record could, for example, be generated by the person providing biometric data in the presence of a trusted party if the validity of a transaction is called into question, at the sacrifice of significant automation and "commercial confidence" benefits). The ability to establish trust as the transaction occurs, rather than having some degree of nonrepudiation later (imagine if the transaction were fraudulent, and a user relied on the person showing up to give a retinal scan) is one significant benefit of example system 4050. If the parties are simultaneously at their respective electronic appliances 600, they may verify each other's identity using video cameras and screens built into the kiosk. Such simultaneous execution has the advantage of allowing multiple parties at different physical locations to negotiate a deal in real time and then simultaneously, reliably execute and receive final, signed agreement copies that are valid and legally binding. Trusted delivery mechanism 4060 may send messages such as offers 4054A and acceptances 4054B between the two electronic appliances 600A, 600B. These messages may be packaged within secure electronic containers 302. Some of these may be human readable, others may be automated as in FIGS. 76A and 76B. If they are human readable and operator managed during negotiation, they may represent a user interface aspect of control structures (e.g., see load module DTD description in connection with FIG. 23, and pop up user interface usage in connection with FIG. 72C). Once the parties 4070A, 4070B agree on the terms of the contract, they may securely indicate their agreement and system 4050 can generate an electronic and/or paper contract document 4068 that evidences and memorializes the agreement. As will be discussed below, contract document 4068 may have special attributes such as seals 4200, hand-written signatures 4300 and/or visual or hidden "electronic fingerprint" information 4400. Such seals 4200, signatures 4300 and electronic fingerprints 4400 can be used to establish the authenticity of the document (for example, preventing a signatory from repudiating it and to allowing it to be admitted as evidence in a court of law). FIG. 98 shows that system 4050 can be used to electronically form contract 4068 between any number of different parties. Electronic network 4058 might, for example, be a world-wide electronic highway 108 or other network such as the Internet, with the various parties being located in many different locations around the world. Alternatively, electronic network 4058 might be a private data network within an organization--or it might be a mixture of the two. Different contracting parties 4070 may use different kinds of electronic appliances 600 such as, for example, personal computers, intelligent walk-up kiosks, home television sets, or any other type of electronic appliance capable of securely receiving and providing information about contract 4068. System 4050 can electronically pass contract 4068 along a "chain" from one party 4070 to the next ("Round Robin"), collecting signatures as it travels along. System 4050 can also allow each party 4070A-4070F to communicate with any other party. One copy of contract 4068 could be passed along from party to party and iteratively signed at the respective signers' locations. The last signer could then broadcast final, signed copies of contract 4068 to all parties. The electronic containers 302 can specify who the next recipient of contract is--forming a trusted chain of handling and control for contract 4068. In one example, all of the parties 4070 may be required to hit an "I Agree" button (e.g., by placing a finger onto a biometric sender 4124 shown in FIG. 97, "clicking" on a displayed "I agree" icon, etc.) before this transaction is actually carried out. Then, barring a system failure, the execution is effectively simultaneous, since it isn't initiated until everyone has indicated their approval, and won't be completed unless each system performs correctly. Trusted Electronic Go-Between FIG. 99 shows that system 4050 may introduce a trusted electronic "go-between" or intermediary 4700 between the sender 4052 and recipient 4056 (and/or between two or more contracting parties 4070). Trusted go-between 4700 acts as an impartial overseer who can document a transaction, and may also become actively involved in directing the transaction to see to it that it is completed properly. Trusted electronic go-between 4700 may provide valuable third party services such as, for example: maintaining a secure archive of data, receipts and other information about transmissions senders 4052 sends to recipients 4056; managing the transaction for example, so that not all parties need to participate simultaneously or to ensure that all prerequisites or preconditions have been satisfied); making certain certifications about information sent via system 4050 such as acting as a digital witness by notarizing documents and transmissions. The drawings show the trusted go-between 4700 as a person for purposes of illustration only. In the preferred example, trusted go-between 4700 may be a computer that performs its functions electronically in a highly automatic and efficient way. In one example, the computer's capabilities may be augmented by human participation. FIG. 100 shows one example use of a trusted electronic go-between 4700 to assist in delivering an item such as document 4054 from sender 4052 to recipient 4056. In this example, sender 4052 may send the item 4054 directly to recipient 4056 within one or more secure electronic containers 302. Alternatively, sender 4052 can send item 4054 (or a copy of it) to trusted electronic go-between 4700 within a secure electronic container 302A. When the trusted electronic go-between 4700 receives container 302A, she may be authorized to open the container, remove item 4054 and affix her seal 4200 to the document. Seal 4200 may certify, notarize and/or "date stamp" the item 4054 as having been received and seen by trusted electronic go-between 4700 on a certain day at a certain time. Trusted electronic go-between 4700 may keep a copy of item 4054 within a secure electronic library or archive 4702.sub.[BW1]. In addition, if desired, trusted electronic go-between 4700 may deliver a copy of item 4054 with the affixed seal 4200 to recipient 4056. When recipient 4056 opens the secure electronic container 302B, he will notice the seal 4200 and have confidence that it is the same item 4054 that was seen and archived by the trusted electronic go-between 4700. In this example, recipient 4056 may directly provide a return receipt 4066 within an additional secure electronic container 302C--or trusted electronic go-between 4700 can provide such a return receipt to sender 4052 based on audit information provided by recipient 4056 and/or originated by the trusted go-between. The Trusted Electronic Go-Between can Help with Contracts FIG. 101 shows how trusted electronic go-between 4700 can make it easier for parties 4070 to execute a legal contract 4068. In this example, the trusted electronic go-between 4700 can maintain a requirements list 4704. This requirements list 4704 (an example of which is shown in FIG. 101A) may specify all of the steps that must be completed and all of the conditions that must be satisfied in order to execute legal contract 4068. Trusted electronic go-between 4700 can monitor the electronic communications between the contractual parties 4070A, 4070B, and notify them of additional requirements that need to be met before the contract 4068 can be signed. In one example, trusted electronic go-between 4700 can also act as a mediator to resolve disputes between the contracting parties 4070A, 4070B, and can help negotiate the contract. At the conclusion of the contracting process, trusted electronic go-between 4700 may affix its own seal 4200A to the executed contract document 4068. This seal 4200A may provide a guarantee or assurance that all of the steps required by trusted electronic go-between 4700 were fulfilled before the contract 4068 was executed and that the contracting parties 4070A, 4070B are who they say they are and had authorization to execute the contract. FIG. 101B shows how the trusted electronic go-between 4700 could be the focal point for a contractual relationship between a number of different contracting parties. In this example, trusted electronic go-between 4700 might communicate directly with each of the various contracting parties 4070 via electronic digital messages, and create the resulting executed contract based on these communications. In one example, go-between 4700 doesn't tell any participant 4070 who has already agreed and who hasn't. The SPU's 500 (PPEs) of each party's appliance 600 can receive administrative objects (see FIG. 21) with the information about each approval, yet this information does not need to be released outside the SPU (PPE). In this model, the rules associated with affixing electronic signatures (digital and/or an image of a physical signature) can be established at the beginning of the negotiation to indicate the list of parties 4070 that must agree. Then, as each party 4070 agrees, their electronic appliance SPU 500 (PPE) will send administrative objects to each of the other participants containing one or more events and data associated with those events that can be processed by the controls associated with use of their signature. If the administrative objects omit the creator identity public header 804 information (see FIG. 17), and the information is transmitted via a remailer (or other intermediary) when network addresses could be used to identify a sender, there will be no way to determine the identity of the sender outside the SPU (PPE) 500. As soon as all of the conditions for use of the signature have been fulfilled, and an event is presented to sign the document, the rest of the transaction can go forward. It is extremely useful to have trusted go-between 4700 monitoring this activity to order the application of signatures (if required), and to allow a roll back if the system fails before applying all of the signatures. The role of go-between 4700 may, in some circumstances, be played by one of the participant's SPU's 500 (PPEs), since SPU (PPE) behavior is not under the user's control, but rather can be under the control of rules and controls provided by one or more other parties other than the user (although in many instances the user can contribute his or her own controls to operate in combination with controls contributed by other parties). In another example, the go-between role 4700 may comprise a "virtual go-between" comprised of a one, a combination of plural, or all, nodes of participants in a collective or other group. Governance can be shared through the interaction of rules and controls of the various node PPEs producing a go-between control role. Upon the completion of a go-between managed transaction, transaction audit information for archive, billing, security, and/or administrative purposes may be securely transmitted, directly, or through one or more other participating in the virtual go-between. The Secure Electronic Go-Between can be Used Within and Between Organizations FIG. 102 shows an example use of system 4050 for inter- and intra-organizational communications. FIG. 102 shows an organization A (left-hand side of the drawing) as having an "Intranet" (a private data network within a particular organization) 5100(A). Intranet 5100(A) may be a local and/or wide area network for example. User nodes 600(A)(1), . . . , 600(A)(N) (for example, employees of organization A) may communicate with one another over Intranet 5100(A). FIG. 102 also shows another organization B that may have its own Intranet 5100(B), user nodes 600(B)(1), . . . , 600(B)(N), and private trusted go-between 4700(B). In addition, FIG. 102 shows a public data network 5104 (such as the Internet for example) and a public trusted go-between 4700(C). FIG. 102 shows that in this example, organizations A and B communicate with the outside world through trusted go-between 4700(A), 4700(B) (which may, if desired, also include "gateways", "firewalls" and other associated secure communications components). In other examples, trusted go-between 4700(A), 4700(B) need not be the actual "gateway" and "firewall" to/from Internet 5104, but could instead operate wholly internally to the respective organizations A, B while potentially generating electronic containers 302 for transmission over Internet 5104. In this example, organization A user nodes 600(A)(1), . . . , 600(A)(N) each have an instance of a virtual distribution environment protected processing environment, and can communicate with one another over Intranet 5100(A) via secure electronic containers 302. Similarly, organization A user nodes 600(B)(1), . . . , 600(B)(N) each have an instance of a virtual distribution environment protected processing environment, and can communicate with one another over Intranet 5100(B) via secure electronic containers 302. In addition, organization A and organization B can communicate with one another over Internet 5104 via secure electronic containers 302. Organization A's private trusted go-between 4700(A) may be used for facilitating organization A's internal communications and processes. Private trusted go-between 4700(A) might be used, for example, to carefully track documents and other items sent from one user to another within organization A. The public go-between 4700(C), meanwhile, can be used to coordinate between organization A and organization B without, for example, revealing confidential information of either organization to the other organization. Below are more detailed examples of how the FIG. 102 arrangement might be advantageously used to conduct business transactions. More About the Secure Electronic Container FIG. 103 shows an example secure electronic object 300 and its contents. Once again, although object 300 is shows as a locked attache case for illustration purposes, the object and its associated container 302 is typically electronic rather than physical and may provide security, trustedness and confidentiality through use of strong cryptographic techniques as shown in FIGS. 5A, 5B and 17-26B. In this example, secure container 302 may contain a digital image 4068I of a document or other item 4054 to be delivered from one party to another. This image may include one or more seals 4200, one or more hand-written signatures 4300, and one or more electronic fingerprints 4400. The item 4054 may be multiple pages long or it may be a single page. The item 4054 may contain text, pictures or graphical information, computer instructions, audio data, computer data, or any combination of these, for example. Image 4068I may be represented in a so-called "universal" format to allow it to be created and displayed and/or printed by any standard software application capable of processing items in the appropriate "universal" format. If desired, image 4068I may include cover sheets, virtual "stick on" notes, and/or the like. Secure container 302 may contain any number of different 4054. Container 302 may also contain another, data version 4068D of the item 4054. This data version 4068D might, for example, comprise one or more "word processing" files corresponding to a text document, for example. The container 302 may also contain one or more tools 4074 for using image 4068I and/or data 4068D. Tools 4074 might be used to allow the intended recipient 4056 to manipulate or view the image 4068I and/or the data 4068D. Tools 4074 might be computer programs in one example (as mentioned above, item 4054 can also be a computer program such as a program being sold to the recipient). Secure container 302 may also contain an electronic, digital control structure 4078. This control structure 4078 (which could also be delivered independently in another container 302 different from the one carrying the image 4068I and/or the data 4068D) may contain important information controlling use of container 302. For example, controls 4078 may specify who can open container 302 and under what conditions the container can be opened. Controls 4078 might also specify who, if anyone, object 300 can be passed on to. As another example, controls 4078 might specify restrictions on how the image 4068I and/or data 4068D can be used (e.g., to allow the recipient to view but not change the image and/or data as one example). The detailed nature of control structure 4078 is described in connection, for example, with FIGS. 11D-11J; FIG. 15; FIGS. 17-26B; and FIGS. 41A-61. Secure container 302 may also include one or more routing slips 4072 and one or more audit trails 4077. Routing slip 4072 and audit trail 4076 are data structures defined by and/or associated with electronic controls 4078, and may be integrated as part of these electronic controls (see FIGS. 22-26B for example). Routing slip 4072 might be used to electronically route the object 300 to the intended recipient(s) 4056 and to specify other information associated with how the object 300 is to be delivered and/or handled. Audit trail records 4077 may be used to gather and recover all sorts of information about what has happened to object 300 and its contents (e.g., where container 302 has been, how image 4068I has been used, etc.). Audit trail 4077 may be used, for example, to generate a return receipt as shown in FIG. 92A. Routing slip 4072 and/or audit trail records 4077 (and associated controls 4078) don't have to be delivered within the same container 302 that contains the image 4068I and/or the data 4077--they can be delivered independently in another container 302 if desired. Document Signatures FIG. 104 shows some examples of how system 4050 can "sign" printed item 4054. In most modern societies, a person indicates his or her assent to a legal document by affixing his or her hand-written signature and/or seal. In the United States, for example, the act of hand writing one's signature on a document may legally bind the signer to the terms and conditions set forth in the document. In other countries (notably Japan), a person indicates assent and agreement to be legally bound by imprinting the document with a special stamp unique to that person. A corporation may emboss legal documents with its corporate seal to indicate the corporation's assent to the document contents. Governmental authorities in many counties use official seals to certify that the document is an official one. System 4050 in this example can accommodate any or all of these conventions by imprinting various graphics and/or symbols on printed item 4054. In the FIG. 104 example, item 4054 bears a "hand-written" signature 4300, a seal 4200, and a electronic fingerprint 4400 (that in one example may comprise a "hidden signature"). Hand-written signature 4300 may be a graphical image of the signer's own hand-written signature. System 4050 can obtain this hand-written signature image 4300 in a number of ways. For example, system 4050 may require the signer to sign his or her signature at the time item 4054 is created. In this example, once the document is finalized, sender 4052 or contracting party 4070 can sign his or her signature using a magnetic or pressure-sensitive signature capture device, for example. Such conventional signature capture devices electronically capture the image of a person's signature and store it in a memory. System 4050 can then--once it securely obtains the authorization of the signer with a very high degree of trustedness and sureness (e.g., by requesting a password, biometric test, etc.)--place hand-written signature 4300 onto an appropriate part of item 4054. Alternatively, the signer may carry his or her hand-written signature on a portable storage medium such as, for example, a magnetic, smart or memory card. The portable storage unit may employ rules and controls for budgeting the number of times and/or class and/or other circumstances of a transaction that a signature can be employed, or before the device needs to re-connect to a remote authority as disclosed in the above-referenced Shear et al. patent. The signer can present this storage medium to system 4050 as a source for the signature image 4300 shown in FIG. 104. Once system runs certain checks to ensure that the signer is in fact the one who'has presented the signature card, the system can securely read the signer's hand-written signature from the medium and place it on to item 4054. In still another example, system 4050 may securely maintain hand-written signature files for a number of different users in a secure archive or "secure directory services" as disclosed in the above-referenced Shear et al. patent disclosure. At a user's request, system 4050 may call up the signature file pertaining to that user and impress the corresponding signature onto item 4054. If an image representation of a signature is stored on portable media or in a directory service, the image may be stored in an electronic container 302. Such a container 302 permits the owner of the signature to specify control information that governs how the signature image may be used. In addition, or alternatively, the signature image may be stored in or securely associated with a field of a digital certificate (that may, for example, also incorporate other identifying information). FIG. 104 also shows a "electronic fingerprint" 4400. Electronic fingerprint 4400 may be used to indicate the signer's name and other information (such as, for example, the date and time of the transaction, the signer's public key, etc.) within the item 4054 contents in the way that makes it difficult to remove the information. A term derived from Greek roots, "steganography" which means "hidden writing"--applies to such techniques that can be used to hide such information within a document while allowing it to be recovered later. Example techniques for hiding information from within text include, for example, varying the spacing between lines of text by an almost imperceptible amount to encode information (see FIG. 105A), varying by very slight amounts the spacings ("kerning") between words or characters (see FIG. 105B). System 4050 can use such "steganography" techniques to hide information within an item 4054 (e.g., by slightly permuting the gray scale or color frequencies across a document) so it can be later recovered and used to authenticate and/or identify the document--and/or it can use visible electronic fingerprinting or watermarking techniques to provide visible indications of such information (see FIG. 105C). System 4050 also is capable of imprinting special seals 4200 onto item 4054. FIGS. 106A-106C show example seals 4200. Seal 4200A shown in FIG. 106A may be the type of seal one expects from a Governmental document bearing an official seal. While it is possible for system 4050 to provide an embosser creating a raised seal 4200A, in a preferred embodiment system 4050 prints seals 4200A using a conventional monochrome or color printer at high resolution so that the seal image is flat. FIG. 106B shows an example rectangular seal 4200B in the center of the left margin of an item 4054, and another circular seal 4200C (for example, of the type that might be used in Japan) in the lower left hand corner of the document. FIG. 106C shows an item 4054 bearing two circular seals: one seal 4200D in the lower left hand corner of the page, and another circular seal 4200E in the lower right hand corner. FIGS. 106A-106C are merely illustrative examples--any desired quantity, shape or configuration of seals or other visual, machine-readable codes can be used depending upon the prevailing legal climate, the country and aesthetic considerations. FIGS. 107A and 107B show one example configuration for seal 4200. In this example, seal 4200 may include a center portion 4202, an outer portion 4204 and a border 4206. Center portion 4202 may bear a distinctive image to make the seal immediately recognizable. In this example, center portion 4202 is the great seal of the United States--and would thus be appropriate for affixing on U.S. Government official documents. Other appropriate images for seals might include, for example, a family coat of arms, a printed or holographic photograph image of the signer, a predetermined complicated pattern, or the like. Besides being distinctive, the image 4203 within center portion 4202 should preferable be complex and difficult to copy--making seal 4200 less prone to counterfeiting. Similarly, border 4206 may be an ornate pattern that might show discontinuities if printed or copied using inferior equipment. In this example, outer portion 4204 is used for encoding digital information. FIG. 107A shows an example "template" seal before this additional encoding information is added. FIG. 107B shows an example of a completed seal in which many small lines have been added to at least portions of the outer ring 4204 of the seal 4200. Appliance 600 could "complete" the FIG. 107A template seal to create a completed seal shown in FIG. 107B based on one or more electronic controls 4078. FIG. 107B also shows a close-up view illustrating that the line pattern can have variations that encode digital "bits" of information. In this particular example, lines 4208 radiating outwardly from center portion 4202 may encode a digital "1" value, while lines 4210 radiating inwardly from border 4206 may encode a digital "0" value. As another example, the selective use of large dots 4211a, small dots 4211b and no dots 4211c could encode digital values. Any kind of information (e.g., numerical, text, graphics, sound, or any combination of these) may be encoded into the image of seal 4200 using this technique. The particular line images shown in FIG. 102B are illustrative only--other visual patterns (and/or steganographic techniques) may be used to encode digital information into the seal's image. System 4050 can recover the encoded information by scanning and analyzing an image of item 4054 in either digital or printed form. In one embodiment, system 4050 can create electronic controls 4078 based at least in part on this information it obtains from seal 4200. FIG. 108 shows one example of the type of "digital signature" information that might be encoded into the seal 4200's image. In this particular example, the text and/or graphics contents of item 4054 can be transformed into a compact value using a special cryptographic function called a "one-way hash" 4212. The resulting number may be "concatenated" (i.e., put end to end) with other information such as, for example, a time value and a certificate value or number obtained from a "digital certificate" 4214. The time value may be obtained from a real time clock 528 incorporated in secure processing unit (SPU) 500 shown in FIG. 9. The resulting string of digital information may then be encrypted with the private cryptographic key of sender 4052, the contracting party 4070 and/or system 4050. The resulting digital signature value 4216 may be used to encode some or all of the seal 4200's pattern. The hash function may operate on a document in its image form, or its text equivalent (producing two different hash values). In addition, the text version of a document may be pre-processed before operation of the hash function to simplify verification of a document if it must be rekeyed into a verification system (e.g., in the case where all electronic copies of a document have been lost). Since cryptographically strong hash functions are extremely sensitive to the slightest change in data (yielding different values if, for example, a tab character is keyed as a series of spaces) this pre-processing may normalize the document by, for example, discarding all font and formatting information and//or reducing each occurrence of "whitespace" (e.g., spaces, tabs, carriage returns, etc.) into a single space. If the same pre-processing is applied to a retyped version of the document before the hash function is applied, it will have a much higher likelihood of yielding the same hash value if the documents are substantively the same. System 4050 may later recover this information by digitally and/or optically scanning the image of item 4054 and analyzing the pattern of seal 4200 to recover digital signature 4216. System 4050 may then apply the public key corresponding to the private key used to encrypt the information--thereby recovering the hash, time and digital certificate, while at the same time authenticating the information as having been encrypted with the relevant private key(s). In this example, System 4050 also has the original document image 4054 available to it, and may therefore duplicate the one-way hash process 4212 and compare the hash value it gets with the hash value encoded within seal 4200. Mismatches indicate that the seal 4200 may have been copied from another document and does not apply to the document currently being analyzed. Other types of digital identifying information that system 4050 might affix to the document include, for example: digital information generated by algorithms (such as error correcting algorithms for example) including certain kinds of unique transmittal information or certain unique pseudo-randomly generated codes that might be combined with transmittal information and/or information representing transmittal content, such that representation of such a collection of relevant transmittal related information may uniquely and reliably confirm that a given document (or other information) sent by sender 4052 is actually the exact document sent; or Reed-Solomon codes or other error correcting or other algorithms relying on formalisms within abstract algebra for establishing a correct sequence of bits; or MD4 or other message digest algorithms employing, for example, one-way hash algorithms that attempt to uniquely identify a sequence of bits that is highly sensitive to content and ordering of bits in a sequence. EXAMPLE ELECTRONIC APPLIANCE FIG. 109 shows an example detailed architecture for electronic appliance 600. In this example, appliance 600 may include one or more processors 4126 providing or supporting one or more "protected processing environments" (PPE) 650 (e.g., SPEs 503 and/or HPEs 544) shown in FIGS. 6-12 and 62-72). Protected processing environment 650 may, for example, be implemented using a secure processing unit (SPU) 500 of the type shown in FIG. 9 and/or may be based on software tamper-resistance techniques or a combination of software and hardware. As described above in detail, protected processing environment 650 provides a secure, trusted environment for storing, manipulating, executing, modifying and otherwise processing secure information such as that provided in secure electronic containers 302. In this particular example, secure containers 302 may not be opened except within a protected processing environment 650. Protected processing environment 650 is provided with the cryptographic and other information it needs to open and manipulate secure containers 302, and is tamper resistant so that an attacker cannot easily obtain and use this necessary information. Electronic appliance 600 may be any type of electronic device such as a personal computer, intelligent kiosk, set top box, or dedicated stand-alone communications appliance--just to name a few examples. Processor 4126 is connected to one or more user input devices 4106, 4118, 4140; card/media reader 4108, 4132; document reader/scanner 4114; biometric sensor(s) 4124; display 4104; document printer 4122; and, optionally, a receipt printer 4122A for printing receipts of the type shown in FIG. 92A. A document handler/destroyer 4115 may be provided to feed multi-page documents into document reader/scanner 4114 and--in one embodiment--to destroy documents to ensure that only one "original" exists at a time. Such controlled document destruction might, for example, be useful in allowing sender 4052 to deliver an original stock certificate to a transfer agent. The sender 4052 could insert the original certificate into appliance 600--which may scan the original to convert it to digital information (e.g., through use of OCR technology), confirm delivery, and then destroy the original paper version. Secure controls 4078 could be used to ensure that only a single original ever exists on paper. Processor 4126 is also connected to secure and/or insecure digital or other storage 4130 (such as, for example, magnetic disks, random access memory, optical disks, etc.), and to a communications device 666 permitting the processor to communicate electronically with other processors or devices via an electronic network 4058 (672). In one example, appliance 600 may be provided with additional and/or different components such as shown in FIGS. 7 and 8. EXAMPLE PROCESS TO SEND AN ITEM FIG. 110 shows example steps electronic appliance 600 may perform to send an item such as item 4054. Initially, electronic appliance 600 must be created or established at the user site (or the user must go to electronic appliance as shown in FIG. 88). This establishing process may include, for example: node initialization (FIGS. 64, 68, and 69), and updates (FIG. 65), locally registering any rules and controls associated with the user's rights, locally registering any rules and controls associated with any class-based rights, including, for example, any provision for integration of the item sending process into a user application (e.g., to be listed as a "printer" under a print set up in a Windows or other personal computer software application); and the establishment of any necessary certified user identities, which may include, for example, the use of a wider purpose certified identity and/or the certified use of a non-certified identity (such as some network name service identifications) or certified delegation of use of a certified identity. Once the appliance 600 has been properly initialized, the first step in a send process 4500 may be to authenticate the identity of sender 4052 (FIG. 110, block 4502). This authentication step 4502 may be performed in a variety of ways such as, for example: use of biometric sensor 4124 to provide a retinal, iris, fingerprint, thumbprint, or other scanning/matching; the use of a voice print for identity verification; hand-written signature capture and biometric analysis; requiring the user to present an identification card 4109 (which may be a smart card, magnetic card, or other storage information) that contains information about the sender's identity; capture and pattern recognition of a photographic image of the sender's face; requiring the sender to respond orally and/or via other user input devices 4106, 4118, such as keyboards or the like to provide "secret" information such as Mother's maiden name, special passwords or code words, or other information uniquely known to the sender; any combination or subcombination of these various techniques. In this particular example, the authentication step 4502 may involve an application program executing on appliance 600 requesting authentication support from protected processing environment 650--for example, sending to the protected processing environment an authentication "event" requesting the protected processing environment to authenticate the sender and providing authentication information to the protected processing environment (FIG. 110, block 4502) as a basis for the authentication. FIG. 111 shows example steps that protected processing environment 650 may perform in response to receipt of an authentication event. The example steps shown in. FIG. 111 are control set dependent--that is, that are typically based on one or more electronic control sets previously delivered to the protected processing environment 650 during the registration process described above. In this particular example, the protected processing environment 650 may examine the authentication information provided to it (e.g., the output of biometric sensors, password information, information read from an identity card, etc.) and determine (based on methods provided in one or more electronic control sets) whether it has sufficient basis to conclude with a requisite, specified degree of assurance that the sender is who she says she is (FIG. 111, decision block 4502A). Processes identified within the control sets operating within the PPE650 may perform these functions using resources provided by the PPE--providing an important degree of programmable, general purpose behavior. The nature and characteristics of this sender authentication test performed by PPE 650 may vary depending on the particular electronic control set being used--as dictated by particular applications. As discussed above, in situations that have legal significance in which non-repudiation is very important, PPE 650 may impose a relatively stringent authentication test. Other, more routine situations may use control sets that impose less stringent authenticity checks. The PPE 650 may abort the process if it decides there is insufficient information to form a trusted belief of authenticity and/or if it determines that the sender is not who she says she is (FIG. 111, block 4502B). PPE 650 may indicate/authorize that the process may continue if the authenticity check is successful (FIG. 111, "Y" exit to decision block 4502). The sender's appliance 600 may next need to identify or "register" the intended recipient(s) 4056 (FIG. 110, block 4506). In this particular example, the step of registering the intended recipient(s) involves generating a "register recipient" event and sending this event to protected processing environment 650. Upon receiving this "register recipient" event, protected processing environment 650 may--based on one or more methods within a corresponding electronic control set--perform certain steps required to coordinate its activities with the intended recipient's electronic appliance 600--including, for example, contacting the intended recipient. Example steps are shown in FIG. 112. Why might the sender's PPE 650 need to contact the recipient before sending the item? The answer is that it may be necessary or desirable for the sender 4052 and the recipient 4056 to negotiate and/or agree as to the appropriate electronic controls that should apply. In an item transmission scenario, for example, such an "agreement" might work out who is going to pay for the delivery service, which recipient appliance (home or office) the document is to be delivered to, what kind of return receipt is acceptable to both parties, etc. The PPE 650's "register recipient" event processing may, for example, allow the proposed recipient to deliver a set of controls to the sender's system that defines the parameters of receipt. Some general purpose systems may use the default settings in the kiosk or other transmission station. The address itself may provide an indication to the transmitting station as to whether it may or must request a set of control information from the recipient prior to transmission. More complicated scenarios may require further coordination. For example, an option to destroy the original item at the send end and recreate it at the recipient's end (e.g., in the case of the stock certificate mentioned earlier) is both a send option and a receipt option. Similarly, options pertaining to procedures for electronic contract execution typically will require pre-agreement from both the sender and the recipient (i.e., from all parties to the contract). In these cases, there should be some menu options that are driven by the address of the proposed recipient--and there may be an electronic (or humanly-driven) negotiation to resolve conflicts. The PPE 650's "register recipient" processing may also require input or other interaction from the user. FIGS. 90A and 90B show a relatively straightforward menu-based user interface that may be used to elicit information from sender 4052. In a more advanced example, DTDs 1108 (see FIG. 23 and following) associated with one or more load modules 1100 may be used to control user interfaces (e.g., the "pop up" as shown in FIGS. 72A-72D)). In this model, the user interface does not contain any specific visual elements (e.g., menus, buttons, data entry fields, etc.). Instead, the pop up contains application "framework" code. The framework code in this style of user interface uses a structured input stream (DTD 1108) from the PPE 650 to create the visual elements of the interface, and optionally the allowed values of certain fields. This structured data stream may (like other control structure DTDs 1108) be based on SGML, for example. This dynamic user interface approach allows control structures to be more "self describing" in the sense that application programs do not need to know ahead of time (i.e. when they are written) all of the fields, values, etc. for the structures. This gives structure designers more freedom in how their controls are designed. Given a rich enough grammar in the DTD 1108, designers needn't concern themselves with whether application programs will have the ability to manage the interaction with a user regarding their structures. This capability can also be used to create controls that support the electronic negotiation process shown for example in FIGS. 76A-76B. FIG. 112 shows example steps that may be performed by protected processing environment 650, based on one or more electronic control sets, in response to receipt of a "register recipient" event. In this example, PPE 650 first uses the dynamic user interaction discussed above to have the sender identify the proposed recipient(s) (FIG. 112, block 4503). For example, PPE 650 may request sender 4052 to provide various types of identification information corresponding to intended recipient(s) 4056 such as, for example, name; physical address; electronic address; public key; and the like. PPE 650 may check this user input for validity (decision block 4503A), and may abort the process (or perform some other exception handling routine) if the input is not valid (e.g., it falls outside of the permissible scope as defined by associated electronic controls). PPE 650 may also, at this time--with or without input from sender 4052 as may be necessary--identify any other information required for identifying recipients, such as for example, any preset template(s), class identification requirements, and/or other automation factors and/or workflow assignments, redistribution, and/or content interaction parameters. The PPE 650 then may determine whether it needs to request and obtain a control set from the recipient to proceed (FIG. 112, decision block 4506A). The PPE 650 may have obtained the required control set(s) during a previous transaction; the sender may supply the required control set, or the PPE may in some cases be able to use a "default" control set it already has so that no additional control set might be required ("N" exit to decision block 4506A, FIG. 112)--and send processing may proceed to the next step. On the other hand, if PPE 650 must get a recipient's control set (FIG. 112, "Y" exit to decision block 4506A), the PPE 650 may contact the intended recipient's electronic appliance 600 and/or a control set archive (FIG. 112, block 4506B) over network 672 for example. PPE 650 may employ secure directory/name services as shown in FIG. 12 (and/or as described in the above-reference Shear et al. patent disclosure) to obtain sufficient information for sending and addressing the item to the intended recipient(s) 4056. Once PPE 650 determines how to contact the recipient, it may construct an administrative object 870 (see FIG. 21) requesting the appropriate recipient controls (FIG. 112, block 4506C), and send the administrative object to the recipient's PPE 650 or other appropriate VDE node that can supply the information (FIG. 112, block 4506D). The PPE 650 within the recipient's electronic appliance 600 or other responding VDE node may process administrative object 870 upon receiving it (FIG. 112 block 4506E)--constructing a response (e.g., a responsive administrative object containing the requested or require control sets) (FIG. 112 block 4506G) and sending it to the sender's PPE 650. The sender's PPE 650 may register the received controls (FIG. 112, block 4506H) upon receiving them from the recipient's PPE 650. The sender's PPE 650 may then determine, based on the received controls, whether it can continue (FIG. 112, decision block 4506I). If there is a problem with the controls (e.g., they are for some reason unacceptable to the sender, they are not valid, etc.), the sender's PPE 650 determines whether the problem is critical (FIG. 112, decision block 4506J). If the problem is critical, PPE 650 aborts the whole process ("Y" exit to FIG. 112 decision block 4506J). If the problem is not critical ("N" exit to FIG. 112 decision block 4506J), PPE 650 performs an exception process (FIG. 112, decision block 4506L) to handle the problem and then waits for the next event--which in this particular example may be a "generate secure object" event (see FIG. 110, block 4512). FIG. 113 shows example steps the PPE 650 may perform in response to this "create secure object" event based on the control sets registered in accordance with step 4506, for example. Referring to FIG. 113, the PPE 650 may use the dynamic user interaction techniques described above to request sender 4052 to select between send options and to otherwise specify the type and level of service he or she desires (FIG. 113 block 4512A; see FIG. 91A block 4090A). Generally, sender 4052 may be required to select between various options; each option may carry with it a certain price. The following are example options the sender 4052 may select from: Document Options Signature Options a. digital b. visual c. both Seal options a. visual b. hidden (steganographic) c. both Seal options a. Insert third party seal b. Complete sender seal c. Provide handwritten signature d. Provide steganographic electronic fingerprint e. Provide visual electronic fingerprint Privacy/Use Options a. modify/no modify b. partial disclosure Item Destruction Option a) destroy paper original b) destroy digital "original" Delivery Options Receipt Options a) receipt to send b) receipt to sender and trusted go-between c) receipt to trusted go-between d) no receipt requested Integrity Guarantee Options a) no modifications permitted (final version, for example) b) no modifications other than signing permitted c) no cut, paste, exerpting permitted d) other document (item) controls Privacy Options a) public transaction b) authorization list c) direct parties to transaction (sender, receiver, etc.) d) direct parties plus transaction authorities (see Shear et al.) Authentication Options a) type and/or "strength" of recipient authentications (e.g., biometric, password, other) b) strength requirement Delivery Type a) direct delivery b) store and forward c) permit proxy delivery (registered or certified) Contract Execution Options send offer a) single recipient b) multiple recipients send acceptance propose modification add comments negotiate (with our without saving negotiation history) execute contract degree/type of non-repudiation evidence required Teleconferencing Options Name of party Address of party (if known) Secure directory lookup (if address unknown) Quality (speed) of connection Payment methods (if different for teleconference) Advanced options Teleconference protocol Teleconference network carrier Trusted Go-Between Options Contract settlement options Audit options Archival options a) archive digital "original" b) archive "sent" audit record c) archive "received" audit record d) archive negotiation history audit record(s) Notary options a) notarize digital "original" b) notarize sub-sections of digital "original" c) notarize "sent" audit record d) notarize "received" audit record e) notarize negotiation history audit record(s) Negotiations a) Automated negotiations enabled (yes/no) b) Specific human go-between (if yes, who) Length of time to store records (days, months, years, forever) Contents inaccessible to trusted-go-between (automated service only) Payment methods a) Mastercard b) Visa c) American Express d) ACH e) EDI X.12 f) other In the dynamic user interface model, for example, the user options associated with a contract offer (which are used to create electronic controls associated with the electronic transaction) might relate to a suggested addition, modification, deletion, etc. to an existing item 4054. If the VDE-aware applications used by the participants included word processing capabilities (given that the negotiation has a text based portion), for example, the VDE protected content in the offer could be represented as a "redline" or "revision marking." The controls could further include aspects that manage modification of content in a controlled way (e.g., see FIG. 51, and FIGS. 51a-f). A more complex example might include several of these modifications, insertions, deletions, etc. in a single offer to represent a "horse trading" offer indicating a willingness to, make a series of changes at once, for example, a willingness to pay more money in exchange for removing a restrictive clause. The options (and associated controls) associated with a contractual offer may also permit the offerer and/or the recipient to add comments to the offer before it is sent and/or accepted. These comments and/or some or all of the negotiation history may be recorded and managed using the audit capabilities of VDE and/or one or more repositories for VDE objects. In this example, the PPE 650 checks the user input for validity (FIG. 113, decision block 4512B) based on applicable controls, and may abort the process (or provide other suitable exception handling) if the input is not valid. PPE 650 may next specify any audit and routine controls based on the user input it has received and/or the recipient controls it has registered (FIG. 113, block 4512C). As mentioned above, object 300 may include one or more control sets 4073 (contained in one or more PERCs 306 for example) that specify the type of routing and auditing to be performed in connection with sending an item 4054 (and also providing one or more control methods for use in auditing and/or routing. Step 4512C typically also involve creating electronic controls specifying permissions and/or restrictions relating to the use of item 4054. In fact, the electronic control set(s) 4078 created by block 4512C may, for example, specify a variety of different document delivery or other characteristics such as, for example: document delivery options selected by sender 4052; authentication requirements applicable to intended recipient(s) 4056; what use, if any, is to be made of a third part electronic go-between 4700 and what the third party electronic go-between is authorized to do and is restricted from doing; other document flow requirements such as direct, pass through or round robin (interactive); applicable payment methods; restrictions concerning use of the document (e.g., whether or not the document can be modified, whether or not the document can be passed along to another party, other restrictions concerning document use and/or privacy); and other item chain of handling and/or control restrictions. Control set 4078 can be used to enforce a secure chain of handling and control on document container 302 and/or its contents. This secure chain of handling and control may be used, for example, to specify delivery, routing, auditing or other parameters as discussed above. In performing step 4512, appliance 600 may also create routing slip 4072 (see FIG. 103) and a template for return receipt(s) 4066. In one example, items 4066, 4072, may be embodied within electronic control set 4078 and expressed by the various elements within the electronic control set. FIG. 113A shows an example of a routing slip 4072 data structure that may be maintained within secure electronic container 302 (e.g., as one or more DTDs 1108 in connection with one or more load modules 1100--see FIG. 3). This routing slip data structure 4072 may include, for example: a transaction ID field 4520; a sender ID field 4522; a recipient 1 ID and node ID field 4524 (1), 4526 (1), respectively, and a corresponding recipient receipt information field 4527(1); a recipient 2 ID and node ID field 4524 (2), 4526 (2), respectively, and a corresponding recipient receipt information field 4527(2); a recipient N ID and node ID field 4524 (N), 4526 (N), respectively, and a corresponding recipient receipt information field 4527(N); communication/routing information 4528; exception list 4529; and/or other information 4530. Exception list 4529 may indicate "named exceptions" (e.g., communications failure, line busy, refused receipt, refused payment request, etc.) paired with a list of responses (e.g., try again, cancel entire transaction, send report, invoke event in PPE) and data parameterizing the responses (e.g., number of retries, list of recipients of cancellation notices, report recipients, control information identifier and additional parameters for control use and/or invocation; respectively). Recipient receipt information field 4527 for each recipient may indicate, for example, the nature of the receipt required, and the recipients of that receipt. A receipt "template" may be included in the container, may be referenced in an archive, or may be named out of a set of default templates stored in each appliance. The routing slip 4072 (see FIG. 103) associated with the document(s) in the container may be integrated with control information 4078 reflecting chain of handling and control relationships among recipients. For example, the control information 4078 associated with the item(s) 4054 may be correlated with fields of the routing slip 4072. Successful completion of a receipt may qualify a specific user to become eligible to use a subset of the control information 4078 that permits them to make changes in a portion of the item, and describe their own control information for the changes, so long as this control information, does not provide further recipients with the right to modify the new material. The control information 4078 may further specify that no changes may be made to an item 4054 until one or more specified recipients has read the item, and (through use of reciprocal controls as show in FIGS. 41a-41d for example) indicated their approval of further changes. In another example, an entire class of users may be permitted to access the documents (through the presence of a certificate indicating their membership in a class, for example), and the routing slip 4072 may be used to record who has handled a particular version of the document. Through use of chain of handling and control techniques, the presence of certain users on the routing slip may permit further control information to be specified by a user. For example, after an analyst's research report has been reviewed by three other analysts, a manager may be permitted to modify the control information associated with the report to permit transmission to "public" users. Electronic controls 4077 may also include one or more control methods specifying the type of audit information that is to be maintained in connection with the electronic transaction. This audit information may be used for constructing a receipt 4066, to provide evidence preventing repudiation, and for a variety of other functions. Such audit information may be maintained exclusively within the sender's appliance 600, it might be maintained exclusively within the recipient's appliance secure database, it might be maintained exclusively within the trusted go-between 4700's appliance 600 secure database, or it might be maintained in a combination of any or all of these. Additionally, the audit information may or may not be delivered with item 4054 depending on the particular objectives. A usage clearinghouse 200c as described above in connection with FIG. 1A and/or as disclosed in the Shear et al. patent disclosure may be used to track the audit information based on event-driven or periodic reporting, for example. Audit records could be transmitted to a usage clearinghouse (or to a trusted go-between 4700) by an automatic call forwarding transmission, by a supplemental call during transmission, by period update of audit information, by the maintenance of a constant communication line or open network pathway, etc. FIG. 113B shows an example of secure audit information 4077 that may be maintained under the control of one example set of electronic controls 4078. This audit information may include, for example: a transaction identifier 4532; sender identifier 4534 identifying sender 4052; an identifier 4536 identifying the location (e.g., node) of sender 4052; an identifier 4538 of recipient 4056; an identifier 4540 specifying the location (e.g., node ID) of the intended recipient 4056; an identifier 4542 of the document or other item being sent; a secure document descriptor (e.g., a one-way hash value produced from the document's contents); other document information 4546 (e.g., format and/or size); document delivery options 4548; cost/payment information 4550; time/date the item the item was sent (field 4552); time/date stamp 4554 of document receipt; identification of who opened the document (field 4556); a time stamp identifying the location/node date and time of document opening (4558); and other information 4560. As mentioned above, audit information 4077 associated with use of a document may be transmitted to many different parties. Audit information 4077 may also be treated as part of the signaling methodology described for reciprocal methods (see FIGS. 41a-41d) to provide receipts. For example, copies of receipts may be delivered to the sender, as described above, as well as to the sender's manager in a corporate setting, or to the sender's legal counsel or other professional advisors (such as tax advisers, accountants, physicians, etc.) Some items 4054 which are delivered to, or used by, recipients to gather information (such as tax forms, purchase orders, sales reports, and insurance claims) may require delivery of receipts to several parties other than the sender. Some transactions may require the delivery of such receipts before completion. For example, a sales report requesting delivery of products from a company's inventory may require that a receipt from the reading of a document delivered to the sales organization be received by the accounting department for audit purposes before permitting receipt of the document by the sales organization. Referring once again to FIG. 113, electronic appliance 600 may next request authority from sender 4052 to obtain payment for delivery of the item (FIG. 110, block 4505; FIG. 113, block 4512D). Payment may be by any convenient mechanism, and may be made by the sender, the recipient and/or by a third party. This payment processing in this example is handled by PPE 650 in accordance, for example, with one or more billing methods as shown in FIG. 49D for example. The appliance 600 is then ready to accept item 4054 (such as a document) to be sent if the item hasn't already been inputted (FIG. 110, block 4507; FIG. 113 block 4512E). PPE 650 may (based on control sets specifying this) use the dynamic user interaction technique described above to interact with the sender 4052 and obtain the requested item for transmission. As mentioned above, for physical documents, appliance 600 can optically scan the document into electronically readable form employing document reader/scanner 4114 using page reader technology and/or optical character recognition, for example. For electronic documents or other items such as those created by a personal computer 4116 (see FIG. 95), this "inputting" step may be a matter of having sender 4054 select or create the item using standard document or file creation applications, or physically picking such document using icons or other menu-driven techniques. In one particular example, sender 4052 may "select" a document or item to send by commanding a word processing or other application to "print" or otherwise write the item to a particular virtual printer or other, output device which is mapped into the overall secure electronic delivery process. Appliance 600 may store the item in any of multiple representations. For example, it could store it in Adobe Acrobat (PDF) or other text based page description. Storing the document in CCIT Group III Facsimile format is an example of a "universal" image format for black and white images. Group V is an example of a color format. TIFF is another example that incorporates many image types, as well as different compression formats and descriptive metadata. PPE 650 may perform various tests on the inputted item and/or other results of the user interaction provided by block 4512E in accordance with one or more user controls. For example, if the sender has specified that he is sending a 6 page letter but only inputs five pages, PPE 650 may notice this discrepancy and notify the sender (FIG. 113, decision block 4512F). PPE 650 may abort the process or perform other suitable exception handling ("N" exit to decision block 4512F) if the results of the test are not satisfactory. PPE 650 may embed any seals 4200, signatures 4300 or hidden signatures 4400 into the item if needed (FIG. 105, block 4510). This process may involve, for example, identifying signature insertion locations and embedding signatures upon directed or other controlled circumstances. "Intelligent" optical character recognition (OCR) may be used to identify signature locations. The display might also show an image of the page and allow the operator to identify the signature locations, for themselves, or more importantly, for other parties. The PDF (or other document description format) expressions could be extended to include a code that would allow indication of signature insertion points. Depending upon the particular electronic controls being used, placement of the sender's signature or seal on the document may be based on the PPE 650's authentication of the sender as shown in FIG. 111--and may require an additional indication of assent from the sender--for example, pressing a "Yes" button, providing additional biometric or other identification information (e.g., "place your finger on the sensor if you want to sign this letter" or "Provide your mother's maiden name to sign this letter"). Such authentication is important for non-repudiation and to prevent fraud. The sender might actually sign his signature on a pressure-sensitive or magnetic-sensing signature capture and/or verification pad, provide a bit-map image of his signature by presenting a "smart card" storing it (plus using appropriate authentication techniques to assure that the bitmap image is being presented by the true signature owner), or provide enough information through user interaction as described above that the PPE 650 can access an electronic signature file containing the signature (e.g., stored locally within appliance 600 or accessible over network 672 from an archive). In the multi-party execution example shown in FIGS. 97 & 98, appliance 600 could simultaneously embed two or more signatures into the same document or other item 4054--but only upon securely receiving indications that all signatories assent to the document's terms. Appliance 600 may next place the item and associated electronic controls into one or more secure containers 302 (FIG. 113, block 4512H). Referring to FIG. 103 once again, step 4512 normally involves placing the image 4068I of item 4054 (including any seats, signatures and other information) into the secure container 302. It may also involve placing a data (e.g., text) version of the item 4068D into the same or different container 302, along with possibly adding tools 4074 for using the item in either or both forms. The PPE 650 may then send the completed object 300 to an object switch 734 (see FIG. 12) for transmission to the recipient. Referring to FIG. 110, appliance 600 may then deliver the secure container(s) 302 to the intended recipient 4056 and/or to trusted electronic go-between 4700 based upon the instructions of sender 4052 as now reflected in the electronic controls 4078 associated with the object 300 (FIG. 110, block 4514). Such delivery is preferably by way of electronic network 4058 (672), but may be performed by any convenient electronic means such as, for example, Internet, Electronic Mail or Electronic Mail Attachment, WEB Page Direct, Telephone, floppy disks, bar codes in a fax transmission, filled ovals on a form delivered through physical mail, or any other electronic means to provide contact with the intended recipient(s). Appliance 600 may, through further interaction with PPE 650, immediately and/or later provide a receipt such as shown in FIG. 89A (FIG. 110, block 4516). Appliance 600 can immediately issue a receipt indicating that the object 300 has been sent. If rapid electronic communications means are being used, appliance 600 may also receive audit trail information from the recipient's appliance 600 while the sender waits, and issue a receipt indicating some or all of the kind of recipient interaction information shown in the FIG. 92A example receipt. This receipt providing step may, for example, be based on PPE 650 receiving one or more administrative or other objects 300 containing audit information (see FIG. 113B). For purposes of security and trustedness, PPE 650 may actually "issue" the receipt--although it may use various other portions of appliance 600 (e.g., receipt printer 412A, display 4104, card/media reader 4108, 4132, etc.) to output the receipt to the sender 4052. PPE 650 may also or alternatively maintain a copy of the receipt information (and/or the audit information 4077 on which it is based) within its secure database 610 (see FIG. 16). The trusted go-between 4700 similarly may maintain a copy of the receipt information (and/or the audit information 4077 on which it is based) within a secure electronic archive 4702. EXAMPLE RECEIVE PROCESS FIGS. 114A and 114B show an example process 4600 for receiving an item. In this example, electronic appliance 600 that has received an electronic object 300 may first generate a notification to PPE 650 that the container has arrived (FIG. 114A, block 4602). PPE 650 may, in response, use the dynamic user interaction techniques discussed above to interact with and authenticate the recipient in accordance with the electronic controls 4078 within the received object 300 (FIG. 114A block 4603; authentication routine shown in FIG. 111). Intended recipient 4056 may be given an option of accepting or declining delivery of the object (FIG. 114A, block 4604). If intended recipient 4056 accepts the item, appliance may store the container 302 locally (FIG. 114A, block 4606) and then generate a "register object" event for processing by PPE 650. FIG. 115 shows example steps that PPE 650 may perform in response to a "register object" event. In this particular example, PPE 650 may generate and send any return receipt to sender 4052, trusted electronic go-between 4700, or other parties as required by the control set 4078 within container 302 (FIG. 115, block 4607A)--by for example recording audit records 4077 and transmitting them within an administrative object(s) 870 to the required appliances 600. Appliance 600 may next, if necessary, obtain and locally register any methods, controls or other information required to manipulate object 300 or its contents (FIG. 115, block 4607B; see registration method shown in FIGS. 43a-d). For example, item 4054 may be delivered independently of an associated control set 4078, where the control set may only be partial, such that appliance 600 may require additional controls from permissioning agent 200f (see FIG. 1A and "rights and permissions clearing house" description in the copending Shear et al. patent disclosure) or other archive in order to use the item. PPE 650 may next securely authenticate the received item to ensure that it is not a counterfeit (FIG. 115, block 4607C). For example, appliance 600 may check one or more digital signatures 4076 within container 302 to ensure that they are authentic, or perform other authentication tests as described in detail above. PPE 650 may perform critical and/or non-critical exception processing (not shown) if the received object 300 and its contents are not authentic. PPE 600 may analyze any seal or other secure information that is part of the item 4054. For example, although the item image may be captured and cropped by untrusted processes, the analysis of the image data is preferably done inside the PPE 650. Once the seal option of the image is identified, an analysis process will be run to recover the digital information stored in the seal (or steganographically encoded in the document). The next step is to determine what the expected values should be. To do this, the PPE 650 may make requests of an application program running locally to determine a user's expectations, may use a digital representation of a receipt or other audit data, and/or may contact a trusted go-between or other trusted third party to obtain the appropriate expected values. To facilitate this process, there may be some unencrypted information in the seal that can be used to establish a correlation with other information (e.g., a receipt, a transaction number, etc.). If such information is not available, a local store or a trusted third party might compare the entirety of the recovered digital information with stored records to determine such a correlation. In other cases, the expected values may be determined from context (e.g. a default set of expected values; or by examining the seal information itself, in either encrypted or decrypted form, for "tags" or other schema or semantic information). Once the expectation values of the information is determined, any encrypted portion must be decrypted using the public key corresponding to the private key used above to make the seal. This key can be obtained using the mechanisms discussed in Ginter et al. Once decrypted, the expected values may be compared with the actual values to determine correlation. Information about the correlation may be reported to a user and/or a third party, as appropriate. In addition, some or all of the seal information may be included in such report. Once PPE 650 is satisfied that the received item is authentic, it may embed receipt related information into the item if the electronic controls 4078 associated with the item require it (FIG. 115, block 4607D). In one example, the "electronic fingerprinting" techniques described above in connection with FIGS. 58B and 58C may be used for encoding various types of information onto item 4054--for example, to show where the document has been. PPE 650 may embed seals 4200 and/or hidden information 4400 onto the item image 40681 at this time if desired. Electronic fingerprinting, sealing and embedding hidden information may also be performed by the PPE 650 at the sender's 4052 site--but, it may be advantageous to delay this process until the item arrives at the recipient's site because more things have happened to the item by then. For example, it may be desirable to encode, into seal 4200, hidden information 4400 and/or hidden or unhidden electronic fingerprinting and/or watermarking information, the time stamp of when the recipient actually opened the container 302. In some arrangements, one seal, hidden signature or hidden or unhidden electronic fingerprint could be added at the end of sender 4052, and an additional seal, piece of hidden information and/or hidden or visible electronic fingerprint could be added at the end of recipient 4056. Any or all of these various techniques may be used depending upon business requirements, convenience, logistics and aesthetics. PPE 650 may next perform any required payment and/or other processing as needed (FIG. 115, block 4607E). For example, PPE 650 may charge the recipient 405.6 for receiving the document (e.g., "collect on delivery") or it may perform other processing such as debiting, crediting, initiating a local audit, round robin pass along, or the like--all as specified for example by electronic controls 4078. Referring again to FIG. 114A, appliance 600 may next index or otherwise catalog item 4054 for later access and reference (FIG. 114A, block 4618), and may automatically identify document/file format for storage or presentation to recipient 4056 (FIG. 114A, block 4620). Appliance 600 may then select any additional information necessary to allow the recipient 4056 to interact with the document (e.g., conduct any associated database searches or the like) (FIG. 114B, block 4622), and then initiate any associated application(s) and any carrier application required to interact with the document/file (FIG. 114B, block 4624). Appliance 600 may then generate a "send" or "open" event to PPE 650 requesting the PPE to open container 302 and allow the user to access its contents. FIG. 116 shows example steps that may be performed by PPE 650 in response to an "open" or "view" event. In this example, PPE 650 may--upon allowing recipient 4056 to actually interact with the item 4054--embed additional recipient interaction related information into the document such as, for example, the time the recipient actually looked at the document (FIG. 115, block 4625A). PPE 650 can at this time also send additional audit and, or return receipt information to the sender 4052 indicating this event (FIG. 116, block 4625B) if the associated electronic controls 4078 require it. PPE 650 may then release the image 4068I and/or the data 4068D to the application running on electronic appliance 600--electronic fingerprinting or watermarking the released content if appropriate (FIG. 116, block 4625C). Referring again to FIG. 114B, appliance 600 may then wait for further instructions from the recipient 4056. If the recipient wishes (and is permitted by controls 4078) to print the item 4054 (FIG. 114B, decision block 4628), appliance 600 may send a "print" event to PPE 650. FIG. 117 shows example steps PPE 650 may perform in response to such a "print" event. In this example, the PPE 650 may print the item using a suitable printer 4122, including (if necessary or desirable) a certifying seal 4200 and/or other markings on each page of the document (FIG. 117, block 4630A). If recipient 4056 wants to redistribute the item to another person (FIG. 114B, decision block 4632), appliance 600 may generate a "distribute" event to PPE 650. FIG. 118 shows example steps PPE 650 may perform in response to such as "distribute" event. If the electronic control set 4078 associated with the item 4054 permits redistribution, PPE 650 and appliance 600 may redistribute the item within a secure container(s) 302 based on the conditions set forth in the applicable control set. For example, the control set may specify that item 4054 is to be "electronic fingerprinted" to indicate that recipient 4056 has received and looked at it (FIG. 118, block 4634A). Other information that may be embedded into the document at this time could include, for example, information related to the retransmittal such as, for example, name of sender(s), name of recipient(s), location of sender(s), location of recipient(s), employer(s) of sender(s) and/or recipient(s), and/or any other identifying information. PPE 650 may then package all required information within the same or different electronic container 302 and release the completed object(s) 300 to appliance 600 for transport using electronic or other communications means (FIG. 1118, block 4634B). PPE 650 may, if required by controls 4078, also send an administrative object 870 providing additional audit and/or receipt information to the sender 4052 indicating that the item has been passed on to the next intended recipient(s) (FIG. 118, block 4634C). EXAMPLE TRUSTED ELECTRONIC GO-BETWEEN DETAILED ARCHITECTURE AND OPERATION In addition to the secure archive, witnessing and transaction management functions discussed above, trusted electronic go-between 4700 may perform additional services, such as, for example: notary services; provide an electronic trading environment allowing multiple parties to electronically auction goods or services; "clearing" transaction details, such as, payments, audit information and the like; acting as a "certifying authority" (see Shear et al. patent disclosure) by issuing digital certificates 4064; provide any or all of the various support and administrative services described in the Shear et al. patent disclosure; act as a trusted registry for electronic control sets; provide electronic or human arbitration, mediation or negotiation services to facilitate formation of agreements or electronic contracts; provide legal, accounting, architectural, design or other professional services; provide document assembly services; provide document disassembly and component distribution services; provide real estate, commercial or other closing or settlement services; provide court document docketing, filing or other services to assist a judiciary; provide document registry certification, witnessing and other services to assist a judge in ruling on the admissibility of evidence in a court of law; provide tax filing services including income tax form preparation, payment handling and the like; assist in communications between co-counsel, inside and outside corporate counsel, and/or opposing counsel; deliver highly confidential information critical to national security interests; international commerce and management of complicated international commercial transactions; stock and bond trading and/or brokerage; managing and/or coordinating internal organizational functions (e.g., corporate, government); provide currency conversion and arbitrage services; provide arbitrage services related to equity, bonds, options, and other financial instruments provide equity, bond, currency, options and other financial instruments trading, authentication, non-repudiation, transfer agent, and related administrative and/or support services; creation, execution, interface with, and use of "smart agents" as described in the co-pending Ginter et al., application (see FIG. 73). The trusted electronic go-between 4700 may comprise or include a "transaction authority" as disclosed in the above-referenced Shear et al. patent disclosure, and may have the same structure and architecture as shown in FIG. 55 et seq. of that co-pending application. The trusted electronic go-between 4700 may be one computer or many. It may be centralized or distributed. It may be public or private. It may be self-sufficient, or it may operate in conjunction with other go-betweens or other support services. It may be entirely automatic, or it may include functions and tasks that must be performed using human skills and expertise. It could be owned by a corporation or other organization, or it could be a cooperative. It could charge for its services, or it might offer its services free of charge. As illustrated in FIGS. 119-120B, the trusted go-between 4700 may use reciprocal methods and distributed processing (see FIG. 41a and following) to perform its tasks. For example, the trusted go-between 4700 could actually be a group of organizations (e.g., a "trusted go-between" and a notary public) that each provide an aspect of the overall function. For example, a certifying authority, a governmental regulator, and an arbitrator could provide the trusted go-between function with the arbitrator acting as the "front end" (i.e. appearing as "the" trusted go-between from the participants' point of view). Alternatively, all three of these parties may each play a role as independent trusted go-betweens (with the cost of more complex control structures, and all three parties requiring some level of coordination by one or more of the other participants to the extent their functions relate to the same subject matter). In another trusted go-between topology, each of the participants could have one or more trusted intermediaries that interact with each other on behalf of the participants. FIG. 119 shows an example architecture for a trusted go-between 4700 that provides notarization functions. In this example, trusted go-between 4700 may include an electronic appliance 600 providing one or more protected processing environments 650 and a secure electronic archive 4072. In this example, electronic appliance 600 may include a server 4710 that communicates with protected processing environment 650 and supports one or more administrative applications 4712. Server 4710 may, in turn, communicate with additional electronic appliances 600B including associated protected processing environments 650B. In this specific example, additional electronic appliance 600B may be owned and/or operated by an entity having the legal authority to be an electronic notary public. The notary public protected processing environment 650B may execute a control set 914B relating to notary functions. Control set 914B in this example, has a reciprocal relationship between an overall control set 914A executed by a protected processing environment 650A of electronic appliance 600A. As shown in FIG. 120A, a notary protected processing environment 650B may originate both parts of reciprocal control sets, and deliver one half 914A for operation by appliance 600A--or electronic appliance 600A could originate both parts and deliver part 914B to the notary electronic appliance 600B. The illustrated reciprocal control sets 914A, 914B may reciprocally interact as described above in connection with FIG. 41A-41D, for example. FIG. 120B shows example reciprocal methods 1000 that might be contained within an example pair of reciprocal control sets 914A, 914B. In this specific example, the control set 914B operated by the notary protected processing environment 650B may include, for example, the following methods 1000: respond initialize request certificate reply certificate validate certificate request "get document" reply "get document" calculate hash and other parameters make seal modify document request "send document" reply "send document" store document into secure database 610. Similarly, the reciprocal control set 914A operated by electronic appliance protected processing environment 650A may include-methods 1000 responding to reciprocal events, such as, for example: request initialize reply initialize response certificate response "get document" response "send document" additional reciprocal methods The control sets 914B, 914A thus define and control the processing which go-between 4700 performs on documents and other items in order to notarize them. Human users may interact with this process if desired through optional user interfaces 4714, 4716. Such human intervention may be required under certain circumstances (for example, if a live human witness might be required to testify as to certain notarization facts, if the automatic processes determine that a fraud is being attempted, etc.). The dynamic interface technology described above can provide a mechanism for delivering a user interface through the system without direct intervention by the provider of the overall service with respect to user interface, and by the notary with respect to the customer relationship. EXAMPLE TRUSTED GO-BETWEEN PROCESS UPON ITEM RECEIPT FIG. 121 shows an example process 4750 that may be performed by a trusted electronic go-between 4700 in the FIG. 100 scenario shown-above. In this example, the trusted electronic go-between 4700 receives notification that the electronic container 302 has arrived (FIG. 121, block 4752), may store the container locally (FIG. 121, block 4754), and opens and authenticates the container and its contents (FIG. 121, block 4756). The trusted electronic go-between 4700 may then, if necessary, obtain and locally register any method/rules required to interact with secure container 302 (FIG. 121, block 4758). The trusted electronic go-between automatically accesses and identifies any controls indicating processing options (FIG. 121, block 4759), and may generate any audit trails or other notification(s) that the container has arrived (FIG. 121, block 4760). The trusted electronic go-between 4700 may then optionally archive the electronic container (and/or transmission related data) locally (FIG. 121, block 4761)--according to specific options chosen by the sender or other participant and/or the default processing options of the trusted go-between (in one example, all containers and their contents may be stored for five years unless processing options were chosen to the contrary). The trusted electronic go-between 4700 may perform further processes as required by associated electronic controls (FIG. 121, block 4764). The trusted electronic go-between 4700 may, if necessary, redistribute the container to the next recipient (FIG. 121, block 4766), and may then notify the sender 4052 or other parties of the actions taken (FIG. 121, block 4766). Trusted electronic go-between 4700 may also archive transmission related data as determined by the electronic control set 4078 associated with the item 4054 being sent, the transaction type and/or sender and/or recipient information (FIG. 121, block 4760). For example, trusted electronic go-between 4700 might automatically determine archiving requirements based at least in part on certified class based identification information regarding sender 4052 and/or recipient 4056. In one example, trusted electronic go-between 4700 archives transmittal related information such as receipt data structure 4066 in an object oriented database employing secure containers 302. It may also perform data reduction analysis and/or authentication processes (FIG. 121, block 4762) to provide client specific, class and/or transaction type usage analysis. Trusted electronic go-between 4700 may next further process the received item 4054 in accordance with requirements provided by electronic control set 4078 (FIG. 121, block 4764). For example, the trusted electronic go-between 4700 might perform an integrity check on the item, or it may notarize the item before archiving it. Other processes that might be performed by trusted electronic go-between 4700, depending on the particular scenario, include for example the following non-exhaustive list of functions and/or operations: Applying signatures (digital, visual, or both) Applying seals (visual, hidden, steganographic) Inserting a third party seal Completing a sender seal Providing a handwritten signature Providing a steganographic electronic fingerprint Providing a visual electronic fingerprint Determining Privacy/Use Controls (e.g,. modify/no modify and/or partial disclosure, recording public transactions, permitting disclosure only to those on authorization lists) Issuing receipts (e.g, to sender) Integrity Guarantees (e.g., no modifications permitted, no modifications other than signing permitted, no cut, paste, excerpting permitted) Contract execution functions such as: send offer to single and/or multiple recipients, send acceptance propose modification add comments negotiate (with our without saving negotiation history) execute contract degree/type of non-repudiation evidence required Teleconferencing options such as use of secure directory lookup (if address unknown), quality (speed) of connection, payment handling, and advanced options Audit functions Contract Settlement functions Archival functions such as archive digital "original" archive "sent" audit record archive "received" audit record archive negotiation history audit record(s) Length of time to store records (days, months, years, forever) Contents inaccessible to trusted-go-between (automated service only) Notary functions, for example: notarize digital "original" notarize sub-sections of digital "original" notarize "sent" audit record notarize "received" audit record notarize negotiation history audit record(s) Electronic negotiation functions, for example: Automated negotiations enabled (yes/no) Specific human go-between (if yes, who) Payment handling, for example: Mastercard Visa American Express ACH EDI X.12 other As part of this processing, trusted electronic go-between 4700 may, if necessary, redistribute the electronic container 302 to the intended recipient 4056 (FIG. 121, block 4766). EXAMPLE TRISTED GO-BETWEEN PROCESS TO ARCHIVE AND REDISTRIBUTE AN ITEM FIG. 122 shows an example process 4770 performed by trusted go-between 4700 to archive and redistribute an item 4054. In this example process 4770, the trusted go-between 4700 receives notification that an object 300 (e.g., a container 302 containing an item(s) 4054) has arrived (FIG. 122, block 4772). Trusted go-between 4700 may store the object 300 into its secure archive 4702 (FIG. 122, block 4774). It may then open the container 302 and authenticate its contents (FIG. 122 block 4776). If necessary, trusted go-between 4700 may obtain and register any methods, rules and/or controls it needs to use or manipulate the object 300 and/or its contents (FIG. 122 block 4778). Unless it already has the required permission to redistribute the object 300 (e.g., based on controls within the object's container 302), trusted go-between 4700 may need to request permission to redistribute (FIG. 122, block 4780). Trusted go-between 4770 may test to determine whether it has the required permissions (FIG. 122, decision block 4782)--and request them from the appropriate-party or parties if necessary. If trusted go-between 4700 is unable to obtain the necessary additional permissions ("no" exit to decision block 4782, FIG. 122), the trusted go-between may send a failure notification (FIG. 122, block 4784) and may archive the requests, replies and audit records (FIG. 122, block 4786). If, on the other hand, trusted go-between 4700 has the necessary permission(s) to redistribute the received object 300 ("yes" exit to decision block 4782, FIG. 122), the trusted go-between may affix one or more new seals 4200 to the item(s) 4068 (FIG. 122, block 4788), and may then send the sealed copies within secure containers 302 to the appropriate recipient(s) (FIG. 122, block 4790). Trusted go-between 4700 may perform appropriate payment processing (FIG. 122, block 4792), and may optionally provide appropriate return receipts as required by the controls associated with the object 300 (FIG. 122, block 4794). EXAMPLE PROCESS FOR TRUSTED GO-BETWEEN TO PROVIDE AN ITEM FROM ITS SECURE ARCHIVES In most instances, retrieving archived data requires a user to authenticate themselves, and present information identifying the container. Some containers may require more than one party to retrieve data (e.g., both the recipient and the sender), in most cases a user who is not party to the transaction cannot retrieve data (an exception could be a government authority, such as a court or tax auditor). In one interesting case, all electronic copies have been lost or were never stored (presumably, the archive only contains transaction information and a hash value). FIG. 123 shows an example process 4800 for trusted electronic go-between 4700 to provide items 4068 it has archived within secure archive 4702 to an appropriate authorized party (such as, for example, one of the owner(s) of the item or a court of law). In this example, trusted go-between 4700 may receive notification of the arrival of an object 300 requesting a particular item 4068 the trusted go-between previously archived within its secure archive 4702 (FIG. 123, block 4802). The trusted go-between 4700 may store the received object (block 4804, FIG. 123), and may open and authenticate the object (FIG. 123, block 4806). The trusted go-between 4700 may obtain and register any necessary controls it requires to fulfill the request (FIG. 123, block 4808). In this example, the trusted go-between 4700 may authenticate the received request, and in the process may also satisfy itself that the requester has authorization to make the request (FIG. 123, blocks 4810, 4812). This authentication process provides assurance that the request is authentic and has come from a party with authorization to obtain the requested information (for example, a court of competent jurisdiction). Assuming the request and requestor are both authentic, trusted go-between 4700 may access the requested item(s) from its secure archive 4702(FIG. 123, block 4814). Trusted go-between 4700 may affix one or more appropriate seals 4200 to the item(s) (FIG. 123, block 4816), and then send the sealed copy(s) of the item(s) to the requester (FIG. 123, block 4818). In this example, trusted go-between 4700 may optionally notify the owner(s) or other interested parties of item 4054 that it has provided a copy to the authorized requestor (FIG. 123, block 4820). Trusted go-between 4700 may perform appropriate payment processing as may be required for this transaction (FIG. 123, block 4822), and may optionally issue appropriate receipts to appropriate parties (FIG. 123, block 4824). EXAMPLE CONTRACT EXECUTION PROCESS FIGS. 124A-124B are together a flow chart of an example process for contract execution such as shown in FIG. 97. In this example process 4830, Alice and Bob wish to enter into a contract. Alice creates the contract 4068 using a word processor or other appropriate mechanism (FIG. 124A, block 4832). Alice identifies Bob as the other party to the contract (FIG. 124A, block 4834). The protected processing environment 500 within Alice's electronic appliance 600 may create appropriate electronic controls (FIG. 124A, block 4836) specifying that Bob is the other party and other parameters (e.g., her offer is only good for thirty days, Bob's electronic appliance must use biometric sensing techniques of a certain type for execution, Bob may or may not change the contract) Alice may indicate to protected processing environment 500 within her electronic appliance 600 that she wishes to sign the contract--thereby creating a legal "offer" (FIG. 124A, block 4838). She may do so by, for example, clicking on a "I agree" icon or button her PPE 500 causes to be displayed, by placing her finger on a biometric sensor, etc. The particular mechanism used is preferably sufficiently secure to make it difficult for Alice to later repudiate her decision to sign. The strength of the authentication should be indicated in the transmission, as well as some requirement for this strength. This is central to "commercial trustedness," and furthermore the level of assurance (e.g. location, tamper resistance, etc.) is directly tied to this. The level of trustedness is based on the strength of authentication which can never exceed the strength of the assurance level; both of which should be disclosed to all relevant parties in a transaction. In this response to this action, Alice's protected processing environment 500 may affix Alice's signature 4300 and/or appropriate personal seals 4200 to the contract (see FIG. 97) (FIG. 124A, block 4838). The process 4830 may, at this point, perform an appropriate payment method pre-authorization (for example, to ensure that Alice will pay the compensation required under the contract) (FIG. 124A, block 4840). Alice's protected processing environment 500 may package the sealed, signed contract 4068 with appropriate controls provided by block 4836 within an electronic container 302 (FIG. 124A, block 4842). Alice's electronic appliance 600 may send the resulting object 300 to Bob's electronic appliance 600. Upon receipt by Bob's electronic appliance (FIG. 124A, block 4844), Bob's protected processing environment 500 may open the container 302 and authenticate the received object 300, Alice's signature 4300 and/or her seal 4200 (FIG. 124A, block 4846). Bob's protected processing environment 500 may then cause Alice's signed contract to be displayed so that Bob can read and understand it (FIG. 124A, block 4848). Assume that Bob reads the contract, and agrees to sign it (FIG. 124A, block 4848). In this case, Bob's protected processing environment may send an object 300 to Alice's protected processing environment containing "agreement" controls--electronic controls that provide PPE 500 with methods to perform when the parties have agreed to execute the contract (FIG. 124A, block 4850)). At this point, Alice may confirm her intention to sign the contract as now agreed to by Bob (e.g., Bob may have modified the contract before agreeing to sign it) FIG. 124A, block 4852). This confirmation may, for example, be based on biometric or other non-repudiation assuring techniques as described above. Alice's protected processing environment 500 may send notification of Alice's confirmation to Bob (FIG. 124A, block 4854). Upon receipt of Alice's confirmation (FIG. 124B, block 4856), Bob may also sign the contract conditional on Alice's signature (FIG. 124B, block 4858). Bob's protected processing environment 500 may send the conditionally signed and sealed contract to Alice's protected processing environment (FIG. 124B, block 4860). Alice may then sign and seal the contract (FIG. 124B, block 4862) and her protected processing environment 500 may send the signed and sealed contract to Bob--retaining a copy for Alice herself (FIG. 124B, block 4864)). In this example, Alice's protected processing environment may also send a copy of the signed, sealed contract to a trusted go-between 4700 for notarization and/or archival purposes (see FIG. 101) (FIG. 124B, block 4866). The trusted go-between 4700 may notarize and/or archive the signed, sealed contract (FIG. 124B, block 4868), and may issue archival and/or notary receipts to both Alice and Bob (FIG. 124B, block 4870). In one specific example, the delivered contract can be a non-disclosure agreement co-delivered with an, item(s) 4054 subject to the non-disclosure provisions of the agreement. Associated electronic controls automatically enforce the non-disclosure provisions of the agreement with respect to the co-delivered item(s) 4054. EXAMPLE CONTRACT EXECUTION MEDIATED BY A TRUSTED GO-BETWEEN FIGS. 125A-125B show an example contract execution process in which the trusted electronic go-between 4700 is more directly involve as an intermediary in forming the contract (see FIGS. 101, 101A, 101B). In this example routine 4872, steps 4832A-4840A may be similar or identical to steps 4832-4840 shown in FIG. 124A. However, instead of Alice sending the completed "offer" object 300 directly to Bob's electronic appliance 600, Alice may send the object to trusted go-between 4700 (FIG. 125A, block 4874). Upon receiving the object (FIG. 125A, block 4876), the trusted go-between 4700 may open the object and authenticate it (FIG. 125A, block 4878). The trusted go-between 4700 may then apply its own seal 4200, and send its sealed, notarized copy of the offer in an electronic container 302 with associated appropriated electronic controls to Bob (FIG. 125A, block 4880). Trusted go-between 4700 may notarize and archive the item and associated audit information so far created (FIG. 125A, block 4882) (e.g., to keep a secure record of the negotiation process). Upon receipt of the object, Bob's protected processing environment 500 may open the container 302 (FIG. 125A, block 4884) and send audit records indicating receipt and opening of the object (FIG. 125A, block 4886). Assuming that Bob agrees to sign the document (e.g., after he has read it) (FIG. 125B, block 4848A), Bob may indicate his assent through biometric sensing or other techniques as described above--and his protected processing environment 500 may at that point send an object 300 with "agreement" controls to the trusted go-between 4700 (FIG. 125, block 4888). The trusted go-between 4700 may notify Alice of Bob's intention to sign the contract (FIG. 125B, block 4890). Alice may then send the trusted go-between her signature with electronic controls making the signature conditional on Bob's signature (FIG. 125B, block 4892). The trusted go-between 4700 may archive Alice's signature, and send Bob notification of Alice's conditional signature (FIG. 125B, block 4894). Bob may the sign the contract conditional on Alice's signature (FIG. 125B, block 4858A), and send the conditionally signed and sealed contract to the trusted go-between 4700 (FIG. 125B, block 4896). The trusted go-between 4700 may apply Alice's signature and/or seal to the contract based on the controls she sent to the trusted go-between at block 4892 (FIG. 125B, block 4897). The trusted go-between 4700 may deliver the completed, signed and sealed contract to both Alice and Bob (FIG. 125B, block 4898), and may optionally itself notarize and/or archive the signed, sealed contract (FIG. 125B, block 4899). ADDITIONAL EXAMPLES The following are some non-exhaustive examples of how system 4050 provided by the present inventions can be used in a variety of different, illustrative contexts. EXAMPLE Automobile Purchase FIG. 126 shows an example of how trusted electronic go-between 4700 might help to coordinate and complete a complex contractual arrangement, such as the purchase of a car. Suppose buyers 4070A want to buy a car from manufacturer 4070B through car dealership 4070C. Buyers 4070A could use an electronic appliance 600 to specify the car model, options and price they are willing to pay. They could also fill out a credit application, provide a down payment, package all of this information into a secure electronic-object 300A, and send the electronic container to trusted electronic go-between 4700. Trusted electronic go-between 4700 might then contact the car dealership 4070C, present the buyers' offer and receive (in another secure electronic object 300B) the car dealership's counter offer concerning price and availability. Trusted electronic go-between 4700 could negotiate or mediate between the two parties, and supervise the creation of a contract 68 finalizing the deal. Trusted electronic go-between 4700 could send a copy of the final contract 4068 to the buyers 4070A and to the car dealership 4070C, using secure electronic objects 300C and 300D to ensure secure electronic delivery of this information. Trusted electronic go-between 4700 could include the buyers' down payment within secure object 300D for receipt by car dealership 4070C. Trusted electronic go-between 4700 could also forward the buyers' credit application within yet another secure electronic object 300E to a credit company 4070D. The credit company could provide the proceeds of an automobile loan to car dealership 4070C to pay for the new car. Meanwhile, car dealership 4070C could send an order to the manufacturer 4070B who could manufacture and deliver the new car to the buyers 4070A either directly or through the car dealership 4070C. EXAMPLE Document Notary FIG. 127 shows an example of how system 4050 could be used to notarize a contract, statement or other document. In this example, Bob (4070a) and Ted (4070b) may enter into a contract using electronic or other means. They may sign the contract electronically by having their electronic appliances 600, 600' insert their handwritten and digital signatures (and if desired, also their own personal seals or other affirmations). They may then individually or jointly place the executed contract 4068 into one or more electronic containers 302(1) and transmit the contract to a trusted go-between 4700 for registration. To prevent either party from later repudiating the contract 4068, trusted go-between 4700 may require certain secure indication(s) allowing the trusted go-between to verify that Bob and Ted are who they say they are. These indications required by trusted go-between 4700 should have sufficient reliability that they will later stand up in a court of law. One possibility is for trusted go-between 4700 to capture biometric information such as photographic images, fingerprints, handprints, retina patterns or the like. Another possibility is to rely on the digital signatures (and thus the security of the private keys) of Bob and Ted--possibly in conjunction with digital certificates and biometric sensing techniques as described above. In system 4050, Bob's private key and Ted's private key might never be exposed outside of their respective secure electronic appliances 600, 600'--preventing each of them from voluntarily exposing their private keys as a basis for repudiating the contract. Trusted go-between 4700 may be completely electronic and automatic. It may receive container 302(1), and open the container to access the contract 4068 it contains. Trusted go-between 4700 may create a notarial seal 4200 on the document encoded with information encrypted using the trusted go-between's private key. This encrypted information might indicate the time and date the trusted go-between received the document; a digital certificate number that securely identifies the trusted go-between; and the "hash" value of the signed contract 4068 (see FIG. 103 above). Trusted go-between 4700 may include this resulting digital signature within its notarial seal 4200 and/or may place the digital signature elsewhere on the document 4068 to create a notarized version 4068'. Trusted go-between 4700 may then store the notarized document 4068' within its secure electronic archive 4702. The trusted go-between 4700 may also, if desired, supply copies of the notarized document back to Bob (4070a) and Ted (4070b) within additional electronic containers so they each have record copies of the notarized contract 4068'. Suppose a dispute arises between Bob and Ted. Bob wants to enforce the contract 4068 against Ted. Ted claims he never signed the contract. Trusted go-between 4700 supplies a copy of the notarized contract 4068' to a court of law 5016 or other dispute resolver. By electronically analyzing the executed contract 4068', the court 5016 can read the notarization assurance of trusted go-between 4700 that Ted did in fact execute contract 4068. So long as the trusted go-between 4700 required sufficient verification of Ted's identity before electronically notarizing the document 4068', the court 5016 should accept the notarization as conclusive evidence that Ted executed it. Because of the extremely high degree of trustedness possible using system 4050, the FIG. 127 example could be used to communicate national security secrets or highly sensitive criminal investigation results (e.g., wiretaps) between authorized government agents. Trusted go-between 4700 might be authorized to register (but not open) the containers 302(1) it, receives for later use as evidence in court 5016. EXAMPLE Teleconferencing FIG. 128 shows the variation on the FIG. 127 example including a teleconferencing capability. In this FIG. 128 above, intelligent kiosk appliances 600, 600' are each equipped with a video camera 4124 that allows sender 4052 and recipient 4056 to see and speak with one another in real time. Sender 4052 can see recipient 4056 on the sender's display, and recipient 4056 can see sender 4052 on the recipient's display. Similarly, the sender and recipient can each hear each other through microphones/speakers, 4128 (and/or telephone handsets 4110) their intelligent kiosks are equipped with. This teleconferencing capability can be useful, for example, to allow sender 4052 and recipient 4056 to verify they each are who they say they are, and to assist in negotiating contract 4068 or otherwise discussing the content of an item 4054. In order to further assure the authenticity of the communication, a secure communications link may be established using key exchange techniques (e.g., Diffie-Hellman) and encryption of the signal between the stations. Secure containers 302 may be used to encapsulate the video and audio being exchanged between electronic kiosk appliances 600, 600' to maintain confidentiality and ensure a high degree of trustedness. Thus, in this example, each secure container 302(2) might contain some portion of or multiple video images and/or some portion of or multiple audio segments. Electronic appliances 600, 600' can exchange such secure container 302(2) back and forth in rapid succession to provide real time audio and video transmission In order to improve performance, the containers themselves may remain at the users' sites, and only the encrypted contents transmitted between the participants. This may allow one or two containers to protect the entire communications between the parties. In still another variation, the teleconferencing shown in FIG. 128 does not need to be simultaneous. For example, sender 4052 could walk up to kiosk appliance 600 and operate the kiosk to record a brief video and audio recording of a message. Sender 4052 could use appliance 600 to review and approve the recording, and then send the recording to recipient 4056 in more or more secure containers 302. Recipient 4056 could present himself to the same or different electronic appliance 600' at a later time. The electronic appliance 600' could verify that recipient 4056 is who he says he is, and then play back the sender's recording. EXAMPLE Doctor Management/Coordination of Health Records FIG. 129 shows how system 4050 might be used to help a doctor 1000 manage and coordinate health records. In this example, after seeing a patient, doctor 5000 might use an electronic appliance 600 (such as a personal computer for example) to electronically create a patient record 5004 and a drug prescription 5006. The doctor 5000 could instruct electronic appliance 600 to package a copy of patient record 1004 and drug prescription 5006 into one or more secure electronic containers 302(1). Doctor 5000 could specify to electronic appliance 600 (in the form of electronic controls 4078) that: neither document can be modified; each document is highly confidential; patient record 5004 may be revealed only to the patient's insurance company 5008; and drug prescription 5006 may be revealed only to the patient 5002 and to the patient's chosen drug store 5010. The doctor 5000 may then send container 302(1) to a trusted go-between 4700. Trusted go-between 4700 could be a computer within a doctor's office, or it could be a commercially operated trusted go-between specializing in health care transactions or usable in general types of transactions. Trusted go-between 4700 might be instructed by electronic controls 4078 to time and date stamp electronic container 302(1) upon receipt, and to store the electronic container within its secure archive 4702. It might also be instructed to maintain patient records 5004 completely confidential (indeed, controls 4078 may prevent the trusted go-between 4700 from itself having any access to these patient records), but to forward a copy of the patient records 5004 to the patient's insurance company 5008 so the insurance company can pay for the medical services rendered by the doctor 5000. For example, the trusted go-between 4700 in one example has no access to the content of the container 302(1), but does have a record of a seal of the contents. If trusted go-between 4700 has the seal, it can interact with other parties to confirm the contents of the seal--without needing to know or disclosing (as the case may be) the contents. Controls 4078 might also instruct trusted go-between 4700 to forward the drug prescription 5006 to the patient's selected drug store 5010 upon the request of patient 5002. The patient 5002 could make such a forwarding request, for example, by operating An intelligent kiosk 600' at the drug store 5010. The patient's electronic request 5012 could be sent to trusted go-between 4700, which in response might retrieve the drug prescription 5006 from its secure archive and forward it electronically within a secure container 302(3) to the drug store 5010 chosen by patient 5002. One of the patient records 5004 might be a consent form that was executed by patient 5002. To help prevent the patient 5002 from later repudiating his consent, doctor 5000 might register this consent form with trusted go-between 4700--which could then "witness" it by notarizing it and affixing its seal, date stamp and/or digital signature. Trusted go-between 4700 could provide this consent form 5014 to a court of law 5016 and/or medical malpractice company in the event that patient 5002 sued the doctor for medical malpractice. EXAMPLE Complex Business Transaction FIG. 130 shows an example of how system 4050 might be used to accomplish a real estate transaction. In this example, seller 5030 wants to sell his house 5032, and buyer 5034 wants to buy the house. The seller 5030 and buyer 5034 and their respective real estate agents 5036, 5038 write a legal contract which the seller and buyer then sign. The seller 5030 and buyer 5034 use an electronic appliance 600 to create an electronic version of contract 4068 (or the electronic execution techniques discussed above could be used to initially create the contract). They place the executed electronic version of the contract 4068 within one or more secure electronic containers 302(1), and send the contract to trusted go-between 4700. Trusted go-between 4700 registers the contract 4068, and then creates an electronic list of rules based on contract 4068. A partial example rule list is shown in FIG. 130A. Although the FIG. 130A conditions are shown as being written on a clipboard, in the preferred embodiment the "clipboard" is electronically implemented by a computer and comprises one or more electronic control sets 4078 that specify the conditions that must be satisfied in order for the overall real estate transaction to settle. Trusted go-between 4700 may need to communicate with each of a number of parties in order to determine whether the conditions have been satisfied. For example: trusted go-between 4700 may need to confirm, via a secure communication 302(2) with an escrow bank 5040, that the buyer 5034 and buyer's agent 5038 have deposited a purchase money deposit with the escrow bank; trusted go-between 4700 may assist buyer 5034 in creating and filing loan applications with one or more banks 5042, along with supporting documentation, and may require confirmation from the lending bank 5042 that the buyer's financing has been approved so the transaction can go forward; trusted go-between may have to coordinate with an inspector, appraiser and/or surveyor 5044 to ensure that house 5032 has no termites, has an appraised value in excess of the value buyer 5034 is attempting to borrow from lender 5042, has been properly surveyed as required by the lender, etc.; trusted go-between 4700 may need to coordinate with a lawyer 5046 to ensure that the title to the property for sale is clear and unencumbered; and trusted go-between 4700 may need to communicate with other parties to take care of other details leading up to the transaction completion. In this example, trusted go-between 4700 may receive electronic notifications in secure containers 302 as each step in the overall process is completed. As illustrated in FIG. A3A, trusted go-between 4700 can electronically check each completed condition off of its electronically-maintained condition list as it receives such event notifications. Trusted go-between 4700 maintains this electronic list 4704 in a secure, validated and authenticated manner using system 4050--requiring, for example, receipt of electronic containers having event notifications that are signed cryptographically with one or more digital signatures from the appropriate parties. In this way, trusted go-between 4700 can maintain a highly reliable and validated, authenticated audit of the transaction steps as the overall transaction proceeds. In addition, trusted go-between 4700 may, if desired, be empowered to issue additional requirements and/or instructions to facilitate the progress of the transaction. For example, trusted go-between 4700 might be a private trusted go-between operated by lender 5042--and thus, might be empowered to select which lawyer 5046 to use and to send that lawyer, automatically, appropriate instructions and forms for completing the transaction. As another example, the trusted go-between 4700 may be part of the business operated by lawyer 5046 or other settlement agent, and may thus be empowered to select and instruct escrow bank 5040. When trusted go-between 4700 determines, based on the electronic rules/control set 4704 and the notifications it has received that all conditions for settlement have been satisfied, the trusted go-between may allow the "atomic transaction" to settle by issuing appropriate notifications and/or instructions--once again using secure electronic containers 302 and the receipt, verification, authentication, and other mechanisms discussed above to ensure reliability, confidentiality and a high degree of trustedness. For example: The trusted go-between 4700 might instruct the lender 5042 to deposit the loan proceeds into loan escrow bank 5040. Upon receiving notification from escrow bank 5040 that the loan proceeds have been properly deposited and the money is available, the trusted go-between 4700 could instruct escrow bank 5040 to transfer the funds to seller's bank 5048 and thereby release the seller's outstanding mortgage on the property. Trusted go-between 4700 might also instruct escrow bank 5040 to transfer or otherwise pay the seller's agent 5036 and the buyer's agent 5038 their appropriate commissions as set forth in contract 4068. Trusted go-between 4700 might also notarize the deed which seller 5030 has executed in favor of buyer 5034, and could electronically file the deed with the court 5016 (or other governmental authority) for recordation. Trusted go-between 4700 might also at the same time file the lender's 5042 deed of trust and a release executed by the seller's bank 5048. All of these various coordination steps can be performed nearly simultaneously, efficiently, rapidly and with an extremely high degree of trustedness based on the user of electronic containers 302 and the secure communications, authentication, notarization and archiving techniques provided in accordance with the present inventions. EXAMPLE Court Filings and Docket Management FIG. 131 shows how system 4050 could be used to manage filings in a court of law. In this example, the plaintiffs attorney 5050 and the defendant's attorney 5052 can electronically exchange court filings and other documents (e.g., letters, discovery requests, discovery responses, motions, briefs, responses, etc.) by sending secure containers 302 between their respective electronic appliances 600, 600'. Because of the high degree of security and trustedness provided by system 4050, even confidential information can be exchanged using this technique with little risk that the information will fall into the wrong hands (of course, the system cannot prevent people from making mistakes, in addition to the chance--however remote--that a determined adversary could dedicate sufficient resources to cracking the system (such as, for example, through brute force techniques to "crack" the algorithms). The lawyers can specifically specify who can open the containers 302 and have a very high degree of trust that no one other than the specified individuals (e.g., opposing counsel and the court 5056) will be able to access the information within. For example, defendant's attorney 5052 can specify one container 302 for opening by his co-counsel, client or client's in-house counsel, and program another container 302 for opening only by opposing (plaintiffs) counsel 5050. Because of the unique trustedness features provided by system 4050, the defendant's attorney 5052 can have a high degree of trust and confidence that only the authorized parties will be able to open the respective containers and access the information they contain. Appliances. 600, 600' may issue highly trusted and reliable return receipts as described above. These highly trusted electronic return receipts may substitute for certificates of service if court 5016 permits. The lawyers 5050, 5052 can also electronically file any of these exchanged documents with the court 5056 by sending the documents to the clerk 5054 via secure electronic containers 302. In this example, the clerk 5054 may actually be a computerized trusted go-between 4700 (represented here by a person but implemented in practice in whole or in part by one or more secure electronic appliances 600). The clerk 5054 may present a digital certificate evidencing that it is authorized to open a secure container 302 it has received. The clerk may then date stamp each received document (this may involve placing a seal 4200 on the document but more typically might involve simply placing a digital time signature on the document). The clerk 5054 may file the document electronically within a secure electronic archive 4702 that can provide a database for linking related documents together. The judge 5056 might have a secure electronic appliance 600 in the courtroom or in chambers that could be used to view and/or print documents from the secure electronic archive 4702. The judge 5056 could instantly call up any filing to determine when it was received by the clerk 5054 and to review its contents. Different authorizations and/or encryption strengths could be used with respect to publicly available documents and documents under seal (for example, so that sealed documents could only be opened by the judge 5056 or her staff). The judge 5056 could write her orders and opinions using electronic appliance 600. She could then send these documents within a secure electronic container 302(3) for filing by the clerk 5054 in secure electronic archive 4702, and for automatic service on the lawyers 5050, 5052. In this example, the clerk/trusted go-between 4700 could also be used to ensure compliance with the local rules of court. For example, the clerk/trusted go-between 4700 could maintain, in electronic form, electronic controls 4078 indicating the time and formal requirements with respect to different kinds of filings. The clerk/trusted go-between 4700 could automatically check all incoming filings from the lawyers 5050, 5052 to ensure compliance with the local rules, and to issue notices and other appropriate forms in accordance with the local rules. Use of a dynamic interface technology may be used to generate and deliver a set of controls to the sender's system that defines the parameters of receipt--and default controls may be used to specify appropriate parameters, formats, etc. FIG. 131 shows that this system can be extended to allow communications between defendant's counsel 5052, his co-counsel (e.g., defendant's in-house counsel) 5052A, and his client (e.g., the defendant's Chief Executive Officer) 5052B. Because of the high degree of trustedness and security-provided by system 4050, there is no danger that privileged communications between defendant's CEO 5052B and defendant's litigating counsel 5052 will be disclosed to plaintiffs counsel 5050. On the other hand, defendant's litigating counsel 5052 could automatically distribute certain documents (e.g., court filings not under seal, discovery requests and responses, etc) to defendant's CEO 5052B and defendant's inside counsel 5052A in addition to sending them to the court 5016 and to plaintiff's counsel 5050. In this example, defendant's litigating counsel 5052 could enforce any/all of the following different electronic control set options on electronic container contents: accessible by inhouse counsel 5052A and CEO 5052B only (e.g., for privileged, attorney-client communications); accessible by the court 5016, plaintiff's counsel 5050, inhouse counsel 5052A, CEO 5052B (e.g., for court filings not under seal); accessible by the court 5016, plaintiff's counsel 5050, and inhouse counsel 5052A but not CEO 5052B (e.g., for court filings under seal); accessible by the court 5016 only (e.g., for documents being reviewed in camera). Note that in this example, documents can be controlled independently of where they are routed. For example, defendant's litigating counsel 5052 could specify electronic controls that would allow court 5016 to access a document that need not be filed with the court but which might be of interest to the court at a later date (e.g., letter between opposing counsel later used as an exhibit to a motion). The fact of document transmission (along with some information about the document such as document title and identifier) could be transmitted without actually transmitting the document itself--allowing the court to retrieve the document itself independently at a later time if desired. EXAMPLE Patent Office Automation FIG. 132 shows how system 4050 might be used for Patent Office automation. In this example, an inventor 5060 might file her patent application 5062 by sending it to the Patent Office 5064 in one or more secure electronic containers 302(1). The high degree of trustedness, confidentiality and security provided in accordance with these inventions ensure that the patent application 5062 will arrive at the Patent Office 5064, and will not be disclosed to or accessed by anyone other than the Patent Office. Upon receiving the patent application 5062, a trusted go-between 4700 within the Patent Office 5064 could open the container 302(1) and access the patent application 5062. Trusted go-between 4700 could electronically examine the patent application 5062 to ensure it meets all formal requirements, and could also date/time stamp the received patent application in order to document its filing date. Trusted go-between 4700 could automatically issue the inventor 5060 a filing receipt based upon secure receipt of the patent application 5062 using the return receipt techniques described above. Trusted go-between 4700 could then deposit the patent application 5062 into a secure electronic archive 4702 to await examination. Trusted go-between 4700 could include appropriate routing information based on a routing slip as described above to route the patent application 5062 to the appropriate group and/or patent examiner 5064 within the Patent Office 5064. A patent examiner. 5064 could examine the patent application 5062 by requesting a copy of it from electronic archive 4702. All communications could take place within secure electronic containers 302(2) to ensure confidentiality and reliability--completely avoiding the problem of lost files. The patent examiner 5064 could conduct prior art searches using the same electronic appliance 600' used to review the patent application 5062. The examiner 5064 could print out a copy of the patent application 5062 as desired. The patent examiner 5064 could also use electronic appliance 600' to draft office actions and notices. The examiner 5064 could communicate these notices and actions via trusted go-between 4700 to the inventor 5060. Trusted go-between 4700 could maintain copies of the examiner's actions and notices within secure electronic archive 4702--ensuring their confidentiality and also making sure they do not become lost. System 4050 could provide a return receipt when the inventor 5060 opened the electronic container 302 containing the examiner's actions or notices--thus proving in a highly reliable and trusted fashion that the inventor had in fact received what the examiner sent. Similarly, inventor 5060 could file responses (and could even teleconference with the examiner 5064) via electronic appliance 600. The high degree of trustedness and confidentiality provided by system 4050 along with the return receipt and other options discussed above provide a highly reliable, confidential communications means that can be used to demonstrate when items were actually filed. Once the examiner--after conducting a lengthy prior art search and carefully analyzing the patent application 5062 to ensure that the invention is patentable--is fully and completely satisfied that the inventor 5060 is entitled to a patent, the examiner 5064 could instruct the trusted go-between 4700 to grant the application as a patent. Trusted go-between 4700 could retrieve a copy of the application 5062 from the secure electronic archive 4702, use automatic means to transform it into an issued patent, and insert a seal 4200 (for example, bearing the digital certificate of the Patent Office 5064) onto the document. The trusted go-between 4700 could then issue the granted patent 5066 to the inventor 5060 by sending it in a secure electronic container 302(3)--thus ensuring that it does not get lost and is in fact received by the inventor. Members of the public could obtain a copy of the issued patent 5066 by requesting one from trusted go-between 4700. Trusted go-between 4700 could maintain a copy of the issued patent 5066 within secure electronic archive 4702, along with electronic controls 4078 that specify the document is a matter of public record and can be disclosed to members of the public. Other documents in secure electronic archive 4702 (e.g., patent applications 5062 that have not yet been published) can be maintained confidential by use of electronic controls 4078 specifying that only certain people (e.g., patent examiner 5064) can access them. The FIG. 132 example also provides a convenient mechanism for registering invention disclosure documents with the patent office or other organization. For example, inventor 5060 could use electronic appliance 600 to file an invention disclosure document with the trusted go-between 4700. Trusted go-between 4700 would notarize or witness receipt of the document upon receipt by embedding the document with a digital signature specifying the trusted go-between's identity, the current time and date, and a hash value for use in an integrity check. Trusted go-between 4700 could then file the invention disclosure document within secure electronic archive 4702. At a later date, inventor 5062 could prove the invention disclosure document had been created as of a certain date by requesting trusted go-between 4700 to produce a copy of the invention disclosure document from secure electronic archive 4702. Trusted go-between 4700 would thus provide a secure, trusted independent corroboration of document creation--since it could demonstrate (based upon its imprinted digital signature) that it had received the document on a certain date and that the document had a certain contents. The disclosure service could also simply send the inventor a signed hash value, and then discard the document; since the hash value could be used with a copy preserved by the inventor. The service could archive the signed hash value themselves as well (although that is not required). EXAMPLE Tax Filing System FIG. 133 shows an example of how system 4050 can be used to facilitate filing of income or other taxes. Sender 4052 can use electronic kiosk appliance 600 to file her income tax return 5070. Appliance 600 transmits the income tax return 5070 to the governmental taxing authority 5072 within a secure container 302(1). Secure container 302(1) ensures that the tax return 5070 is opened by no one other than the governmental tax authority 5072. System 4050 can electronically provide a return receipt to sender 4052 proving that tax authority 5072 received the tax return 5070. Appliance 600 may help the taxpayer 4052 complete her tax return 5070. For example, the appliance 600 could ask a series of questions based on a preprogrammed electronic script. The appliance 600 could calculate the taxes owed, and--once taxpayer 4052 approved the tax return 5070--allow the taxpayer to electronically sign the return as described above. Appliance 600 could accept tax payments via credit or smart cards, debit authorizations from bank accounts, etc. Appliance 600 could also issue a paper or electronic receipt to the taxpayer 4052 assuring the taxpayer that the tax return 5070 has been filed. A court might accept this receipt as evidence of timely filing. Tax authority 5072 may include an internal trusted go-between 4700 that registers and securely date stamps all tax return filings 5070 and places them into a secure electronic archive 4702. The trusted go-between 4700 can also analyze each tax return 5070 to ensure that it complies with electronic rules embodying the tax laws (some of this process could be performed by humans and some by computers if desired). Trusted go-between 4700 can provide, to a payment mechanism 5074, an electronic container 302(2) requesting the payment mechanism to issue a refund to (or collect a deficiency from) the tax payer 4052. In one example, payment can be in the form of electronic currency carried within one or more secure containers 302(3). If the return is structured appropriately for automated processing, tax calculations and application of relevant tax rules can also be automated by the trusted go-between. EXAMPLE Inter and Intra Organization Communications FIG. 102 (described above) shows an example of secure trusted electronic go-betweens for use within and outside of organizations such as corporations. As described above, the secure electronic go-betweens 700(A), 700(B) can be used to facilitate secure item handling and delivery within an organization. As one example, suppose a confidential memo needs to be approved by users 600(A)(1), 600(A)(3) and 600(A)(5) (who can each revise the memo) before being distributed to each of users 600(A)(2), 600(A)(7)-600(A)(10) and 600(A)(12) (none of whom can change the memo), with copies to users 600(A)(1), 600(A)(3) and 600(A)(5) (who also can't change the memo after all three of them have signed off on it) and to no one else. Private trusted go-between 4700(A) can maintain a rule set that specifies these requirements. Trusted go-between 4700(A) can: send the memo (in secure containers) in "round robin" fashion to each of users 600(A)(1), 600(A)(3) and 600(A)(5) for approval. If any one of these users changes the memo, then trusted go-between 4700(A) can circulate the revised memo to the other two for additional comments and revisions. Once all three of users 600(A)(1), 600(A)(3) and 600(A)(5) approve the memo, trusted go-between 4700(A) may be empowered to place each of their digital and/or handwritten signatures or initials on the memo, place it into one or more secure containers with a control set specifying it is read only and can only be read by users 600(A)(1)-600(A)(3), 600(A)(5), 600(A)(7)-600(A)(10) and 600(A)(12). Trusted go-between 4700(A) may then send a copy of the memo in a container to each of these users, or could require the same container to circulate from one to another. The trusted go-between 4700 may require the electronic controls to maintain a secure audit trail indicating where the container has been, who has opened it, who has accessed the memo it contains, and when. Trusted go-between 4700(A) might thus increase personal accountability by evidencing whether a particular person had-seen a particular document, when, and for how long. Organization A's Intranet 5104 might also be used to exchange and/or distribute highly confidential design specifications. System 4050 can provide a highly secure audit trail indicating who has had access to a container containing the confidential design specifications; when the person(s) accessed it; and what they did with the specification (print a copy, view it on screen for so many minutes, make a copy of it, etc.) System 4050 (with or without the assistance of a trusted go-between 4700(A) can also maintain, in digital form, a detailed record of who has "signed off" on the design specifications--thus ensuring personal accountability and providing a high degree of efficiency. Private transaction authorities 4700(A), 4700(B) can also provide a "firewall" function to protect confidential information from escaping to outside of the respective organizations A, B. Suppose for example that organization A is an integrated circuit design house and organization B is an integrated circuit foundry. Organization A designs and specifies the circuit layout of a chip, producing a "tape out" that it sends to organization B. Organization B manufactures an integrated circuit based on the "tape out", and delivers chips to organization A. System 4050 can be used to facilitate the above business transaction while protecting confidentiality within each of organizations A and B. For example: organization A's private trusted go-between 4700(A) can supervise an overall design and specification development effort within organization A. All communications take place in secure containers 302 over organization A's Intranet 5100(A) to maintain confidentiality. Trusted go-between 4700(A) can maintain a secure archive of historical design documents, works in progress, and specification versions as the design process progresses. Organization A's private trusted go-between 4700(A) can manage the final design specification development--ensuring that all conditions required to finalize the design specifications are followed. Once the design specification has been finalized, trusted go-between 4700(A) can circulate it within secure containers 302 to those individuals within organization A that need to "sign off" on it. Their respective appliances 600(A)(1), . . . 600(A)(k) can affix and/or embed digital signatures, handwritten signatures, seals and/or electronic fingerprints as described above to indicate specification approval. Upon being satisfied that the specification has been "signed off" by the appropriate people, trusted go-between 4700(A) can send it over Internet 1104 within a secure container 302 to public trusted go-between 4700(C). Public trusted go-between 4700(C) may be a commercial trusted go-between retained by organizations A and B to act as a liaison between them. Organization A's private trusted go-between 4700(A) can filter (or protect) all information it sends to public trusted go-between 4700(C) to ensure that organization B can access only that information intended for it. For example, private trusted go-between 4700(A) might provide additional electronic controls within the container to prevent organization B from seeing any detailed audit information showing where the specification has been within organization A. The public trusted go-between 4700(C) might act as an independent trusted third party, notarizing the design specification to later evidence that organization A delivered it on a particular date and time in accordance with a contract. Public trusted go-between 4700(C) could then forward the design specification (still within a secure container) over Internet 5104 to organization B's private trusted go-between 4700(B). Organization B's private trusted go-between 4700(B) could automatically send a copy of the design specification over organization B's Intranet 5100(B) to the appropriate users 600(B)(1), 600(B),(N) within organization B. No one outside of organization B would need to know who received a copy of the specification. On the other hand, organization A's trusted go-between 4700(A) could, if desired, include electronic controls restricting access to only certain engineers within organization B--and these secure controls would be carried along into organization B and securely enforced by electronic appliances 600(B)(1), . . . , 600(B)(N). Organization B's trusted go-between 4700(B) could manage the chip manufacturing process, ensuring that all steps and conditions required to manufacture chips in accordance with organization A's design specification are followed. EXAMPLE Integration with Communications Switching Telecommunications are becoming ubiquitous in post-industrial societies. As a convenience to customers, the trusted go-between could offer many of its services as part of, or in conjunction with providers of telecom services. In one non-limiting example shown in FIG. 134, a trusted go-between 4700 is co-located and integrated with a telephone switch that connects to a telephone or other telecommunications network via wires (or other connections) 5100 (in another example, the switch and trusted-go between 4700 cooperate, but are not co-located). In one example, a person with a laptop 5102 or other computer lacking a PPE 650 wishes nontheless to take advantage of a subset of secure item delivery services. The computer 5102 is equipped with a fax modem and associated application software. The computer dials a special number which may be an "800" number and is connected to the trusted go-between 4700 who authenticates the sender using a pre-established password and/or stronger methods such as biometric measurements. The sender indicates the telephone number of fax machine to receive the document. After selection of delivery options and trusted go-between services, and after making arrangements for payment, the sender's computer 5102 faxes the document pages 4058d, 4058e, 4058h to the trusted go-between 4700. In one-example, the trusted go-between 4700 applies seals 4200 to each page 4058d, 4058e, 4058f of the faxed document and an additional seal for the overall document. The trusted go-between 4700 then faxes the sealed document to the recipient-fax machine 5104. The trusted go-between 4700 also archives and notarizes the sealed document in case the sender or other authorized party requires proof that the document was sent on a particular time and date to a device with a particular telephone number. In the event that the sender's and/or recipient's appliance is VDE aware (e.g., fax machine 4014c equipped with a protected processing environment 650), this service will be provided with additional levels of security and trustedness. In another example, the sender may prefer to have the document delivered in a secure container over a network such as the Internet, in which-case, the sender may indicate the recipient's network address. The sender may connect a personal computer 5102 with a modem to another special number and send a digital item to the trusted go-between 4700 using Internet protocols. In this one example, the sender may not have yet installed VDE, and so the trusted go-between takes the document or item and puts it in a secure container along with controls selected by the sender and delivers the secure container to the recipient, who in this example, does have VDE installed. These examples illustrate the more general point that the trusted go-between 4700 may provide a range of value-added services even to parties who do not yet have the VDE installed on their appliances, and can enhance the security and trustedness of item delivery nevertheless. While the invention has been described in connection with what is presently considered to be the most practical and preferred embodiment, it is to be understood that the invention is not to be limited to the disclosed embodiment, but on the contrary, is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims. * * * * *