Sixth

The KISS (keep it simple, stupid) philosophy of Arch Linux was devised around the year 2002 by Judd Vinet, a Canadian computer science graduate who launched the distribution in the same year. For several years it lived as a marginal project designed for intermediate and advanced Linux users and only shot to stardom when it began promoting itself as a "rolling-release" distribution that only needs to be installed once and which is then kept up-to-date thanks to its powerful package manager and an always fresh software repository. As a result, Arch Linux "releases" are few and far between and are now limited to a basic installation CD that is issued only when considerable changes in the base system warrant a new install media.

Besides featuring the much-loved "rolling-release" update mechanism, Arch Linux is also renowned for its fast and powerful package manager called "Pacman", the ability to install software packages from source code, easy creation of binary packages thanks to its AUR infrastructure, and the ever increasing software repository of well-tested packages. Its highly-regarded documentation, complemented by the excellent Arch Linux Handbook makes it possible for even less experienced Linux users to install and customise the distribution. The powerful tools available at the user's disposal mean that the distro is infinitely customisable to the most minute detail and that no two installations can possibly be the same.

On the negative side, any rolling-release update mechanism has its dangers: a human mistake creeps in, a library or dependency goes missing, a new version of an application already in the repository has a yet-to-be-reported critical bug... It's not unheard of to end up with an unbootable system following a Pacman upgrade. As such, Arch Linux is a kind of distribution that requires its users to be alert and to have enough knowledge to fix any such possible problems. Also, the infrequent install media releases mean that sometimes it is no longer possible to use the old media to install the distribution due to important system changes or lack of hardware support in the older Linux kernel.

• Pros: Excellent software management infrastructure; unparalleled customisation and tweaking options; superb online documentation
• Cons: Occasional instability and risk of breakdown
• Software package management: "Pacman" using TAR.XZ packages
• Available editions: Minimal installation CD and network installation CD images for 32-bit (i686) and 64-bit (x86_64) processors
• Suggested Arch-based and Arch-like alternatives: Manjaro Linux (live with Cinnamon, Enlightenment, KDE, LXDE, MATE, Openbox, Xfce), Antergos (live with GNOME 3), ArchBang Linux (lightweight with Openbox), Chakra GNU/Linux (live CD with KDE), Bridge Linux (live with GNOME, KDE, LXDE and Xfce), ParabolaGNU/Linux (free software), KaOS (live with KDE)

Arch Linux (an example desktop)

Source from distrowatch

Read More

ESET NOD32 Antivirus

 

 

System Requirements

• ESET NOD32 Antivirus, 2015 edition runs on any system with Microsoft®

• Operating System:
  Windows® 10, 8.1, 8, 7, Vista, XP, and Microsoft Windows Home Server 2003, 2011.
  Learn more about Windows 10 compatibility
  

• Product requires an Internet connection.

Product Overview (PDF)

Download ESET NOD32® Antivirus offline installer 32 bit for windows  
Click here

Download ESET NOD32® Antivirus offline installer 64 bit for windows
Click here

Read More

Avast Anti Virus

What makes Avast security unique?

Just as the computing landscape has dramatically changed in recent years, so have the requirements for protecting users. An ever-increasing diversity of platforms, operating systems, applications and devices means an ever-greater set of attack vectors. By leveraging the largest multi-platform sensor network in the world, the cloud, machine learning, and proprietary big-data analytics, Avast delivers a unique and highly sophisticated approach to today’s security challenges.

Security in Numbers

There are four main components to our protection network. First, there are the 230 million globally distributed devices that serve as the unparalleled sensor network for our system. Second, there is the massive database of more than 5 billion files tested by Avast, which we call FileRep. Third, there is Scavenger, our internal system that keeps track of all the threat samples Avast has ever detected and of all the work that the virus analysts did to classify and detect those threats. Fourth, there is the GPU-powered system that leverages this amazing amount of information to quickly and automatically classify as many new samples as possible. We call it Medusa.

Synchronization

To be effective, Medusa has to be kept up to date with all the changes that happen in Scavenger. This includes new files arriving, and those files being classified as malware or benign, or being removed from the sets that are relevant for classification. A durable message queue in RabbitMQ is used to ensure that no updates are lost even during Medusa server updates and maintenance. Additionally, the consistency between Medusa and Scavenger is continuously checked with complete dumps of object identifiers.

Real-time deployment

