Thursday, November 17, 2016

How a Virus works


computer virus is a type of malicious software program ("malware") that, when executed, replicates by reproducing itself (copying its own source code) or infecting other computer programs by modifying them.[1] Infecting computer programs can include as well, data files, or the "boot" sector of the hard drive. When this replication succeeds, the affected areas are then said to be "infected" with a computer virus.The term "virus" is also commonly, but erroneously, used to refer to other types of malware. "Malware" encompasses computer viruses along with many other forms of malicious software, such as computer "worms"ransomwaretrojan horseskeyloggersrootkitsspywareadware, malicious Browser Helper Object (BHOs) and other malicious software. The majority of active malware threats are actually trojan horse programs or computer worms rather than computer viruses. The term computer virus, coined by Fred Cohen in 1985, is a misnomer. Viruses often perform some type of harmful activity on infected host computers, such as acquisition of hard diskspace or central processing unit (CPU) time, accessing private information (e.g., credit card numbers), corrupting data, displaying political or humorous messages on the user's screen, spamming their e-mail contacts, logging their keystrokes, or even rendering the computer useless. However, not all viruses carry a destructive "payload" or attempt to hide themselves—the defining characteristic of viruses is that they are self-replicating computer programs which install themselves without user consent.
Virus writers use social engineering deceptions and exploit detailed knowledge of security vulnerabilities to gain access to their hosts' computers and computing resources. The vast majority of viruses target systems running Microsoft Windows, employing a variety of mechanisms to infect new hosts, and often using complex anti-detection/stealth strategies to evade antivirus software.Motives for creating viruses can include seeking profit (e.g., with ransomware), desire to send a political message, personal amusement, to demonstrate that a vulnerability exists in software, for sabotage and denial of service, or simply because they wish to explore cybersecurity issues, artificial lifeand evolutionary algorithms.
Computer viruses currently cause billions of dollars' worth of economic damage each year, due to causing system failure, wasting computer resources, corrupting data, increasing maintenance costs, etc. In response, free, open-source antivirus tools have been developed, and an industry of antivirus software has cropped up, selling or freely distributing virus protection to users of various operating systems.As of 2005, even though no currently existing antivirus software was able to uncover all computer viruses (especially new ones), computer security researchers are actively searching for new ways to enable antivirus solutions to more effectively detect emerging viruses, before they have already become widely distributed.[

Early academic work on self-replicating programs

The first academic work on the theory of self-replicating computer programs was done in 1949 by John von Neumann who gave lectures at the University of Illinois about the "Theory and Organization of Complicated Automata". The work of von Neumann was later published as the "Theory of self-reproducing automata". In his essay von Neumann described how a computer program could be designed to reproduce itself. Von Neumann's design for a self-reproducing computer program is considered the world's first computer virus, and he is considered to be the theoretical "father" of computer virology. In 1972, Veith Risak, directly building on von Neumann's work on self-replication, published his article "Selbstreproduzierende Automaten mit minimaler Informationsübertragung" (Self-reproducing automata with minimal information exchange). The article describes a fully functional virus written in assembler programming language for a SIEMENS 4004/35 computer system. In 1980 Jürgen Kraus wrote his diplom thesis "Selbstreproduktion bei Programmen" (Self-reproduction of programs) at the University of Dortmund. In his work Kraus postulated that computer programs can behave in a way similar to biological viruses.

Operations and functions


Parts

A viable computer virus must contain a search routine, which locates new files or new disks which are worthwhile targets for infection. Secondly, every computer virus must contain a routine to copy itself into the program which the search routine locates. The three main virus parts are:

Infection mechanism

Infection mechanism (also called 'infection vector'), is how the virus spreads or propagates. A virus typically has a search routine, which locates new files or new disks for infection.

Trigger

The trigger, which is also known as logic bomb, is the compiled version that could be activated any time an executable file with the virus is run that determines the event or condition for the malicious "payload" to be activated or delivered such as a particular date, a particular time, particular presence of another program, capacity of the disk exceeding some limit, or a double-click that opens a particular file.

Payload

The "payload" is the actual body or data that perform the actual malicious purpose of the virus. Payload activity might be noticeable (e.g., because it causes the system to slow down or "freeze"), as most of the time the "payload" itself is the harmful activity, or some times non-destructive but distributive, which is called Virus hoax.

Phases

