[1666] in Virus_Discussion_List
VIRUS-L Digest V10 #89
daemon@ATHENA.MIT.EDU (VIRUS-L/comp.virus Moderator)
Tue Aug 12 15:37:33 1997
Date: Tue, 12 Aug 1997 00:58:18 +0100
Reply-To: virus-l@Lehigh.EDU
From: "VIRUS-L/comp.virus Moderator" <moderator@virus-l.demon.co.uk>
To: "Computer Virus Discussion List" <virus-l@Lehigh.EDU>
VIRUS-L Digest Tuesday, 12 Aug 1997 Volume 10 : Issue 89
Today's Topics:
Please keep posts down till backlog clears (ADMIN)
CFP: 1998 Symposium on Network and Distributed System Security
Compsec 97 - Unmasking the Ghost in Your Machine
7th USENIX Security Symposium - Call for Papers
Virus Bulletin Conference -- VB'97
Legal Tech Intranet/Extranet Conference ^
Extract: _Underground_ new book on international computer crime - "The WANK worm"
VIRUS-L is a moderated, digested mail forum for discussing computer
virus issues; comp.virus is its gatewayed and non-digested USENET
counterpart. Discussions are not limited to any one hardware/software
platform--diversity is welcomed. Contributions should be relevant,
concise, polite, etc. (The complete set of posting guidelines is
available by FTP on ftp.infospace.com/pub/virus-l (IP 206.129.166.107)
or upon request.) Please sign submissions with your real name; clearly
faked or anonymous postings will not be accepted. Some antivirus
documentation, and a full set of back-issues are also archived at
ftp.infospace.com, which is also the home of our FAQ (Frequently Asked
Questions) document.
Administrative mail (e.g., comments or suggestions) should be sent to
me at: nick@virus-l.demon.co.uk. (Beer recipes should still be sent to
Ken van Wyk at: krvw@mnsinc.com.)
VIRUS-L subscribers wanting help with list-processor commands should
send a message to listserv@lehigh.edu with the command "info virus-l"
in the body of the message (the listserv ignores Subject: lines).
All submissions should be sent to: VIRUS-L@lehigh.edu.
Nick FitzGerald
----------------------------------------------------------------------
Date: Mon, 12 Aug 1997 23:55:21 +0100
From: "Virus-L/comp.virus Moderator" <moderator@virus-l.demon.co.uk>
Subject: Please keep posts down till backlog clears (ADMIN)
X-Digest: Volume 10 : Issue 89
Hi all. I have approx eight digests worth of messages still to post,
so please only follow-up to the group if your reply is especially
meritorious.
This is "the conference issue". Some of the conference announcements
here are almost out-of-date--hope it's not too late for your
favourite...
Regards,
Nick FitzGerald,
Virus-L/comp.virus moderator.
------------------------------
Date: Fri, 06 Jun 1997 15:05:39 -0700
From: Matt Bishop <bishop@cs.ucdavis.edu>
Subject: CFP: 1998 Symposium on Network and Distributed System Security
X-Digest: Volume 10 : Issue 89
CALL FOR PAPERS
The Internet Society Symposium on Network and Distributed System Security
Where: San Diego, California
When: March 1998
GOAL: The symposium will foster information exchange between hardware and
software developers of network and distributed system security services.
The intended audience is those who are interested in the practical aspects
of network and distributed system security, focusing on actual system
design and implementation, rather than theory. Encouraging and enabling
the Internet community to apply, deploy, and advance the state of available
security technology is the major focus of symposium. Symposium proceedings
will be published by the Internet Society. Topics for the symposium
include, but are not limited to, the following:
* Architectures for large-scale, heterogeneous distributed systems
* Security in malleable systems: mobile code, mobile agents, dynamic policy
updates, etc.
* Special problems: e.g. interplay between security goals and other goals --
efficiency, reliability, interoperability, resource sharing, and cost.
* Integrating security services with system and application security
facilities and with application protocols, including message handling,
file transport, remote file access, directories, time synchronization,
data base management, routing, voice and video multicast, network
management, boot services, and mobile computing.
* Fundamental services: authentication, integrity, confidentiality,
authorization, non-repudiation, and availability.
* Supporting mechanisms and APIs: key management and certification
infrastructures, audit, and intrusion detection.
* Telecommunications security, especially for emerging technologies -- very
large systems like the Internet, high-speed systems like the gigabit
testbeds, wireless systems, and personal communication systems.
* Controls: firewalls, packet filters, application gateways
* Object security and security objects
* Network information resources and tools such as World Wide Web (WWW),
Gopher, Archie, and WAIS.
* Electronic commerce: payment services, fee-for-access, EDI, notary;
endorsement, licensing, bonding, and other forms of assurance; intellectual
property protections
GENERAL CHAIR:
David Balenson, Trusted Information Systems
PROGRAM CHAIRS:
Matt Bishop, University of California at Davis
Steve Kent, BBN
PROGRAM COMMITTEE:
Steve Bellovin, AT&T Labs -- Research
Doug Engert, Argonne National Laboratories
Warwick Ford, VeriSign
Li Gong, JavaSoft
Rich Graveman, Bellcore
Ari Juels, RSA Laboratories
Tom Longstaff, CERT/CC
Doug Maughan, National Security Agency
Dan Nessett, 3Com Corporation
Rich Parker, NATO
Michael Roe, Cambridge University
Rob Rosenthal, DARPA
Wolfgang Schneider, GMD Darmstadt
Christoph Schuba, Purdue University
Win Treese, Open Market, Inc.
Jonathan Trostle, Novell
Gene Tsudik, USC/Information Sciences Institute
Steve Welke, Institute for Defense Analyses
LOCAL ARRANGEMENTS CHAIR:
Thomas Hutton, San Diego Supercomputer Center
PUBLICATIONS CHAIR:
Steve Welke, Institute for Defense Analyses
LOGISTICS CHAIR:
Torryn Brazell, Internet Society
SUBMISSIONS: The committee invites technical papers and panel
proposals, for topics of technical and general interest. Technical
papers should be 10-20 pages in length. Panel proposals should be two
pages and should describe the topic, identify the panel chair, explain
the format of the panel, and list three to four potential panelists.
Technical papers will appear in the proceedings. A description of each
panel will appear in the proceedings, and may at the discretion of the
panel chair, include written position statements from each panelist.
Each submission must contain a separate title page with the type of
submission (paper or panel), the title or topic, the names of the
author(s), organizational affiliation(s), telephone and FAX numbers,
postal addresses, Internet electronic mail addresses, and must list a
single point of contact if more than one author. The names of authors,
affiliations, and other identifying information should appear only on
the separate title page.
Submissions must be received by 1 August 1997, and should be made via
electronic mail in either PostScript or ASCII format. If the committee
is unable to print a PostScript submission, it will be returned and
hardcopy requested. Therefore, PostScript submissions should arrive
well before 1 August. If electronic submission is difficult,
submissions should be sent via postal mail.
All submissions and program related correspondence (only) should be
directed to the program chair: Matt Bishop, Department of Computer
Science, University of California at Davis, Davis CA 95616-8562,
Email: sndss98-submissions@cs.ucdavis.edu. Phone: +1 (916) 752-8060,
FAX: +1 (916) 752-4767,
Dates, final call for papers, advance program, and registration
information will be available at the URL:
http://www.isoc.org/conferences/ndss98.
Each submission will be acknowledged by e-mail. If acknowledgment is
not received within seven days, please contact the program chair as in-
dicated above. Authors and panelists will be notified of acceptance by
1 October 1997. Instructions for preparing camera-ready copy for the
proceedings will be sent at that time. The camera-ready copy must be
received by 1 November 1997.
------------------------------
Date: Tue, 10 Jun 1997 10:37:19 -0700
From: Jon Buxton <J.Buxton@elsevier.co.uk>
Subject: Compsec 97 - Unmasking the Ghost in Your Machine
X-Digest: Volume 10 : Issue 89
COMPSEC 97
Unmasking the Ghost in Your Machine
The 14th World Conference on Computer Security, Audit & Control
5th-7th November 1997
QEII Conference Centre
Westminster
London
UK
Included in this years Compsec package:-
An extra day of pre-conference sessions on November 4th
presented by Dr. Bill Hancock.
A dedicated Press Briefing including a question and answer
session with our panel of experts.
The Main Four stream conference including over
60 sessions of the highest Computer Security
advice and expertise.
The 6th Annual Directors' Briefing sponsored by COMPUTER
WEEKLY
A new larger COMPSEC 97 Exhibition including an evening
reception.
Sponsored by:-
Elsevier Advanced Technology, Faculty of Information Technology,
Information Systems Audit & Control Association, ICAEW, Federation
Against Software Theft.
Visit our new web site
http://www.elsevier.nl/locate/compsec
The 14th World Conference on Computer Security, Audit and Control
Internet/Intranet Security
Whether utilising the Internet or developing a corporate Intranet, the
threats exist and are similar. Ensure that you remain aware of some of
the latest trends in this field of security.
Security Strategy
Security cannot be applied in a vacuum, it needs to be implemented
within a business framework in order to be effective. What is the extent
of the threat? How can the strategy be managed at the desktop? What role
do TTPs and Certification Authorities play?
Encryption
The key behind the future of effective information security. Learn what
the past has to teach us about where crypto is now and how it will
influence future developments. Discover some of the current concerns in
Internet encryption, system initialisation and protocol failures.
Viruses
Is certification of anti-virus products worth the paper it is written
on, and can you really contract a virus while surfing the Net?
EDP Audit
Learn of developments in IT auditing and in the major areas of computer
security relevant to the EDP auditor.
Hacker Methods
A look at some of the hackers current technical tricks, and an inside
report of the state of play within the hacking community.
Phreaking/Telecoms Fraud
Communications technology has undergone massive development in the last
few years, which has in turn fuelled the growth in telecommunications
fraud. Learn to recognise the very real threats to your organization.
Windows/NT Security
Just how secure is the worlds most popular operating system software?
Hear the view from the company and from an acknowledged independent
expert about Microsoft's software security.
Open Systems
Are `open' systems inherently insecure? Learn of the existing threats
and the advances and future directions in securing these systems.
Security Management
There is far more to security than technology. Do you have the right
people to do the job, and how aware are your staff of the security
issues?
Disaster Recovery
Will your business literally go with a bang, go up in smoke or be swept
away by a flood? Will you sit like Canute and hold back the tide, or
will you listen to the experts?
Network Security
The threats to your system infrastructure and data transmission are
considerable. Are you taking the right steps at all levels to secure
your networks?
Electronic Commerce
The future of business is electronic, yet the future of electronic
commerce is founded upon security. The risks of not considering the
security issues before taking the plunge into electronic commerce are
not worth taking.
Information Warfare
Infowar has moved away from simply being a military problem. It is
starting to pose a real threat to industry and corporate communications
structures. Just what is the threat and how can it be faced?
Technical Issues
Do you have a problem with applets? Is Java a strong coffee or a
security headache?
Will the evolving threats outpace the developing technology to counter
them? Is technology on the side of the criminal or the security manager?
Legal Issues
The Internet has become a legal quagmire, how should this be faced by
the security manager? And, who really is liable if software bugs result
in security breaches which damage your company?
The Year 2000
Less than three years to go, are you prepared for the millennium bugs?
Think again, have you yet considered the problem with embedded systems?
Directors Briefing
Free to all Compsec International delegates - the business perspective
of computer security. Appreciate the benefits of security investment and
learn the consequences of failing to carry out effective security
practices.
What previous delegates have said about COMPSEC
"As a leading practitioner of computer security assurance, we recognise
the importance of technical training for our staff. Compsec provided an
excellent selection of technical presentations and the opportunity to
meet other colleagues in the same profession."
Computer Assurance Services Manager, Coopers & Lybrand, UK
"The conference gave me an appreciation of where technology and control
is heading for the future."
Senior Computer Auditor, BT, UK
"This conference is an opportunity to gain a wider perspective of the
challenges involved."
Strategic Planning Manager, Polygram Record Operations Ltd., UK
"Very high quality papers - invaluable for reference."
Chief of Automation Systems, National Bank of Commerce, Tanzania.
"Broad Spectrum of interesting speakers."
IT Audit Manager, Uni Storebrand A/S, Norway.
Pre-COMPSEC Seminars
Tuesday 4th November, Stakis St. Ermins Hotel, London.
Dr. Bill Hancock (Executive Vice-President, Network 1 Software and
Technology Inc.) returns once again to present an extra day of
pre-conference seminars.
In the morning
Total Network Security
In the Afternoon
How to Secure a Web Site
Dr Hancock continues to be one of the most popular and engaging speakers
in the world. An experienced computer and network designer/engineer he
has thousands of network designs to his credit. He has designed and
re-engineered networks for many of the Fortune 1000 as well as many
international companies and governments with system counts from 2 to
over 500,000. Bill was advisor to the White House for the installation
of the Executive Office of the President's dial-up security facilities
and Internet connection. He has written 24 books on computer networking
and security and has written articles for Data Communications Magazine,
DEC professional, Digital News, The Wall Street Journal, The Dallas
Morning News, IEEE Networks, Network World, Network Security and many
others. He currently writes a regular column in both Digital News and
Review and Network Security magazines.
The COMPSEC 97 Exhibition
Your chance to promote your product or visit companies producing the
latest hardware, software and techniques with advice from some of the
best names in IT security.
If you wish to exhibit at COMPSEC 97, call Alex Verhoeven now on
Tel: +44 (0) 1865 843829.
Fax: +44 (0) 1865 843971
E-mail: a.verhoeven@elsevier.co.uk
COMPSEC '97
DAY 1 - Wednesday 5th November 1997
9.00 KEYNOTE
Infosec Folk Art and Beyond
Donn Parker, SRI Consulting
INTERNET/INTRANET
Flemming Room
10.00
Internet E-mail Security
Peter Wood, First Base
11.00 COFFEE
11.30
Some Observations on Vulnerabilities
Prof. Eugene Spafford, Purdue University
12.30 LUNCH Compsec Exhibition
2.00
Intranet Firewalls
Dr. Bill Hancock, Network 1
3.00
Internet Holes - Eliminating IP Address Forgery
Dr. Fred Cohen, Sandia National Labs.
4.00 TEA
4.30
IP Security - Internet, Intranet and Beyond
Marius Nacht, Checkpoint Software Technologies Inc.
SECURITY STRATEGY
Westminster Room
10.00
Delivering Manageable Security to the Desktop
John Sherwood, Sherwood Associates
11.00 COFFEE
11.30
The Role of Trusted Third Parties - The UK Approach
Nigel Hickson, Department of Trade and Industry
12.30 LUNCH Compsec Exhibition
2.00
What are Certification Authorities and What are They Liable For
Tom Parker, ICL
3.00
The Enemy Everywhere
Michael Bacon, KPMG
4.00 TEA
4.30
Look Back in Wonder - A History of Infosec
Chris Amery, Zergo
ENCRYPTION
St. James' Room
10.00
Lessons From History
Prof. Harold Highland, Compulit Inc.
11.00 COFFEE
11.30
20 Years of DES
Dr. Carl Meyer, IBM
12.30 LUNCH Compsec Exhibition
2.00
Crypto System Initialization - An Update
Dr. Carl Meyer, IBM
3.00
Internet Encryption
Paul Docherty, Portcullis
4.00 TEA
4.30
Key Recovery - Why, How, Who?
Andy Clarke, Sapher Servers
VIRUSES
Fleet Room
10.00
Contracting a Macro Virus Whilst Surfing the Net
Dr. David Aubrey Jones, Reflex Magnetics
11.00 COFFEE
11.30
Virus Certification
Sarah Gordon, IBM
12.30 LUNCH Compsec Exhibition
IT AUDIT
Fleet Room
2.00
Advanced IT Auditing: Selecting and Testing the Right Controls
Keith Osbourne, ICL
3.00
COBIT - Audit Guidance on Effective Implementation
Vernon Poole, Aid To Industry
4.00 TEA
4.30
Using Automated Tools to Audit Novell Security
Paul Williams, Arthur Andersen
5.30 CLOSE
5.30 - 7.00 EVENING RECEPTION SPONSORED BY OUR EXHIBITORS
DAY 2 - Thursday 6th November 1996
9.00 KEYNOTE
Intrusion Detection And Response
Dr. Fred Cohen, Sandia National Labs
HACKER METHODS
Flemming Room
10.00
Update on the State of Play in the Hacker Community
Ken Lindup, SRI International
11.00 COFFEE
11.30
`Sneaking Through the Backdoor' The Technical Tricks of Hacking
Neil Barrett, Bull Information Systems
12.30 LUNCH Compsec Exhibition
COMS SECURITY / PHREAKING
Flemming Room
1.30
Computer Related Fraud and its Evolution Within Telephony
Tom Mulhall, BT
2.30
Telco Fraud Including PBX's - The Gory Details!
Peter Hoath, BT
3.30 TEA
4.00
PBX Fraud The Final Solution - Detection, Deterrent and Countermeasures
Tom Mulhall and Peter Hoath, BT
WINDOWS/NT SECURITY
Westminster Room
10.00
Windows/NT Security Today and in the Future
Peter Birch, Microsoft
11.00 COFFEE
11.30
Securing Windows NT in Today's Networking Environment
Dr. Gene Schultz, SRI International
12.30 LUNCH Compsec Exhibition
OPEN SYSTEMS
Westminster Room
1.30
Guy Martin
Multi Platform Security, SunSoft
2.30
X/Open Security
Dean Adams
3.30 TEA
4.00
Unix Security
Suleiman Shehu, Zergo
SECURITY MANAGEMENT
St. James' Room
10.00
Policies Alone do not Constitute a Sufficient Awareness Effort
Charles Cresson Wood, Baseline Software
11.00 COFFEE
11.30
Addressing Your Information Security Skills Shortage
Bill Pepper, Zergo
DIRECTOR'S BRIEFING
St. James' Room
The Importance of Information Security
Rod Parkin, RKP Associates
Electronic Commerce - The Way Forward
Terry Dosdale, Axiom Services
Security - Who Cares?
Martin Smith, The Security Company
Managing Security For Outsourcing Contracts
John Sherwood, Sherwood Associates
DISASTER RECOVERY
Fleet Room
10.00
Bang Goes Your Business
Michael Bacon, KPMG
11.00 COFFEE
11.30
Business Continuity and Beyond
Nigel Ghent, Comdisco
12.30 LUNCH Compsec Exhibition
IT AUDIT
Fleet Room
1.30
Auditing NT Servers
Peter Wood, First Base
2.30
Auditing the IT Security Function
Keith Osbourne, ICL
3.30 TEA
4.00
Key Security Pointers With CA-ACF2
Norman Crocker, Information Security Consulting
5.00 CLOSE (Directors' Briefing 5.30 Close)
DAY 3 - Friday 7th November 1996
9.00 KEYNOTE
Creating A Security Culture
Martin Smith, The Security Company & Heather Wilson, The Change Company
NETWORK SECURITY
Flemming Room
10.00
Penetration Testing
Gary Hardy, Zergo
11.00 COFFEE
11.30
Securing Third Party Connections
Dr. Gene Schultz, SRI Inc.
12.30 LUNCH
1.30
Information Flow Within the Globally Connected Environment
Sarah Gordon, IBM
2.30
Securing Lotus Notes 4.5
P.J.Corum, The Corum Group
3.30 TEA
ELECTRONIC COMMERCE
Westminster Room
10.00
The Strategic Value of Infosec in Business
Donn Parker, SRI Consulting
11.00 COFFEE
11.30
Essential Controls for Internet Electronic Commerce
Charles Cresson Wood, Baseline Software
12.30 LUNCH
INFORMATION WARFARE
Westminster Room
1.30
Information Warfare and Defending the UK Nation State
Michael Corcoron, Defence Research Agency
2.30
Penetration Testing and Red Teaming
Andrew Jones, Defence Research Agency
TECHNOLOGY ISSUES
St James' Room
10.00
A Comparison Between Java and ActiveX Security
David Hopwood, Network Security Consultant
11.00 COFFEE
11.30
Java Applets - The Security Issues
P.J. Corum, The Corum Group
12.30 LUNCH
St. James' Room
1.30
Intelligent Agents
t.b.a.
2.30
Smartcards - Is Britain Getting Smarter?
Alan Laird, Bull Information Systems
LEGAL ISSUES
Fleet Room
10.00
The Internet - A Legal Quagmire
Mark Crichard, Garretts
11.00 COFFEE
11.30
Software Reliability - The Legal Issues
Graham Smith, Bird and Bird
12.30 LUNCH
THE YEAR 2000
Fleet Room
1.30
The Year 2000 Problem
Taskforce 2000
2.30
The Year 2000 - The Other Problem: Embedded Systems
Alasdair Kemp, IEE
3.30 TEA
4.00 CLOSING ADDRESS
Blaming the Victim, Prof. Eugene Spafford, Purdue University
5.00 CLOSE
=================================================
PRIORITY ORDER FORM
Please register the following for:
COMPSEC International 97 (PCS46+B1)
Please register the following for:
Directors' Briefing - 6th November (PCS47+B1)
Please register the following for:
Pre-COMPSEC Sessions with Dr. Bill Hancock - 4th November
Surname (Prof/Dr/Mr/Ms)
First name
Job title
Organisation
address
Post/Zip code
Country
Tel
Fax
E-mail
company activity
special dietary requirements
Registration fee for COMPSEC 97
- #1050+ VAT@17.5% = #1233.75
Registration fee for the Director's Briefing
#95+VAT@17.5% = #111.63
(Directors' Briefing is FREE to COMPSEC Delegates)
Bill Hancock - Pre-Compsec Seminars
Total Network Security (PCS13+B1)
How to Secure a Web Site (PCS15+B1)
COMPSEC delegate - #75+VAT@17.5% = #88.13
Non-COMPSEC delegate - #125+VAT@17.5% =#146.88
Membership Discounted registration fee for ISACA(EDPAA)/BCSCASG/IT
Faculty of ICAEW/IIA (Individual members)
- #925+ VAT@17.5%=#1086.88
(please include membership no.)Please complete the form in BLOCK
CAPITALS
Fax registrations to +44 (0) 1865 843958
(please photocopy for multiple registrations)
Total amount payable including VAT....................
I enclose a cheque/Eurocheque payable to Elsevier Science Ltd.
Please invoice me
Purchase order number
I have arranged a bank transfer to:
Elsevier Science Ltd. National Westminster Bank plc, 21 Lombard Street,
London EC3P 3AR, UK.
(Account number 95800379 - Sort Code 60 00 01)Please charge my:
ACCESS/VISA/MASTERCARD/EUROCARD
(delete as appropriate)
Card number
Expiry date
Todays date
signature
(name & address if different to above)
I am interested in exhibiting, please send me details (PCS48+C5)
Please send me a copy of your Computer Security/Audit publications
catalogue (PCS+A1)
Please return completed form to
Amy Richardson,
COMPSEC International 97
Elsevier Advanced Technology
The Boulevard,
Langford Lane
Kidlington
Oxford OX5 1GB, UK
Tel: +44 (0) 1865 843643
Fax: +44 (0) 1865 843958
E-mail: a.richardson@elsevier.co.uk
Our reference (please quote on all correspondence)
CCS461E/
=================================================
------------------------------
Date: Wed, 9 Jul 1997 16:02:44 GMT
From: jackson@usenix.ORG (Jackson Dodd)
Subject: 7th USENIX Security Symposium - Call for Papers
X-Digest: Volume 10 : Issue 89
ANNOUNCEMENT AND CALL FOR PAPERS
7th USENIX Security Symposium
January 26-29, 1998
Marriott Hotel-- San Antonio, Texas
Sponsored by the USENIX Association, the UNIX and Advanced Computing
Systems Professional and Technical Association
In cooperation with: The CERT Coordination Center.
Important Dates for Refereed Papers
Papers due: September 9, 1997
Author notification: October 8, 1997
Camera-ready final papers due: December 9, 1997
Registration Materials Available: End October, 1997
(Authors, see "How to Submit a Refereed Paper" below.)
PROGRAM CHAIR
Avi Rubin, AT&T Labs - Research
PROGRAM COMMITTEE
Carlisle Adams, Nortel
Dave Balenson, Trusted Information Systems
Steve Bellovin, AT&T Research
Dan Boneh, Bellcore
Diane Coe, Concept5 Technologies
Ed Felten, Princeton University
Li Gong, JavaSoft
Peter Honeyman, CITI, University of Michigan
Hugo Krawczyk, IBM Watson Labs
Jack Lacy, AT&T Research
Hilarie Orman, DARPA/ITO
Mike Reiter, AT&T Research
David Wagner, University of California, Berkeley
READERS
Katherine T. Fithen, CERT
Trent Jaeger, IBM Watson Labs
Invited talks coordinator: Greg Rose, Qualcomm Australia
Conference home page: <http://www.usenix.org/sec/sec98.html>
OVERVIEW
The goal of this symposium is to bring together researchers,
practitioners, system programmers, and others interested in the
latest advances in security and applications of cryptography.
This will be a four day symposium with two days of tutorials,
followed by two days of refereed paper presentations, invited talks,
works-in-progress presentations, and panel discussions.
TUTORIALS Monday and Tuesday, January 26-27
Tutorials for both technical staff and managers will provide
immediately useful, practical information on topics such as local and
network security precautions, what cryptography can and cannot do,
security mechanisms and policies, firewalls and monitoring systems.
If you are interested in proposing a tutorial, contact the tutorial
coordinator, Dan Klein: phone (412)421-2332 email <dvk@usenix.org>.
TECHNICAL SESSIONS
Wednesday and Thursday, January 28-29
In addition to the keynote presentation, the technical program includes
refereed papers, invited talks, a Works-in-Progress session, and panel
sessions. There will be Birds-of-a-Feather sessions the last two
evenings. You are invited to make suggestions to the program committee
via email to <security-pc@usenix.org>.
Papers that have been formally reviewed and accepted will be presented
during the symposium and published in the symposium proceedings,
published by USENIX and provided free to technical session attendees.
Additional copies will be available for purchase from USENIX.
SYMPOSIUM TOPICS
Refereed paper submissions are being solicited in areas including but
not limited to:
* Adaptive security and system management
* Analysis of malicious code
* Applications of cryptographic techniques
* Attacks against networks/machines
* Computer misuse and anomaly detection
* Copyright protection (technical solutions)
* Cryptographic & other security tools
* File and file system security
* Network security
* New firewall technologies
* Security in heterogeneous environments
* Security incident investigation and response
* Security of Mobile Code
* User/system authentication
* World Wide Web security
Note that this symposium is not about new codes, ciphers, nor
cryptanalysis for its own sake.
Papers must represent novel scientific contributions in computer
security with direct relevance to the engineering of secure systems
for the commercial sector.
HOW TO SUBMIT A REFEREED PAPER
(Please read carefully.)
The guidelines for submission are a bit different from previous
years. Authors must submit a mature paper in postscript format.
Any incomplete sections (there shouldn't be many) should be
outlined in enough detail to make it clear that they could be
finished easily. Full papers are encouraged, and should be about
8 to 15 typeset pages. Submissions must be received by
September 9, 1997.
Along with your paper, please submit a separate email message
containing the title, all authors, and their complete contact
information (phone, fax, postal address, email), including an
indication of which author is the contact author.
Authors will be notified of acceptance on October 8, 1997.
All submissions will be judged on originality, relevance, and
correctness. Each accepted submission may be assigned a member
of the program committee to act as its shepherd through the
preparation of the final paper. The assigned member will act
as a conduit for feedback from the committee to the authors.
Camera-ready final papers are due on December 9, 1997.
If you would like to receive detailed guidelines for submission
and examples of extended abstracts, you may send email to:
<securityauthors@usenix.org>
or telephone the USENIX Association office at (510) 528-8649.
The Security Symposium, like most conferences and journals,
requires that papers not be submitted simultaneously to another
conference or publication and that submitted papers not be
previously or subsequently published elsewhere. Papers
accompanied by non-disclosure agreement forms are not
acceptable and will be returned to the author(s) unread.
All submissions are held in the highest confidentiality prior
to publication in the Proceedings, both as a matter of policy
and in accord with the U.S. Copyright Act of 1976.
There will be one or two prizes awarded for best paper(s).
WHERE TO SUBMIT
For reliability, please send one copy of your paper to the program
committee via each of the following two methods. All submissions
will be acknowledged.
o Email Postscript to: securitypapers@usenix.org
o Send a hard copy to:
Security Symposium
USENIX
2560 Ninth St., Ste. #215
Berkeley CA 94710
U.S.A.
Phone: (510) 528-8649
Fax: (510) 548-5738
Vendor Exhibits
Demonstrate your security product to our technically astute attendees
responsible for security at their sites. We invite you to take part
in the Vendor Display. The table-top display allows you to meet
with attendees informally and demonstrate in detail your security
solutions.
Contact: Cynthia Deno
Email: cynthia@usenix.org
Phone: 408.335.9445
Fax: 408.335.5327
Works-in-Progress Session (WIPs)
The last session of the symposium will be a Works-in-Progress session
consisting of five minute presentations. Speakers should provide a one
or two paragraph abstract to the program chair by 6:00 pm on January
28, 1998 at the conference. These should be provided in person, not via
email. The chair will post the schedule of presentations by noon on the
29th. Experience at other conferences has shown that usually, all of
them are accepted. The five minute time limit will be strictly enforced.
INVITED TALKS
There will be several invited talks at the conference in parallel with
the refereed papers. If you have suggestions for possible speakers,
please send them to <security@usenix.org>.
REGISTRATION MATERIALS
Materials containing all details of the technical and tutorial
programs, registration fees and forms, and hotel information will be
available at the end of October 1997. To receive the registration
materials, please contact:
USENIX Conference Office
22672 Lambert Street, Suite 613
Lake Forest, CA USA 92630
Phone: (714) 588-8649
Fax: (714) 588-9706
Email: <conference@usenix.org>
Information can also be found under the Conference home page:
<http://www.usenix.org/sec/sec98.html>.
[Moderator's note: Due to the upheavals this end, I think this posting
misses the cut-off date for paper proposals. Check the web site ASAP
if interested.]
------------------------------
Date: Wed, 23 Jul 1997 11:53:10 +0100
From: "Alie" alie@virusbtn.com
Subject: Virus Bulletin Conference -- VB'97
X-Digest: Volume 10 : Issue 89
The Virus Bulletin International conference is now in it's seventh year.
Our annual event is recognised as the world's leading event to address the
computer virus threat.
VB'97 will run as two parallel tracks, one corporate and one technical, and
is being held at The Fairmont Hotel, San Francisco, USA on 2/3 October
1997. Over 300 delegates are expected to attend the presentations led by a
panel of internationally renowned virus experts.
The VB'97 exhibition will run alongside the programme, featuring the
world's leading A/V vendors. Confirmed exhibitors include McAfee, Dr
Solomon's Software, Sophos, Command Software, NCSA, IBM, Integralis, Trend,
DataFellows, and Elsevier.
Throughout VB'97 delegates will have every opportunity to meet the industry
experts and speakers at the conference. Our social programme includes a
welcome drinks reception and spectacular black tie Gala Dinner.
Virus Bulletin is an independent monthly journal which has been dedicated
to inform, educate and report to a world-wide readership of IT
professionals, on all aspects of the computer virus threat and the industry
that fights to combat it.
If you would like to receive a brochure for VB'97 or would like further
information on Virus Bulletin please contact me (Alie@virusbtn.com) or visit
our web page at http://www.virusbtn.com/.
------------------------------
Date: Mon, 11 Aug 97 14:37:39 -0500
From: Craig Wolynez <legaltech@ljextra.com>
Subject: Legal Tech Intranet/Extranet Conference ^
X-Digest: Volume 10 : Issue 89
********************************************************
** Advance Notice -- The First Annual **
** Legal Tech Internet/Intranet/Extranet Conference **
** September 25 and 26 at the New York Hilton **
********************************************************
Law Technology Product News, Law Journal EXTRA! and Corporate
Presentations are pleased to invite you to a very special conference and
exhibit on law firm technology -- The First Annual Legal Tech
Internet/Intranet/Extranet Conference with Exhibits, to be held on
September 25 and 26 at the New York Hilton. We hope you won't miss this
opportunity to find out more about the most significant technological
development in the legal profession in many years.
Since we are limiting the audience to approximately 350 people, we are
notifying you in advance to allow members of the online community and
their firms to register while we can still guarantee that space is
available. We ask that you e-mail us at legaltech@ljx.com or register at
http://www.ljx.com/legaltech within the next few weeks to reserve your
seat. You can also phone (212) 545-6143. We will be publishing an
announcement in print shortly.
Legal Tech Internet is a unique, interactive seminar devoted exclusively
to the dynamic change in law practice resulting from today's intranet and
extranet technology. These exciting new developments allow law firms to
develop a complete communications strategy on two levels-- within the
firm as well as between the firm and its clients -- something unheard of
just a few years ago.
The Legal Tech Internet conference and exhibits will bring you the most
advanced, important and productive uses of the intranet and extranet
technology and teach you how to harness the power of the internet to
ensure that your firm stays on the cutting edge. We have a distinguished
faculty of lawyers, consultants and select vendors who will provide
demonstrations of the software and systems discussed in the conference
sessions. Breakout sessions with actual case study presentations will
give participants an opportunity to see just how this exceptional
technology is being used. Details on the faculty members and program
schedule are available at http://www.ljx.com/legaltech where you can also
download the complete seminar brochure in .pdf format.
So that you can take full advantage of these extraordinary presentations,
we must limit the number of registrants from each firm. The fee is $350,
and includes attendance at the conference, the breakout sessions,
exhibits, luncheon on the first day and breakfast. Please let us know if
you will be attending as soon as possible so that we can ensure a place
for you.
We look forward to seeing you in September.
Barbara Lamm
Law Journal EXTRA!
Legal Tech Internet/Intranet/Extranet
Web: http://www.ljx.com/legaltech
E-Mail: legaltech@ljx.com
Phone: (212) 545-6143
------------------------------
Date: 23 Jun 1997 13:55:07 +1000
From: proff@profane.iq.org (Julian Assange)
Subject: Extract: _Underground_ new book on international computer crime - "The WANK worm"
X-Digest: Volume 10 : Issue 89
Anyone read this book? Apparently the first in-depth investigation
into the international computer underground to come out of the
Southern-Hemisphere - or so I'm told :) - JA
Underground; Tales of Hacking, Madness and Obsession on the Electronic
Frontier, by Suelette Dreyfus; published by Mandarin (Random House
Australia); (P) 475 pages with bib. http://www.underground-book.com/
Edited-down extract from Underground - The WANK Worm
Extracted from Chapter 1 - "10, 9, 8, 7, 6, 5, 3, 2, 1"
Somebody's out there, somebody's waiting
Somebody's trying to tell me something
from 'Somebody's Trying to Tell Me Something', on 10, 9, 8, 7, 6, 5, 4, 3,
2, 1 by Midnight Oil
Monday, 16 October 1989
Kennedy Space Center, Florida
NASA buzzed with the excitement of a launch. Galileo was finally going to
Jupiter.
Administrators and scientists in the world's most prestigious space agency
had spent years trying to get the unmanned probe into space. Now, on
Tuesday, 17 October, if all went well, the five astronauts in the Atlantis
space shuttle would blast off from the Kennedy Space Center at Cape
Canaveral, Florida, with Galileo in tow. On the team's fifth orbit, as the
shuttle floated 295 kilometres above the Gulf of Mexico, the crew would
liberate the three-tonne space probe.
An hour later, as Galileo skated safely away from the shuttle, the probe's
32500 pound booster system would fire up and NASA staff would watch this
exquisite piece of human ingenuity embark on a six-year mission to the
largest planet in the solar system. Galileo would take a necessarily
circuitous route, flying by Venus once and Earth twice in a gravitational
slingshot effort to get up enough momentum to reach Jupiter.
NASA's finest minds had wrestled for years with the problem of exactly how
to get the probe across the solar system. Solar power was one option. But if
Jupiter was a long way from Earth, it was even further from the Sun - 778.3
million kilometres to be exact. Galileo would need ridiculously large solar
panels to generate enough power for its instruments at such a distance from
the Sun. In the end, NASA's engineers decided on a tried if not true earthly
energy source: nuclear power.
Nuclear power was perfect for space, a giant void free of human life which
could play host to a bit of radioactive plutonium 238 dioxide. The plutonium
was compact for the amount of energy it gave off - and it lasted a long time.
It seemed logical enough. Pop just under 24 kilograms of plutonium in a lead
box, let it heat up through its own decay, generate electricity for the
probe's instruments, and presto! Galileo would be on its way to investigate
Jupiter.
American anti-nuclear activists didn't quite see it that way. They figured
what goes up might come down ..NASA assured them Galileo's power pack was
quite safe. The agency spent about $50 million on tests which supposedly
proved the probe's generators were very safe. They would survive intact in
the face of any number of terrible explosions, mishaps and accidents. NASA
told journalists that the odds of a plutonium release due to 'inadvertent
atmospheric re-entry' were 1 in 2 million. The likelihood of a plutonium
radiation leak as a result of a launch disaster was a reassuring 1 in 2700.
NASA's Goddard Space Flight Center, Greenbelt, Maryland
Across the vast NASA empire, reaching from Maryland to California, from
Europe to Japan, NASA workers greeted each other, checked their in-trays for
mail, got their cups of coffee, settled into their chairs and tried to login
to their computers for a day of solving complex physics problems. But many
of the computer systems were behaving very strangely.
>From the moment staff logged in, it was clear that someone - or something - had
taken over. Instead of the usual system's official identification banner,
they were startled to find the following message staring them in the face:
W O R M S A G A I N S T N U C L E A R K I L L E R S
_______________________________________________________________
\__ ____________ _____ ________ ____ ____ __ _____/
\ \ \ /\ / / / /\ \ | \ \ | | | | / / /
\ \ \ / \ / / / /__\ \ | |\ \ | | | |/ / /
\ \ \/ /\ \/ / / ______ \ | | \ \| | | |\ \ /
\_\ /__\ /____/ /______\ \____| |__\ | |____| |_\ \_/
\___________________________________________________/
\ /
\ Your System Has Been Officically WANKed /
\_____________________________________________/
You talk of times of peace for all, and then prepare for war.
This was not going to be a good day for the guys down at the NASA SPAN
computer network office.
This was not going to be a good day for John McMahon.
--
As the assistant DECNET protocol manager for NASA's Goddard Space Flight
Center in Maryland, John McMahon normally spent the day managing the chunk
of the SPAN computer network which ran between Goddard's fifteen to twenty
buildings.
McMahon worked for Code 630.4, otherwise known as Goddard's Advanced Data
Flow Technology Office, in Building 28. Goddard scientists would call him up
for help with their computers. Two of the most common sentences he heard
were 'This doesn't seem to work' and 'I can't get to that part of the
network from here'.
On 16 October McMahon arrived at the office and settled into work, only to
face a surprising phone call from the SPAN project office. Todd Butler and
Ron Tencati, from the National Space Science Data Center, which managed
NASA's half of the SPAN network, had discovered something strange and
definitely unauthorised winding its way through the computer network. It
looked like a computer worm.
A computer worm is a little like a computer virus. It invades computer
systems, interfering with their normal functions. It travels along any
available compatible computer network and stops to knock at the door of
systems attached to that network. If there is a hole in the security of the
computer system, it will crawl through and enter the system. When it does
this, it might have instructions to do any number of things, from sending
computer users a message to trying to take over the system. What makes a
worm different from other computer programs, such as viruses, is that it is
self-propagating. It propels itself forward, wiggles into a new system and
propagates itself at the new site. Unlike a virus, a worm doesn't latch onto
a data file or a program. It is autonomous.
At the SPAN centre, things were becoming hectic. The worm was spreading
through more and more systems and the phones were beginning to ring every
few minutes. NASA computers were getting hit all over the place.
The SPAN project staff needed more arms. They were simultaneously trying to
calm callers and concentrate on developing an analysis of the alien program.
Was the thing a practical joke or a time bomb just waiting to go off? Who
was behind this?
NASA was working in an information void when it came to WANK. Some staff
knew of the protesters' action down at the Space Center, but nothing could
have prepared them for this. NASA officials were confident enough about a
link between the protests against Galileo and the attack on NASA's computers
to speculate publicly that the two were related. It seemed a reasonable
likelihood, but there were still plenty of unanswered questions.
Callers coming into the SPAN office were worried. People at the other end of
the phone were scared. Many of the calls came from network managers who took
care of a piece of SPAN at a specific NASA site, such as the Marshall Space
Flight Center. Some were panicking; others spoke in a sort of monotone,
flattened by a morning of calls from 25 different hysterical system
administrators. A manager could lose his job over something like this.
Most of the callers to the SPAN head office were starved for information.
How did this rogue worm get into their computers? Was it malicious? Would it
destroy all the scientific data it came into contact with? What could be
done to kill it?
NASA stored a great deal of valuable information on its SPAN computers. None
of it was supposed to be classified, but the data on those computers is
extremely valuable. Millions of man-hours go into gathering and analysing
it. So the crisis team which had formed in the NASA SPAN project office, was
alarmed when reports of massive data destruction starting coming in. People
were phoning to say that the worm was erasing files.
It was every computer manager's worst nightmare, and it looked as though the
crisis team's darkest fears were about to be confirmed.
Yet the worm was behaving inconsistently. On some computers it would only
send anonymous messages, some of them funny, some bizarre and a few quite
rude or obscene. No sooner would a user login than a message would flash
across his or her screen:
Remember, even if you win the rat race-you're still a rat.
Or perhaps they were graced with some bad humour:
Nothing is faster than the speed of light...
To prove this to yourself, try opening the refrigerator
door before the light comes on.
Other users were treated to anti-authoritarian observations of the paranoid:
The FBI is watching YOU.
or
Vote anarchist.
But the worm did not appear to be erasing files on these systems. Perhaps
the seemingly random file-erasing trick was a portent of things to come - just
a small taste of what might happen at a particular time, such as midnight.
Perhaps an unusual keystroke by an unwitting computer user on those systems
which seemed only mildly affected could trigger something in the worm. One
keystroke might begin an irreversible chain of commands to erase everything
on that system.
The NASA SPAN computer team were in a race with the worm. Each minute they
spent trying to figure out what it did, the worm was pushing forward, ever
deeper into NASA's computer network. Every hour NASA spent developing a
cure, the worm spent searching, probing, breaking and entering. A day's
delay in getting the cure out to all the systems could mean dozens of new
worm invasions doing God knows what in vulnerable computers. The SPAN team
had to dissect this thing completely, and they had to do it fast.
Some computer network managers were badly shaken. The SPAN office received a
call from NASA's Jet Propulsion Laboratories in California, an important
NASA centre with 6500 employees and close ties to California Institute of
Technology (Caltech).
JPL was pulling itself off the network.
This worm was too much of a risk. The only safe option was to isolate their
computers. There would be no SPAN DEC-based communications with the rest of
NASA until the crisis was under control. This made things harder for the
SPAN team; getting a worm exterminating program out to JPL, like other sites
which had cut their connection to SPAN, was going to be that much tougher.
Everything had to be done over the phone.
Worse, JPL was one of five routing centres for NASA's SPAN computer network.
It was like the centre of a wheel, with a dozen spokes branching off - each
leading to another SPAN site. All these places, known as tailsites, depended
on the lab site for their connections into SPAN. When JPL pulled itself off
the network, the tailsites went down too.
It was a serious problem for the people in the SPAN office back in Virginia.
To Ron Tencati, head of security for NASA SPAN, taking a routing centre
off-line was a major issue. But his hands were tied. The SPAN office
exercised central authority over the wide area network, but it couldn't
dictate how individual field centres dealt with the worm. That was each
centre's own decision. The SPAN team could only give them advice and rush to
develop a way to poison the worm.
Next or Previous
The SPAN office called John McMahon again, this time with a more urgent
request. Would he come over to help handle the crisis?
The SPAN centre was only 800 metres away from McMahon's office. His boss,
Jerome Bennett, the DECNET protocol manager, gave the nod. McMahon would be
on loan until the crisis was under control.
When he got to Building 26, home of the NASA SPAN project office, McMahon
became part of a core NASA crisis team .. At first the core team seemed only
to include NASA people and to be largely based at Goddard. But as the day
wore on, new people from other parts of the US government would join the
team.
The worm had spread outside NASA.
It had also attacked the US Department of Energy's worldwide High-Energy
Physics' Network of computers. Known as HEPNET, it was another piece of the
overall SPAN network, along with Euro-HEPNET and Euro-SPAN. The NASA and DOE
computer networks of DEC computers crisscrossed at a number of places. A
research laboratory might, for example, need to have access to computers
from both HEPNET and NASA SPAN. For convenience, the lab might just connect
the two networks. The effect as far as the worm was concerned was that
NASA's SPAN and DOE's HEPNET were in fact just one giant computer network,
all of which the worm could invade.
The Department of Energy keeps classified information on its computers. Very
classified information. There are two groups in DOE: the people who do
research on civilian energy projects and the people who make atomic bombs.
So DOE takes security seriously, as in 'threat to national security'
seriously. Although HEPNET wasn't meant to be carrying any classified
information across its wires, DOE responded with military efficiency when
its computer managers discovered the invader. They grabbed the one guy who
knew a lot about computer security on VMS systems and put him on the case:
Kevin Oberman.
Even as the WANK worm coursed through NASA, it was launching an aggressive
attack on DOE's Fermi National Accelerator Laboratory, near Chicago. It had
broken into a number of computer systems there and the Fermilab people were
not happy. They called in CIAC, who contacted Oberman with an early morning
phone call on 16 October. They wanted him to analyse the WANK worm. They
wanted to know how dangerous it was. Most of all, they wanted to know what
to do about it.
The DOE people traced their first contact with the worm back to 14 October.
Further, they hypothesised, the worm had actually been launched the day
before, on Friday the 13th. Such an inauspicious day would, in Oberman's
opinion, have been in keeping with the type of humour exhibited by the
creator or creators of the worm.
Oberman began his own analysis of the worm, oblivious to the fact that 3200
kilometres away, on the other side of the continent, his colleague and
acquaintance John McMahon was doing exactly the same thing. ..
---
John McMahon's analysis suggested there were three versions of the WANK
worm. These versions, isolated from worm samples collected from the network,
were very similar, but each contained a few subtle differences. In McMahon's
view, these differences could not be explained by the way the worm recreated
itself at each site in order to spread. But why would the creator of the
worm release different versions? Why not just write one version properly and
fire it off? The worm wasn't just one incoming missile; it was a frenzied
attack. It was coming from all directions, at all sorts of different levels
within NASA's computers.
McMahon guessed that the worm's designer had released the different versions
at slightly different times. Maybe the creator released the worm, and then
discovered a bug. He fiddled with the worm a bit to correct the problem and
then released it again. Maybe he didn't like the way he had fixed the bug
the first time, so he changed it a little more and released it a third time.
In northern California, Kevin Oberman came to a different conclusion. He
believed there was in fact only one real version of the worm spiralling
through HEPNET and SPAN. The small variations in the different copies he
dissected seemed to stem from the worm's ability to learn and change as it
moved from computer to computer.
The worm circumnavigated the globe. It had reach into European sites, such
as CERN - formerly known as the European Centre for Nuclear Research - in
Switzerland, through to Goddard's computers in Maryland, on to Fermilab in
Chicago and propelled itself across the Pacific into the Riken Accelerator
Facility in Japan.
NASA officials told the media they believed the worm had been launched about
4.30 a.m. on Monday, 16 October.
They also believed it had originated in Europe, possibly in France ..
The WANK worm left a number of unanswered questions in its wake, a number of
loose ends which still puzzle John McMahon. Was the hacker behind the worm
really protesting against NASA's launch of the plutonium-powered Galileo
space probe? Did the use of the word 'WANK' - a most un-American word - mean the
hacker wasn't American? Why had the creator recreated the worm and released
it a second time? Why had no-one, no political or other group, claimed
responsibility for the WANK worm?
One of the many details which remained an enigma was contained in the
version of the worm used in the second attack. The worm's creator had
replaced the original process name, NETW_, with a new one, presumably to
thwart the anti-WANK program. McMahon figured the original process name
stood for 'netwank' - a reasonable guess at the hacker's intended meaning. The
new process name, however, left everyone on the SPAN team scratching their
heads: it didn't seem to stand for anything. The letters formed an unlikely
set of initials for someone's name. No-one recognised it as an acronym for a
saying or an organisation. And it certainly wasn't a proper word in the
English language. It was a complete mystery why the creator of the WANK
worm, the hacker who launched an invasion into hundreds of NASA and DOE
computers, should choose this weird word. The word was 'OILZ'.
It is not surprising the SPAN security team would miss the mark. It is not
surprising, for example, that these officials should to this day be
pronouncing the 'Oilz' version of the WANK worm as 'oil zee' .. nor that
they hypothesised the worm's creator chose the word 'Oilz' because the
modifications made to the last version made it slippery, perhaps even oily.
Likely as not, only an Australian would see the worm's link to the lyrics of
Midnight Oil.
This was the world's first worm with a political message, and the second
major worm in the history of the worldwide computer networks...
Yet, NASA and the US Department of Energy were half a world away from
finding the creator of the WANK worm. Even as investigators sniffed around
electronic trails leading to France, it appears the perpetrator was hiding
behind his computer and modem in Australia ...
- ---------------------------------------------------------------------------
Underground; Tales of Hacking, Madness and Obsession on the Electronic
Frontier, by Suelette Dreyfus; published by Mandarin (Random House
Australia); (P) 475 pages with bib. http://www.underground-book.com/
- -
Prof. Julian Assange |If you want to build a ship, don't drum up people
|together to collect wood and don't assign them tasks
proff@iq.org |and work, but rather teach them to long for the endless
proff@gnu.ai.mit.edu |immensity of the sea. -- Antoine de Saint Exupery
------------------------------
End of VIRUS-L Digest [Volume 10 Issue 89]
******************************************