Real-time classification is required whenever a file is too new and a machine is having trouble deciding if the file is malicious. Given that there are 230 million Avast users, there is potential for a massive overload when new threats appear. To eliminate this, we implemented a caching proxy between the clients and the Medusa cluster. A file can be classified differently, as new information arrives from Scavenger, so the TTL of the cached decisions is set to a few minutes. Despite this, the cache hits in almost 40% of the requests.

Cluster setup

Every Medusa node in our deployment uses two or four Nvidia GPUs. A Medusa cluster has one master node that is aware of all the sets, and several slave nodes, which contain some parts of the sets. The classification needs many clean and malicious samples. The Evo-gen generator also uses a set with unclassified samples. Because of a large difference in usage patterns, we keep the different sets separate. Clean set samples are the most important because of the inherently high costs of a false positive. Thus, the clean set takes most of the space and is proportionally the slowest to scan. To increase the throughput, we keep the clean set mirrored. The sets with recent malware and unclassified samples take up only a fraction of the space —roughly 10% — needed for a clean set.

Machine Learning

The only way to effectively use all the information collected over the years is to leverage machine learning. We use instance-based learning because of its many beneficial properties, including the ease of:

• re-learning the model, which is only a matter of adding or removing a sample to or from the correct set
• understanding the reasons for particular decisions
• fine tuning the false positive rate

Custom-distance function

Each sample is represented by a constant-sized feature vector consisting of approximately 100 attributes. We keep the exact composition of the feature vector secret, but, for example, obvious candidates such as section table data in the Portable Executable format are included. In general, there are static and dynamic features, categorized as offsets, sizes, checksums, factors, bit flags and generic numbers. Taking into account the nature of the attributes, we ended up with several distance operators and a weighting scheme that equalizes the importance of the attributes. The following table contains a sample of the operators we use.

Distance operator	Field types	Dexription
EQUAL_RET32	Checksum, value	return 32 when values are equal
Ham	String	Hamming distance
Ham-Mul32	Bitfield	Hamming distance multiplied by 32 - each flag change is as important as maximal change of one feature
Log	Length, Offset	base 2 logarithm of a difference
Order	Length, Offset, Value	difference of base 2 logarithms
Retz	all	ignore the feature, return 0 for all values

.kNN classifier

The most common approach for instance-based learning is the nearest neighbor classification. To fine tune our classifier, we built a tool, called Pythia, which displays the nearest neighbors of a given query sample. It uses a dimensionality reduction method (NMDS) to display the neighbors in 2D space, and also displays additional metadata for the selected samples. This information can be used by a human to determine whether or not it is feasible to distinguish between malware and clean neighbors in the current case. The goal was to create a fully autonomous system — which means high precision at the cost of lower recall. After some experimenting, we added a few thresholds, including minimal allowed distance to clean files, maximal allowed distance to malware files, as well as a weighting term that shifts the balance between clean and malware sets.

Real-world data

The redundancy in real world data is quite significant. Our internal systems handle around 250,000 new PE files every day. Out of those, 150,000 can be directly assigned to one of 20,000 clusters using very strict clustering criteria (low threshold distance and complete linkage). Each cluster can then be classified as a whole. That means 130,000 fewer decisions to make, and that the total number of clusters does not grow by 20,000 every day, as the clusters overlap between days.

World-class Protection

There are several methods we can use to transfer the classification to our customers. In order to provide the highest level of protection, we chose these three methods.

Method	How many users	Delay in classification	How many file versions
Real-time classification	single user	no delay	one
FileRepMalware	all users	seconds	one
Evo-gen	all users	minutes	many

Real-time classification

Avast checks every executable before it’s executed in a customer’s machine. When no signature from the current threat database matches the file, the FileRep service is queried. If the returned user count (prevalence) is anomalously low, the executable ends up in the Avast Sandbox. If the executable trace log does not match any known threat, the real-time classifier is invoked. Avast extracts the feature vector, submits it to a cloud-based service, and waits for the response. Most of the low prevalence files are benign. Out of approximately 250,000 requests daily, about 4,000 are classified as malicious.

FileRepMalware

Once a file is classified as malicious and our internal systems check that it is safe to detect this particular file worldwide, a simple flag is set in the FileRep service. Every Avast client that encounters that particular file instantly blocks it and reports it as FileRepMalware.

Evo-gen

