Search:  
Gentoo Wiki

SECURITY_cope_non_Gpl

This page is a candidate for deletion 
Reason given: Incomplete and abandoned by the original author, with no non-trivial changes since Jan 2006
If you disagree with its deletion, please explain why on its discussion page.
If you intend to fix it, please remove this notice, but do not remove this notice from articles that you have created yourself.
Make sure no other pages link here and check the page's history before deleting.
This article is part of the Security series.

Contents

Introduction

Sometimes there are security flaws resulting from closed sources, parts that can't be fixed or simply aren't fixed quickly, and give the attacker or automatic programs the opportunity to use these security flaws.

So we will explain how to cope with these flaws, which will give the following:

Advantages:

Disadvantages:

This article is mainly for normal users because the people who deal with hackers already use virtualization with open-source (closed source would increase the risk too much) and services or critical things and that give them some advantages, like:

That can be the purpose of another page...

How it works

So, the previous information maybe obvious for some people that use technology such as chroot-jail, user-mode Linux, and virtual machines.

The main idea is to trap the closed-source in a separate system and interface it with the main system for providing the capabilities that are closed-source for server capabilities such as wifi , or use a separate system in order to run closed-source programs.

This can be use in two ways:

Comparison

There are to many technologies that an X86 user can use, so we need to compare them.

Closed-source Programs,modules...

for things such as games,flash i don't know how to deal with X11:

do we need to run X11 in the "virtual machine" or can we network it to the main Linux installation

Retrieved from "http://www.gentoo-wiki.info/SECURITY_cope_non_Gpl"

Last modified: Fri, 08 Aug 2008 11:04:00 +0000 Hits: 4,686