Virus phases is the life cycle of the computer virus, described by using an analogy to biology. This life cycle can be divided into four phases:

Dormant phase

The virus program is idle during this stage. The virus program has managed to access the target user's computer or software, but during this stage, the virus does not take any action. The virus will eventually be activated by the "trigger" which states which event will execute the virus, such as a date, the presence of another program or file, the capacity of the disk exceeding some limit or the user taking a certain action (e.g., double-clicking on a certain icon, opening an e-mail, etc.). Not all viruses have this stage.

Propagation phase

The virus starts propagating, that is multiplying and replicating itself. The virus places a copy of itself into other programs or into certain system areas on the disk. The copy may not be identical to the propagating version; viruses often "morph" or change to evade detection by IT professionals and anti-virus software. Each infected program will now contain a clone of the virus, which will itself enter a propagation phase.

Triggering phase

A dormant virus moves into this phase when it is activated, and will now perform the function for which it was intended. The triggering phase can be caused by a variety of system events, including a count of the number of times that this copy of the virus has made copies of itself.

Execution phase

This is the actual work of the virus, where the "payload" will be released. It can be destructive such as deleting files on disk, crashing the system, or corrupting files or relatively harmless such as popping up humorous or political messages on screen.

Infection targets and replication techniques


Resident vs. non-resident viruses

memory-resident virus (or simply "resident virus") installs itself as part of the operating system when executed, after which it remains in RAM from the time the computer is booted up to when it is shut down. Resident viruses overwrite interrupt handling code or other functions, and when the operating system attempts to access the target file or disk sector, the virus code intercepts the request and redirects the control flow to the replication module, infecting the target. In contrast, a non-memory-resident virus (or "non-resident virus"), when executed, scans the disk for targets, infects them, and then exits (i.e. it does not remain in memory after it is done executing).

Macro viruses

Many common applications, such as Microsoft Outlook and Microsoft Word, allow macro programs to be embedded in documents or emails, so that the programs may be run automatically when the document is opened. A macro virus (or "document virus") is a virus that is written in a macro language, and embedded into these documents so that when users open the file, the virus code is executed, and can infect the user's computer. This is one of the reasons that it is dangerous to open unexpected or suspicious attachmentsin e-mails. While not opening attachments in e-mails from unknown persons or organizations can help to reduce the likelihood of contracting a virus, in some cases, the virus is designed so that the e-mail appears to be from a reputable organization (e.g., a major bank or credit card company).

Boot sector viruses

Boot sector viruses specifically target the boot sector and/or the Master Boot Record (MBR) of the host's hard drive or removable storage media (flash drivesfloppy disks, etc.).

Email virus

Email virus – A virus that specifically, rather than accidentally, uses the email system to spread. While virus infected files may be accidentally sent as email attachments, email viruses are aware of email system functions. They generally target a specific type of email system (Microsoft’s Outlook is the most commonly used), harvest email addresses from various sources, and may append copies of themselves to all email sent, or may generate email messages containing copies of themselves as attachments.

Stealth strategies

In order to avoid detection by users, some viruses employ different kinds of deception. Some old viruses, especially on the MS-DOS platform, make sure that the "last modified" date of a host file stays the same when the file is infected by the virus. This approach does not fool antivirus software, however, especially those which maintain and date cyclic redundancy checks on file changes.Some viruses can infect files without increasing their sizes or damaging the files. They accomplish this by overwriting unused areas of executable files. These are called cavity viruses. For example, the CIH virus, or Chernobyl Virus, infects Portable Executable files. Because those files have many empty gaps, the virus, which was 1 KB in length, did not add to the size of the file.Some viruses try to avoid detection by killing the tasks associated with antivirus software before it can detect them (for example, Conficker). In the 2010s, as computers and operating systems grow larger and more complex, old hiding techniques need to be updated or replaced. Defending a computer against viruses may demand that a file system migrate towards detailed and explicit permission for every kind of file access.


Read request intercepts