Old string-based signatures work well when properly executed, and are especially good at generalizing many variants of a threat. But string-based signatures require an analyst and time. In today’s threat landscape, with all its variants and interconnectivity, there just aren’t enough people or enough time to keep pace. A new approach was required that generalizes like string signatures do, but doesn’t rely on human intervention or take as much time.
Enter Evo-gen. Evo-gen leverages the distance function to create a set of similar feature vectors which allows us to build a rule set from those features. Once we have a set of very similar feature vectors from the distance function, we can start to pick features that make them similar and build a rule set from those features. It is somewhat similar to rule-set generation in decision trees, but the objectives are different. To boost the generalization, we can pick as few rules as possible, while keeping hits in the clean set at zero. But there are many ways to pick 20 rules from 100 possible ones - 5.36x1020, or 536 billion, numerically speaking. We’re currently taming the combinatorial explosion with a stochastic approach, which provides better results than Scavenger approaches. This is where the speed of the GPUs is very important again. While trying to understand how the Evo-gen rule sets (blue) affect the signature “ecosystem,” we produced the following visualization. Each blob represents a different rule set or signature, and the size of the blob is proportional to the number of detected variants.


Download Avast Free Antivirus offline installer Click here

Download Avast Pro Antivirus offline installer Click here

Download Avast Internet Security offline installer Click here

Download Avast Premiers offline installer Click here

source from avast !

Read More

Fifth

Although Fedora was formally unveiled only in September 2004, its origins effectively date back to 1995 when it was launched by two Linux visionaries -- Bob Young and Marc Ewing -- under the name of Red Hat Linux. The company's first product, Red Hat Linux 1.0 "Mother's Day", was released in the same year and was quickly followed by several bug-fix updates. In 1997, Red Hat introduced its revolutionary RPM package management system with dependency resolution and other advanced features which greatly contributed to the distribution's rapid rise in popularity and its overtaking of Slackware Linux as the most widely-used Linux distribution in the world. In later years, Red Hat standardised on a regular, 6-month release schedule. In 2003, just after the release of Red Hat Linux 9, the company introduced some radical changes to its product line-up. It retained the Red Hat trademark for its commercial products, notably Red Hat Enterprise Linux, and introduced Fedora Core (later renamed to Fedora), a Red Hat-sponsored, but community-oriented distribution designed for the "Linux hobbyist". After the initial criticism of the changes, the Linux community accepted the "new" distribution as a logical continuation of Red Hat Linux. A few quality releases was all it took for Fedora to regain its former status as one of the best-loved operating systems on the market. At the same time, Red Hat quickly became the biggest and most profitable Linux company in the world, with an innovative product line-up, excellent customer support, and other popular initiatives, such as its Red Hat Certified Engineer (RHCE) certification programme. Although Fedora's direction is still largely controlled by Red Hat, Inc. and the product is sometimes seen -- rightly or wrongly -- as a test bed for Red Hat Enterprise Linux, there is no denying that Fedora is one of the most innovative distributions available today. Its contributions to the Linux kernel, glibc and GCC are well-known and its more recent integration of SELinux functionality, virtualisation technologies, systemd service manager, cutting-edge journaled file systems, and other enterprise-level features are much appreciated among the company's customers. On a negative side, Fedora still lacks a clear desktop-oriented strategy that would make the product easier to use for those beyond the "Linux hobbyist" target. Pros: Highly innovative; outstanding security features; large number of supported packages; strict adherence to the free software philosophy; availability of live CDs featuring many popular desktop environments Cons: Fedora's priorities tend to lean towards enterprise features, rather than desktop usability; some bleeding edge features, such as early switch to KDE 4 and GNOME 3, occasionally alienate some desktop users Software package management: YUM graphical and command line utility using RPM packages Available editions: Fedora for 32-bit (i386) and 64-bit (x86_64) processors; also live CD editions with GNOME, KDE, LXDE, MATE and Xfce desktops Suggested Fedora-based alternatives: Korora (live DVD with GNOME, KDE, LXDE or Xfce) Suggested Red Hat-based alternatives: CentOS, Scientific Linux Fedora 23 Source from distrowatch

Read More

Fourth

