DOCSLIB.ORG

Virus Bulletin, June 1990

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Virus Bulletin, June 1990 June 1990 ISSN 0956-9979 THE AUTHORITATIVE INTERNATIONAL PUBLICATION ON COMPUTER VIRUS PREVENTION, RECOGNITION AND REMOVAL Editor: Edward Wilding Technical Editor: Fridrik Skulason, University of Iceland Editorial Advisors: Jim Bates, Bates Associates, UK, Phil Crewe, Fingerprint, UK, Dr. Jon David, USA, David Ferbrache, Heriot-Watt University, UK, Dr. Bertil Fortrie, Data Encryption Technologies, Holland, Hans Gliss, Datenschutz Berater, West Germany, Ross M. Greenberg, Software Concepts Design, USA, Dr. Harold Joseph Highland, Compulit Microcomputer Security Evaluation Laboratory, USA, Dr. Jan Hruska, Sophos, UK, Dr. Keith Jackson, Walsham Contracts, UK, Owen Keane, Barrister, UK, Yisrael Radai, Hebrew University, Israel, John Laws, RSRE, UK, David T. Lindsay, Digital Equipment Corporation, UK, Martin Samociuk, Network Security Management, UK, John Sherwood, Sherwood Associates, UK, Roger Usher, Coopers&Lybrand, UK, Dr. Ken Wong, BIS Applied Systems, UK KNOWN IBM PC VIRUSES CONTENTS (UPDATE) 11 EDITORIAL TOOLS & TECHNIQUES Computer Viruses as Weapon Dynamic Decompression, Systems 2 LZEXE and the Virus Problem 12 PROCEDURES WORM PROGRAMS Training and Awareness 3 The Internet Worm - Action and Reaction 13 FEATURE ARTICLE PRODUCT REVIEW The Bulgarian Computer Viruses - ‘The Virus Factory’ 6 Certus - Tools To Fight Viruses With 18 ANTI-VIRUS SOFTWARE END-NOTES & NEWS 20 FOR IBM PCs 10 VIRUS BULLETIN ©1990 Virus Bulletin Ltd, England./90/$0.00+2.50 This bulletin is available only to qualified subscribers. No part of this publication may be reproduced, stored in a retrieval system, or transmitted by any form or by any means, electronic, magnetic, optical or photocopying, without the prior written permission of the publishers or a licence permitting restricted copying issued by the Copyright Licencing Agency. Page 2 VIRUS BULLETIN June 1990 Research in effective methods or strategies to remotely EDITORIAL introduce such viruses should be conducted. Efforts in this area should be focused on RF atmospheric signal transmis- sion such as performed in tactical military data communica- Computer Viruses as Weapons Systems tions.” There has been some speculation recently about military research into For some extraordinary reason, this project has been ‘farmed out’ to the use of virus programs to disrupt enemy computer and communi- private enterprise. Jim Vavrina, a computer security specialist with cations systems. Military electronic countermeasures (ECM) might, it the US Army Information Systems Software Centre who uploaded has been argued, encompass computer viruses, worms and other the message, says: “Admittedly, myself and my colleagues are quite forms of replicating attack programs. This speculation is almost surprised that something of this nature would be put on the streets for impossible to substantiate. In the UK for instance, electronic research and not use the expertise internally available.” intelligence (ELINT) and signals intelligence (SIGINT) are highly classified fields and no information about research and development Program Solicitation 90.2 might lead us to conclude that the US projects is made publicly available. Department of Defense has 1) been very slow to appreciate the virus threat and its implications for security and electronic warfare and Interception of enemy communications and cipher-breaking are the 2) regards the issue rather casually and believes it unnecessary to primary SIGINT and ELINT functions. Recent military computer use its immense ‘in-house’ resources for research and development security efforts have attempted to counter ‘leakage’ - the capacity for purposes. enemy intelligence to intercept information processed by computers. Leakage can occur through electromagnetic radiation emanating from Alternatively, Program Solicitation 90.2 could be regarded as a terminals, processors and cabling and this has led to the development classic example of disinformation to conceal the true extent of US of TEMPEST shielding designed to confound eavesdropping. military virus research. Another possible cause of leakage is the Trojan horse or ‘sleeper’ program designed to exploit covert channels and assist illicit communication to unauthorised parties. Viruses, worms and Trojans Morris Sentenced can be used to exploit covert channels and incoming software for Robert Morris has avoided a prison sentence for attacking the US high security computing systems is usually supplied as source code DARPA Internet network. In early May a Federal judge placed him for prior analysis. Covert channels are discussed in the US Depart- on three year’s probation, ordered him to complete 400 hours of ment of Defense Trusted Computer System Evaluation Criteria - the community service, and imposed a fine of $10,000 payable within ‘Orange Book’ - and are a major consideration in the design of secure twelve months. computer systems. * An interesting aspect of the case was the estimated level of damage Offensive Applications (assessed in US dollars) caused by the program. A report from John McAfee of the Computer Virus Industry Association claimed that the Securing information is a defensive measure. Military agencies are Internet worm had caused a staggering $96 million dollars of equally interested in offensive operations. This might involve damage. This report was dismissed as “grossly exaggerated and self- intercepting enemy communications and information and, if serving” by the Cornell commission of enquiry into the incident necessary, destroying or disrupting those facilities. The following headed by Mr. M Stuart Lynn. A figure of $200,000 quoted by Gene information appeared recently on the Virus-L conference: Spafford of the University of Purdue has been accepted as a realistic The US Department of Defense recently published a booklet estimate of the damage inflicted by most knowledgeable observers. titled PROGRAM SOLICITATION 90.2 FY-1990 SMALL As VB reported in April, hackers are still penetrating Internet and BUSINESS INNOVATION RESEARCH (SBIR) PROGRAM. according to some reports the network’s security is as lax as it was Page 45 contains project A90-217 ‘Computer Virus Elec- before the Morris program struck. There is still concern that known tronic Countermeasure (ECM)’. This project, for ‘exploratory bugs and trapdoors in this and other wide area networks remain development’ is a feasibility study to determine: unfixed, that issued ‘patches’ are being ignored by systems adminis- “The potential for using ‘computer viruses’ as an ECM trators and that manufacturers and vendors are failing to address technique against generic military communications systems/ network security. In the UK, the Joint Academic Network (JANET) nets. The goal shall be to determine the feasibility of remotely remains particularly vulnerable to security breaches with little introducing a virus into a system/net and analyzing its effects concerted effort being made to ‘plug the gaps’. on various subsystem components. The Morris sentence (widely regarded as lenient) will probably do DESCRIPTION: The purpose of this research shall be to little to deter network pranksters, either in the US or elsewhere. investigate potential use of computer viruses to achieve Under the circumstances a repeat of the Internet worm, or similar, traditional communications ECM effects in targeted communi- seems inevitable. cations systems. These effects can include data (information) * Trojan horses and covert channels will be the subject of a commis- disruption, denial, and deception, but other effects should sioned article to appear in VB, volume II. also be researched such as executable code in processors, memory storage management, etc. VIRUS BULLETIN ©1990 Virus Bulletin Ltd, England./90/$0.00+2.50 This bulletin is available only to qualified subscribers. No part of this publication may be reproduced, stored in a retrieval system, or transmitted by any form or by any means, electronic, magnetic, optical or photocopying, without the prior written permission of the publishers or a licence permitting restricted copying issued by the Copyright Licencing Agency. June 1990 VIRUS BULLETIN Page 3 PROCEDURES What Should Be Explained? This depends upon the computing experience of the audience. The most basic presentation might include the following points: Training and Awareness 1. A computer virus (never use the term ‘data virus’) is a program that modifies normal programs to include a copy of itself. Viruses also spread from one computer to another. This Computer viruses are created by people and are spread by can happen on a network or with stand-alone computers. people. There are no purely technical solutions to the virus Computer viruses are created by people to damage and disrupt problem because productivity depends upon people using computer systems. (Depending on the level of user knowledge, computers and software. Unless floppy disk drives are dis- it may be necessary to distinguish between programs and data. abled, the user will always be able to install software and Emphasise that pure data cannot spread viruses). execute it. 2. Viruses are particularly dangerous because they do not Thus, there is no point in implementing technical security reveal their presence until they ‘trigger’. After triggering, some measures if a) people will not use them and b) people fail to viruses destroy everything stored on the computer. understand why particular measures are necessary. 3. Programs (software) can spread viruses. In most office Good management depends upon clear and straightforward
Load more