While some antivirus software employ various techniques to counter stealth mechanisms, once the infection occurs any recourse to "clean" the system is unreliable. In Microsoft Windows operating systems, the NTFS file system is proprietary. This leaves antivirus software little alternative but to send a "read" request to Windows OS files that handle such requests. Some viruses trick antivirus software by intercepting its requests to the Operating system (OS). A virus can hide by intercepting the request to read the infected file, handling the request itself, and returning an uninfected version of the file to the antivirus software. The interception can occur by code injection of the actual operating system files that would handle the read request. Thus, an antivirus software attempting to detect the virus will either not be given permission to read the infected file, or, the "read" request will be served with the uninfected version of the same file.
The only reliable method to avoid "stealth" viruses is to "boot" from a medium that is known to be "clean". Security software can then be used to check the dormant operating system files. Most security software relies on virus signatures, or they employ heuristics. Security software may also use a database of file "hashes" for Windows OS files, so the security software can identify altered files, and request Windows installation media to replace them with authentic versions. In older versions of Windows, file cryptographic hash functions of Windows OS files stored in Windows—to allow file integrity/authenticity to be checked—could be overwritten so that the System File Checker would report that altered system files are authentic, so using file hashes to scan for altered files would not always guarantee finding an infection.

Self-modification

Most modern antivirus programs try to find virus-patterns inside ordinary programs by scanning them for so-called virus signatures. Unfortunately, the term is misleading, in that viruses do not possess unique signatures in the way that human beings do. Such a virus "signature" is merely a sequence of bytes that an antivirus program looks for because it is known to be part of the virus. A better term would be "search strings". Different antivirus programs will employ different search strings, and indeed different search methods, when identifying viruses. If a virus scanner finds such a pattern in a file, it will perform other checks to make sure that it has found the virus, and not merely a coincidental sequence in an innocent file, before it notifies the user that the file is infected. The user can then delete, or (in some cases) "clean" or "heal" the infected file. Some viruses employ techniques that make detection by means of signatures difficult but probably not impossible. These viruses modify their code on each infection. That is, each infected file contains a different variant of the virus.

Encrypted viruses

One method of evading signature detection is to use simple encryption to encipher (encode) the body of the virus, leaving only the encryption module and a static cryptographic key in cleartext which does not change from one infection to the next.In this case, the virus consists of a small decrypting module and an encrypted copy of the virus code. If the virus is encrypted with a different key for each infected file, the only part of the virus that remains constant is the decrypting module, which would (for example) be appended to the end. In this case, a virus scanner cannot directly detect the virus using signatures, but it can still detect the decrypting module, which still makes indirect detection of the virus possible. Since these would be symmetric keys, stored on the infected host, it is entirely possible to decrypt the final virus, but this is probably not required, since self-modifying code is such a rarity that it may be reason for virus scanners to at least "flag" the file as suspicious. An old but compact way will be the use of arithmetic operation like addition or subtraction and the use of logical conditions such as XORing, where each byte in a virus is with a constant, so that the exclusive-or operation had only to be repeated for decryption. It is suspicious for a code to modify itself, so the code to do the encryption/decryption may be part of the signature in many virus definitions. An simpler older approach did not use a key, where the encryption consisted only of operations with no parameters, like incrementing and decrementing, bitwise rotation,arithmetic negation, and logical NOT. Some viruses will employ a means of encryption inside an executable in which the virus is encrypted under certain events, such as the virus scanner being disabled for updates or the computer being rebooted. This is called cryptovirology. At said times, the executable will decrypt the virus and execute its hidden runtimes, infecting the computer and sometimes disabling the antivirus software.


Source :https://en.wikipedia.org/wiki/Computer_virus


Monday, November 7, 2016

Camphor! Overview,Effects and Dosage

CAMPHOR


Other Names:

Alcanfor, Arbre à Camphre, Camphor Tree, Camphora, Camphora Officinarum, Camphre, Camphre de Laurier, Camphre Gomme, Camphrier, Cemphire, Cinnamomum Camphora, dl-Camphor, dl-Camphre, Gum Camphor, Kapur, Karpoora, Karpuram, Laurel Camphor.







CAMPHOR OVERVIEW INFORMATION

Camphor used to be made by distilling the bark and wood of the camphor tree. Today, camphor is chemically manufactured from turpentine oil. It is used in products such as Vicks VapoRub.

Camphor products can be rubbed on the
 skin (topical application) or inhaled. Be sure to read the label to find out how the product should be administered.

People use camphor topically to relieve pain and reduce
 itching. It has also been used to treat fungal infections of the toenail, warts, cold sores, hemorrhoids, and osteoarthritis.