Mageia
Mageia might be the newest distribution on this list, but its roots go back to July 1998 when Gaël Duval launched Mandrake Linux. At the time it was just a fork of Red Hat Linux with KDE as the default desktop, better hardware detection and some user-friendly features, but it gained instant popularity due to positive reviews in the media. Mandrake was later turned into a commercial enterprise and renamed to Mandriva (to avoid some trademark-related hassles and to celebrate its merger with Brazil's Conectiva) before almost going bankrupt in 2010. It was eventually saved by a Russian venture capital firm, but this came at a cost when the new management decided to lay off most of the established Mandriva developers at the company's Paris headquarters. Upon finding themselves without work, they decided to form Mageia, a community project which is a logical continuation of Mandrake and Mandriva, perhaps more so than Mandriva itself.

Mageia is primarily a desktop distribution. Its best-loved features are cutting-edge software, superb system administration suite (Mageia Control Centre), ability to attract a large number of volunteer contributors, and extensive internationalisation support. It features one of the easiest, yet powerful system installers on its installation DVD, while it also releases a set of live images with either KDE or GNOME desktops and comprehensive language support, with the ability to install it onto a hard disk directly from the live desktop session. The distribution's well-established package management features, with powerful command-line options and a graphical software management module, allow easy access to thousands of software packages. The unique Mageia Control Center continues to improve with each release, offering newcomers to Linux a powerful tool for configuring just about any aspect of their computer without ever reaching for the terminal.

While Mageia has been off to a flying start since it was established in September 2010, there is some concern over the developers' ability to maintain the distribution over the long term where much of the work is done on a volunteer basis. Also, it lacks the buzz and infrastructure accompanying some of the bigger and more profligate Linux distributions. The project's documentation could also do with some improvement, while its 9-months release cycle can also be viewed as a disadvantage in terms of generating news and media excitement, especially when compared to other major distributions which use a shorter, 6-month development process.

• Pros: Beginner-friendly; excellent central configuration utility; very good out-of-the-box support for dozens of languages; installable live media
  
• Cons: Lacks reputation and mindshare following its fork from Mandriva, some concern over the developers' ability to maintain the distribution long-term on a volunteer basis
  
• Software package management: URPMI with Rpmdrake (a graphical front-end for URPMI) using RPM packages
  
• Available editions: installation DVDs for 32-bit (i586) and 64-bit (x86_64) processors; installable live CDs for 32-bit (i586) processors
  
  
• Possible alternatives: OpenMandriva, ROSA
  
  

Mageia 5
Source from distrowatch

Read More

Download Operating System Ubuntu Dekstop

Ubuntu comes with everything you need to run your organisation, school, home or enterprise. All the essential applications, like an office suite, browsers, email and media apps come pre-installed and thousands more games and applications are available in the Ubuntu software centre.

Download iso ubuntu 15.10 dekstop 64-bit Click Here

Download iso ubuntu 15.10 dekstop 32-bit Click Here

Read More

Third

Debian GNU/Linux was first announced in 1993. Its founder, Ian Murdock, envisaged the creation of a completely non-commercial project developed by hundreds of volunteer developers in their spare time. With sceptics far outnumbering optimists at the time, it seemed destined to disintegrate and collapse, but the reality was very different. Debian not only survived, it thrived and, in less than a decade, it became the largest Linux distribution and possibly the largest collaborative software project ever created!

The success of Debian GNU/Linux can be illustrated by the following numbers. It is developed by over 1,000 volunteer developers, its software repositories contain close to 50,000 binary packages (compiled for 8 processor architectures), and it is responsible for inspiring over 120 Debian-based distributions and live CDs. These figures are unmatched by any other Linux-based operating system. The actual development of Debian takes place in three main branches (or four if one includes the bleeding-edge "experimental" branch) of increasing levels of stability: "unstable" (also known as "sid"), "testing" and "stable". This progressive integration and stabilisation of packages and features, together with the project's well-established quality control mechanisms, has earned Debian its reputation of being one of the best-tested and most bug-free distributions available today.

However, this lengthy and complex development style also has some drawbacks: the stable releases of Debian are not particularly up-to-date and they age rapidly, especially since new stable releases are only published once every 1 - 3 years. Those users who prefer the latest packages and technologies are forced to use the potentially buggy Debian testing or unstable branches. The highly democratic structures of Debian have led to controversial decisions and gives rise to infighting among the developers. This has contributed to stagnation and reluctance to make radical decisions that would take the project forward.

• Pros: Very stable; remarkable quality control; includes over 30,000 software packages; supports more processor architectures than any other Linux distribution
  
• Cons: Conservative - due to its support for many processor architectures, newer technologies are not always included; slow release cycle (one stable release every 1 - 3 years); discussions on developer mailing lists and blogs can be uncultured at times
  
• Software package management: Advanced Package Tool (APT) using DEB packages
  
• Available editions: Installation CD/DVD and live CD images for 12 processor architectures, including all 32-bit and 64-bit processors from Intel, AMD, Power and others
  
• Suggested Debian-based alternatives: Ubuntu, SparkyLinux (Enlightenment, JWM, LXDE, MATE, Openbox, Razor-qt, Xfce), SolydXK (Xfce ou KDE), KNOPPIX (LXDE), Tanglu (GNOME, KDE), siduction (LXQt)
  
  

Debian GNU/Linux 8.0

Source form distrowatch

Read More