Recommended publications
  • End-To-End Enterprise Encryption: a Look at Securezip® Technology
    End-to-End Enterprise Encryption: A Look at SecureZIP® Technology TECHNICAL WHITE PAPER WP 700.xxxx End-to-End Enterprise Encryption: A Look at SecureZIP Technology Table of Contents SecureZIP Executive Summary 3 SecureZIP: The Next Generation of ZIP 4 PKZIP: The Foundation for SecureZIP 4 Implementation of ZIP Encryption 5 Hybrid Cryptosystem 6 Crytopgraphic Calculation Sources 7 Digital Signing 7 In Step with the Data Protection Market’s Needs 7 Conclusion 8 WP-SZ-032609 | 2 End-to-End Enterprise Encryption: A Look at SecureZIP Technology End-to-End Enterprise Encryption: A Look at SecureZIP Technology Every day sensitive data is exchanged within your organization, both internally and with external partners. Personal health & insurance data of your employees is shared between your HR department and outside insurance carriers. Customer PII (Personally Identifiable Information) is transferred from your corporate headquarters to various offices around the world. Payment transaction data flows between your store locations and your payments processor. All of these instances involve sensitive data and regulated information that must be exchanged between systems, locations, and partners; a breach of any of them could lead to irreparable damage to your reputation and revenue. Organizations today must adopt a means for mitigating the internal and external risks of data breach and compromise. The required solution must support the exchange of data across operating systems to account for both the diversity of your own infrastructure and the unknown infrastructures of your customers, partners, and vendors. Moreover, that solution must integrate naturally into your existing workflows to keep operational cost and impact to minimum while still protecting data end-to-end.
    [Show full text]
  • Twenty Years of Berkeley Unix : from AT&T-Owned to Freely
    Twenty Years of Berkeley Unix : From AT&T-Owned to Freely Redistributable Marshall Kirk McKusick Early History Ken Thompson and Dennis Ritchie presented the first Unix paper at the Symposium on Operating Systems Principles at Purdue University in November 1973. Professor Bob Fabry, of the University of California at Berkeley, was in attendance and immediately became interested in obtaining a copy of the system to experiment with at Berkeley. At the time, Berkeley had only large mainframe computer systems doing batch processing, so the first order of business was to get a PDP-11/45 suitable for running with the then-current Version 4 of Unix. The Computer Science Department at Berkeley, together with the Mathematics Department and the Statistics Department, were able to jointly purchase a PDP-11/45. In January 1974, a Version 4 tape was delivered and Unix was installed by graduate student Keith Standiford. Although Ken Thompson at Purdue was not involved in the installation at Berkeley as he had been for most systems up to that time, his expertise was soon needed to determine the cause of several strange system crashes. Because Berkeley had only a 300-baud acoustic-coupled modem without auto answer capability, Thompson would call Standiford in the machine room and have him insert the phone into the modem; in this way Thompson was able to remotely debug crash dumps from New Jersey. Many of the crashes were caused by the disk controller's inability to reliably do overlapped seeks, contrary to the documentation. Berkeley's 11/45 was among the first systems that Thompson had encountered that had two disks on the same controller! Thompson's remote debugging was the first example of the cooperation that sprang up between Berkeley and Bell Labs.
    [Show full text]
  • The Basic Principles of Data Compression
    The Basic Principles of Data Compression Author: Conrad Chung, 2BrightSparks Introduction Internet users who download or upload files from/to the web, or use email to send or receive attachments will most likely have encountered files in compressed format. In this topic we will cover how compression works, the advantages and disadvantages of compression, as well as types of compression. What is Compression? Compression is the process of encoding data more efficiently to achieve a reduction in file size. One type of compression available is referred to as lossless compression. This means the compressed file will be restored exactly to its original state with no loss of data during the decompression process. This is essential to data compression as the file would be corrupted and unusable should data be lost. Another compression category which will not be covered in this article is “lossy” compression often used in multimedia files for music and images and where data is discarded. Lossless compression algorithms use statistic modeling techniques to reduce repetitive information in a file. Some of the methods may include removal of spacing characters, representing a string of repeated characters with a single character or replacing recurring characters with smaller bit sequences. Advantages/Disadvantages of Compression Compression of files offer many advantages. When compressed, the quantity of bits used to store the information is reduced. Files that are smaller in size will result in shorter transmission times when they are transferred on the Internet. Compressed files also take up less storage space. File compression can zip up several small files into a single file for more convenient email transmission.
    [Show full text]
  • Steganography and Vulnerabilities in Popular Archives Formats.| Nyxengine Nyx.Reversinglabs.Com
    Hiding in the Familiar: Steganography and Vulnerabilities in Popular Archives Formats.| NyxEngine nyx.reversinglabs.com Contents Introduction to NyxEngine ............................................................................................................................ 3 Introduction to ZIP file format ...................................................................................................................... 4 Introduction to steganography in ZIP archives ............................................................................................. 5 Steganography and file malformation security impacts ............................................................................... 8 References and tools .................................................................................................................................... 9 2 Introduction to NyxEngine Steganography1 is the art and science of writing hidden messages in such a way that no one, apart from the sender and intended recipient, suspects the existence of the message, a form of security through obscurity. When it comes to digital steganography no stone should be left unturned in the search for viable hidden data. Although digital steganography is commonly used to hide data inside multimedia files, a similar approach can be used to hide data in archives as well. Steganography imposes the following data hiding rule: Data must be hidden in such a fashion that the user has no clue about the hidden message or file's existence. This can be achieved by
    [Show full text]
  • The Release Engineering of Freebsd 4.4
    The Release Engineering of FreeBSD 4.4 Murray Stokely [email protected] Wind River Systems Abstract different pace, and with the general assumption that they This paper describes the approach used by the FreeBSD re- have first gone into FreeBSD-CURRENT and have been lease engineering team to make production-quality releases thoroughly tested by our user community. of the FreeBSD operating system. It details the methodol- In the interim period between releases, nightly snap- ogy used for the release of FreeBSD 4.4 and describes the shots are built automatically by the FreeBSD Project build tools available for those interested in producing customized machines and made available for download from ftp: FreeBSD releases for corporate rollouts or commercial pro- //stable.FreeBSD.org. The widespread availabil- ductization. ity of binary release snapshots, and the tendency of our user community to keep up with -STABLE development with CVSup and “make world”[8] helps to keep FreeBSD- 1 Introduction STABLE in a very reliable condition even before the qual- ity assurance activities ramp up pending a major release. The development of FreeBSD is a very open process. Bug reports and feature requests are continuously sub- FreeBSD is comprised of contributions from thousands of mitted by users throughout the release cycle. Problem people around the world. The FreeBSD Project provides reports are entered into our GNATS[9] database through anonymous CVS[1] access to the general public so that email, the send-pr(1) application, or via a web-based form. others can have access to log messages, diffs between de- In addition to the multitude of different technical mailing velopment branches, and other productivity enhancements lists about FreeBSD, the FreeBSD quality-assurance mail- that formal source code management provides.
    [Show full text]
  • Berkeley DB from Wikipedia, the Free Encyclopedia
    Berkeley DB From Wikipedia, the free encyclopedia Berkeley DB Original author(s) Margo Seltzer and Keith Bostic of Sleepycat Software Developer(s) Sleepycat Software, later Oracle Corporation Initial release 1994 Stable release 6.1 / July 10, 2014 Development status production Written in C Operating system Unix, Linux, Windows, AIX, Sun Solaris, SCO Unix, Mac OS Size ~1244 kB compiled on Windows x86 Type Embedded database License AGPLv3 Website www.oracle.com/us/products/database/berkeley-db /index.html (http://www.oracle.com/us/products/database/berkeley- db/index.html) Berkeley DB (BDB) is a software library that provides a high-performance embedded database for key/value data. Berkeley DB is written in C with API bindings for C++, C#, PHP, Java, Perl, Python, Ruby, Tcl, Smalltalk, and many other programming languages. BDB stores arbitrary key/data pairs as byte arrays, and supports multiple data items for a single key. Berkeley DB is not a relational database.[1] BDB can support thousands of simultaneous threads of control or concurrent processes manipulating databases as large as 256 terabytes,[2] on a wide variety of operating systems including most Unix- like and Windows systems, and real-time operating systems. "Berkeley DB" is also used as the common brand name for three distinct products: Oracle Berkeley DB, Berkeley DB Java Edition, and Berkeley DB XML. These three products all share a common ancestry and are currently under active development at Oracle Corporation. Contents 1 Origin 2 Architecture 3 Editions 4 Programs that use Berkeley DB 5 Licensing 5.1 Sleepycat License 6 References 7 External links Origin Berkeley DB originated at the University of California, Berkeley as part of BSD, Berkeley's version of the Unix operating system.
    [Show full text]
  • Copyright © 1992, by the Author(S). All Rights Reserved
    Copyright © 1992, by the author(s). All rights reserved. Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, to republish, to post on servers or to redistribute to lists, requires prior specific permission. AN IMPLEMENTATION OF A LOG-STRUCTURED FILE SYSTEM FOR UNIX by Margo Seltzer, Keith Bostic, Marshall Kirk McKusick, and Carl Staelin Memorandum No. UCB/ERL M92/134 3 December 1992 AN IMPLEMENTATION OF A LOG-STRUCTURED FILE SYSTEM FOR UNIX by Margo Seltzer, Keith Bostic, Marshall Kirk McKusick, and Carl Staelin Memorandum No. UCB/ERL M92/134 3 December 1992 ELECTRONICS RESEARCH LABORATORY College of Engineering University of California, Berkeley 94720 AN IMPLEMENTATION OF A LOG-STRUCTURED FILE SYSTEM FOR UNIX by Margo Seltzer, Keith Bostic, Marshall Kirk McKusick, and Carl Staelin Memorandum No. UCB/ERL M92/134 3 December 1992 ELECTRONICS RESEARCH LABORATORY College of Engineering University ofCalifornia, Berkeley 94720 An Implementation ofa Log-Structured File System for UNIX1 Margo Seltzer —University ofCalifornia, Berkeley Keith Bostic - University ofCalifornia, Berkeley Marshall Kirk McKusick —University ofCalifornia, Berkeley Carl Staelin - Hewlett-Packard Laboratories ABSTRACT Research results [ROSE91] demonstrate that a log-structured file system (LFS) offers the potential for dramatically improved write performance, faster recovery time, and faster file creation and deletion than traditional UNIX file systems. This paper presents a redesign and implementation of the Sprite [ROSE91] log-structured file system that is more robust and integrated into the vnode interface [KLEI86].
    [Show full text]
  • Archiving.Pdf
    Archiving Zip. Compression. Stuff like that. Written by Dan Gookin Published by Quantum Particle Bottling Co., Coeur d’Alene, ID, 83814 USA Copyright ©2008 by Quantum Particle Bottling Co., Inc. All Rights Reserved. This work cannot be reproduced or distributed without written permission of the copyright holder. Various copyrights and trademarks may or may not appear in this text. It is assumed that the trademark or copyright is owned by whoever owns it, and the use of that material here is in no way considered an infringement or abuse of the copyright or trademark. Further, there is. Oh, wait. Never mind. I’m just making all this up anyway. I’m not a lawyer. I hate lawyers. For additional information on this or other publications from Quantum Particle Bottling Co., please visit http://www. wambooli.com/ Second Edition December, 2008 Table of Contents Archiving .........................................................................................................2 What the Heck is Archiving? ............................................................................4 Historical Nonsense About Compressed Folders and ZIP Files ..........................5 The Bad Old Modem Days .............................................................................6 Packing Multiple Files Into a Single Library ..................................................6 Better than Library Files, Compressed Archives ............................................7 Enter the ARC file format ..............................................................................8
    [Show full text]
  • ES 201 684 V1.1.1 (1999-05) ETSI Standard
    Draft ES 201 684 V1.1.1 (1999-05) ETSI Standard Integrated Services Digital Network (ISDN); File Transfer Profile; B-channel aggregation and synchronous compression 2 ETSI Draft ES 201 684 V1.1.1 (1999-05) Reference DES/DTA-005069 (flc00icp.PDF) Keywords B-channel, FT, ISDN, Terminal ETSI Postal address F-06921 Sophia Antipolis Cedex - FRANCE Office address 650 Route des Lucioles - Sophia Antipolis Valbonne - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N° 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88 Internet [email protected] Individual copies of this ETSI deliverable can be downloaded from http://www.etsi.org If you find errors in the present document, send your comment to: [email protected] Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. © European Telecommunications Standards Institute 1999. All rights reserved. ETSI 3 ETSI Draft ES 201 684 V1.1.1 (1999-05) Contents Intellectual Property Rights ............................................................................................................................... 4 Foreword............................................................................................................................................................ 4 1 Scope.......................................................................................................................................................
    [Show full text]
  • Contributeurs Au Projet Freebsd Version: 43184 2013-11-13 Par Hrs
    Contributeurs au projet FreeBSD Version: 43184 2013-11-13 par hrs. Résumé Cet article liste les organisations et les personnes ayant contribué à FreeBSD. Table des matières 1. Gallerie des dons ..................................................................................................................... 1 2. Le bureau dirigeant .................................................................................................................. 3 3. Les développeurs FreeBSD .......................................................................................................... 3 4. Le projet de documentation de FreeBSD ...................................................................................... 14 5. Qui est reponsable de quoi ....................................................................................................... 15 6. Liste des anciens de la "Core Team" ........................................................................................... 16 7. Liste des anciens développeurs .................................................................................................. 17 8. Liste des logiciels contribués ..................................................................................................... 18 9. Contributeurs additionnels à FreeBSD ......................................................................................... 18 10. Contributeurs du kit de patch 386BSD ....................................................................................... 58 Index .....................................................................................................................................
    [Show full text]
  • Downloaded for Free From
    The Design of the NetBSD I/O Subsystems SungWon Chung Pusan National University 2 This book is dedicated to the open-source code developers in the NetBSD community. The original copy of this publication is available in an electronic form and it can be downloaded for free from http://arXiv.org. Copyright (c) 2002 by SungWon Chung. For non-commercial and personal use, this publication may be reproduced, stored in a retrieval system, or transmitted in any form by any means, electronic, mechanical, photocopying, recording or otherwise. For commercial use, no part of this publication can be reproduced by any means without the prior written permission of the author. NetBSD is the registered trademark of The NetBSD Foundation, Inc. Contents Preface 14 I Basics to Learn Filesystem 15 1 Welcome to the World of Kernel ! 17 1.1 How Does a System Call Dive into Kernel from User Program ? . 17 1.1.1 Example: write system call . 17 1.1.2 Ultra SPARC 0x7c CPU Trap . 18 1.1.3 Jump to the File Descriptor Layer . 24 1.1.4 Arriving at Virtual Filesystem Operations . 28 1.2 General Data Structures in Kernel such as List, Hash, Queue, ... 30 1.2.1 Linked-Lists . 30 1.2.2 Tail Queues . 34 1.2.3 Hash . 38 1.3 Waiting and Sleeping in Kernel . 39 1.4 Kernel Lock Manager . 39 1.4.1 simplelock and lock . 39 1.4.2 Simplelock Interfaces . 40 1.4.3 Lock Interfaces . 40 1.5 Kernel Memory Allocation . 43 1.6 Resource Pool Manager .
    [Show full text]
  • Decompress Files with PCDEZIP
    With PCDEZIP you can confidently download files compressed with PKZIP, Version 2.0. BY BOB FLANDERS AND MICHAEL HOLMES Decompress files with PCDEZIP f you've been using PCUNZIP to PCDEZIP's syntax decompress files, it's time to upgrade to usage: PCDEZIP [switches] zipfile [target\1 [filespec 1...11 I the new PCDEZIP. Phil Katz has released Version 2.0 of his popular switches: -f freshen existing files shareware compression program, PKZIP, extract new and updated files do not prompt on overwrite and the old utility can't decompress the ZIP directory newly zipped files. The new PCDEZIP will -d create directories unzip files zipped with either version of -t test file integrity PKZIP. zipfile .ZIP file Although we have added some valuable new features to PCDEZIP, our attempt has target \ the target directory; trailing backslash required not been to duplicate all the capabilities of the commercial product. PCDEZIP does filenames are files to be extracted; wildcards supported not, for example, permit using wildcard Fig 1: When you enter PCDEZIP with no parameters, it displays its syntax and switches as shown here characters in the .ZIP filename, handle files that span more than one floppy disk, preserve read-only file attributes, or respectively. If you don't supply a compiler it. For example, if SOURCE.ZIP is in your decrypt encrypted files. To get these parameter, C.BAT assumes Borland C++ D :\ PROJECT directory, then the com- facilities — and, of course, to be able to zip 3.1. mand files yourself — you must obtain the full- scale PKZIP, which is available from My PCDEZIP D:\PROJECT\SOURCE Computer Company on (02) 565 1991.
    [Show full text]