Camphor is used topically to increase local
 blood flow and as a “counterirritant,” which reduces pain and swelling by causing irritation. It is important not to apply camphor to broken skin, because it can enter the body quickly and reach concentrations that are high enough to cause poisoning.

Some people use camphor topically to treat respiratory tract diseases and to treat
 heart disease symptoms. Camphor is also used topically as an eardrop, and for treating minor burns.

Some people inhale camphor to reduce the urge to
 cough.

Although it is an
 UNSAFE practice, some people take camphor by mouth to help them cough up phlegm, for treating respiratory tract infections, and for intestinal gas (flatulence). Experts warn against doing this because, when ingested, camphor can cause serious side effects, even death.

Camphor is a well-established folk remedy, and is commonly used. Camphorated oil (20% camphor in cottonseed oil) was removed from the U.S. market in the 1980s because of safety concerns. It continues to be available without a prescription in Canada.

How does it work?

Camphor seems to stimulate nerve endings that relieve symptoms such as pain and itching when applied to the skin. Camphor is also active against fungi that cause infections in the toenails.

CAMPHOR USES & EFFECTIVENESS 

Likely Effective for:

·         Cough.Camphor is FDA-approved as a chest rub in concentrations less than 11%.
·         Pain. Camphor is FDA-approved for use on the skin as a painkiller in concentrations of 3% to 11%. It is in many rub-on products for cold sores, insect stings and bites, minor burns, and hemorrhoids.
·         Skin itching or irritation. Camphor is FDA-approved for use on the skin to help itching or irritation in concentrations of 3% to 11%.


Possibly Effective for:

·         Osteoarthritis. A rub-on cream containing camphor, glucosamine sulfate, and chondroitin sulfate seems to reduce the severity of symptoms of osteoarthritis by about half. Researchers believe it is probably the camphor, not the other ingredients, that relieves the symptoms.


Insufficient Evidence for:

·         Toenail fungus (onychomycosis). Preliminary research suggests that camphor, in combination with lemon eucalyptus oil and menthol, applied to the toenail area, might be useful for treating toe nail fungus. Applying chest rub products containing camphor such as Vicks VapoRub to affected toenails daily until the infected nail grows out appears to clear fungal nail infections in some people.
·         Low blood pressure after standing up. Early resrach suggests that taking a specific product containing camphor and hawthorn (Korodin-Herz-Kreislauf-Tropfen) by mouth helps prevent big drops in blood pressure upon standing. However, it is not clear if taking camphor alone provides the same benefits, and this product is not available in the US.
·         Warts.
·         Hemorrhoids.
·         Other conditions

CAMPHOR SIDE EFFECTS & SAFETY

Camphor is LIKELY SAFE for most adults when applied to the skin in a cream or lotion in low concentrations. Camphor can cause some minor side effects such as skin redness and irritation. Do not use undiluted camphor products or products containing more than 11% camphor. These can be irritating and unsafe. Camphor is also LIKELY SAFE for most adults when inhaled as vapor in small amounts as a part of aromatherapy. Don't use more than 1 tablespoon camphor solution per quart of water. 

Do not heat camphor-containing products (Vicks VapoRub, BenGay, Heet, many others) in the microwave. The product can explode and cause severe burns.

Camphor is
 POSSIBLY SAFE when applied to the skin in higher concentrations for a short time.

Camphor-containing products are
 LIKELY UNSAFE when applied to broken or injured skin. Camphor is easily absorbed through broken skin and can reach toxic levels in the body.

Camphor is
 UNSAFE when taken by mouth by adults. Ingesting camphor can cause severe side effects, including death. The first symptoms of camphor toxicity occur quickly (within 5 to 90 minutes), and can include burning of the mouth and throat, nausea, and vomiting.

Special Precautions & Warnings:

Pregnancy and breast-feeding: Taking camphor by mouth is UNSAFE during pregnancy or breast-feeding. The safety of applying camphor to the skin during pregnancy or breast-feeding is unknown. Do not risk your health or your baby’s. Avoid using camphor during pregnancy.

Children: Camphor is POSSIBLY UNSAFE in children when applied to the skin. Children tend to be more sensitive to the side effects. Camphor is definitely UNSAFE when taken by mouth. Seizures and death can occur if these products are eaten. Keep camphor-containing products away from children.

Liver disease: Taking camphor by mouth or applying it to the skin have been linked to potential liver damage. In theory, using camphor might make liver disease worse.

CAMPHOR DOSING

The following doses have been studied in scientific research:
APPLIED TO THE SKIN:
  • ·         For pruritis and pain: A 3% to 11% ointment is typically used three to four times daily.
  • ·         For cough: A thick layer of 4.7% to 5.3% camphor ointment is applied to the throat and chest. The area may be covered with a warm, dry cloth or left uncovered.
  • ·         For osteoarthritis: A topical cream containing camphor (32 mg/g), glucosamine sulfate (30 mg/g), and chondroitin sulfate (50 mg/g) as needed on sore joints for up to 8 weeks.


INHALATION:
  • ·         One tablespoon of solution per quart of water is placed directly into a hot steam vaporizer, bowl, or washbasin. Sometimes 1.5 teaspoons of solution are added to a pint of water and boiled. The medicated vapors are breathed. This inhalation may be repeated up to three times a day.




Wednesday, November 2, 2016

A Texas-Sized Chunk of Ice Is Missing From the Arctic

A strange thing is happening in the Arctic. After dipping to its second-lowest extent on record in September, sea ice has struggled mightily to rebound in October.

Freakishly mild weather coupled with a warmer-than-normal ocean are in large part responsible for the great sea ice slowdown of 2016. It's just the latest piece of evidence that 2016 is on another level when it comes to signs that the climate is changing.
The turn of the calendar toward winter and rapidly dwindling daylight usually equate to the growth of sea ice in the Arctic. After hitting a minimum in early September, sea ice regrowth got off to a blistering start. But it's speedy recolonization of the Arctic Ocean slowed to a crawl in October. 
Preliminary data published by the Japanese space agency and visualized by Zach Labe, a Ph.D. student at the University of California, Irvine, show that it's the slowest regrowth on record. That includes a period at the end of October where it appears sea ice didn't grow at all.
Large areas of ice were missing at the end of October in the western Beaufort and Chukchi seas north of Alaska and the Kara and Barents seas that sit above Russia. Ted Scambos, a scientist at the National Snow and Ice Data Center, said it looks like sea ice is about 232,000 square miles below the previous record and 965,000 square miles below the October average. For perspective, the latter is an area slightly larger than the eastern half of the U.S. (and the former is roughly the size of Texas).
The main reason for the slow growth is it's been relatively warm by Arctic standards almost all month. The Arctic Ocean has been an astonishing 7°F above normal on average in October (again, this is based on preliminary data) with a number of areas much warmer than that with temperatures ranging up to 18°F warmer than usual.
"There is a strong high pressure over Scandinavia which is helping to transport warm air from the north Atlantic towards the Arctic," Julienne Stroeve, a scientist at NSIDC, said. "Ocean temperatures are also quite a bit above normal especially in the Chukchi and East Siberian Sea so that is also contributing."
It's the latest piece of dismal sea ice news in 2016. This year set a record low for the winter maximum, besting the previous record set just a year ago. Sea ice reached its the second-lowest minimum ever recorded in the region, trailing only 2012.
The lack of ice this summer allowed the Crystal Serenity, a luxury cruise ship, to traverse the Northwest Passage. There have also been a number of other months with record low sea ice this year.
Compounding the sea ice misery in the Arctic is the disappearance of sea ice that's been around for four years or more. That older sea ice essentially acts like the foundation of a house, helping support the growth of new, younger sea ice. It's also thicker and harder and less prone to melting. Without it, younger sea ice is being built on shaky ground and melts more easily each summer.
And yet the foundational layer of ice is disappearing from the Arctic. In the 1980s, it accounted for about 20 percent of all sea ice. But when sea ice reached its minimum in 2016, older ice made up only 3 percent of the icepack.
Taken alone, all of this indicates 2016 may be an outlier. But looking at the big picture shows it's right in line with recent trends. September sea ice has disappeared at a clip of 13.4 percent per decade since the late 1970s. And ships have been using the Northwest Passage since 2007; the Crystal Serenity was just a particularly high profile crossing for its exorbitant ticket prices.
Climate change will continue to crank up the heat and rapidly eat away at Arctic sea ice. That means in the coming decades we'll likely look back at 2016 as the good old days when at least there was some old ice left.

Source : http://www.seeker.com/a-texas-sized-chunk-of-ice-is-missing-from-the-arctic-2076375250.html