|
Written by LE Webmaster
|
|
Wednesday, 26 January 2005 |
Hackers have computers too and want to keep their own machines free of intrusion
from the Internet. Paradoxically, these computers may be the most secure
computers on the Internet, because the hackers use free software that they can
examine for security problems, they are the first to discover (or create)
security weaknesses, and they fix their own systems as soon as loopholes are
discovered. They share the security fixes with anyone who wants them, and you
can take advantage of this fast response to new threats in your own network by
using the same software they do. Free firewalls often suffer from a few of the
same class problems: Weak or missing logging and alerting features No real-time
firewall monitoring capability Weak or missing graphical user interface
Difficult command prompt-based configuration
 Be first to comment this article |  Add as favourites (54) | Read more...
|
|
Written by LE Webmaster
|
|
Wednesday, 26 January 2005 |
The idea behind chroot is fairly simple. When you run BIND (or any other process) in a chroot jail, the process is simply unable to see any part of the filesystem outside the jail. For example, in this document, we'll set BIND up to run chrooted to the directory /chroot/named. Well, to BIND, the contents of this directory will appear to be /, the root directory. Nothing outside this directory will be accessible to it. You've probably encounted a chroot jail before, if you've ever ftped into a public system.
Be first to comment this article | Add as favourites (51) | Read more... |
|
Written by LE Webmaster
|
|
Wednesday, 26 January 2005 |
This article is meant for those who are going to implement firewall using OpenBSD. The main purpose for this article is to protect servers (such as web, mail, DNS and others) within a firewalled network.
This article is based on wanvadder's personal experiences and wanvadder cannot guarantee it will suit all system that you have. Fell free to email wanvadder any comments, feedback or any other issues concerning this article. Co-operations from everybody are highly appreciated.
Be first to comment this article | Add as favourites (51) | Read more... |
|
|
Written by machex
|
|
Wednesday, 26 January 2005 |
This article shows in a step-by-step fashion, how to install and configure the Apache 1.3.x Web server in order to mitigate or avoid successful break-in when new vulnerabilities in this software are found
Be first to comment this article | Add as favourites (68) | Read more... |
|
|
Written by void
|
|
Wednesday, 26 January 2005 |
Over the past couple of years, steganography has been the source of a lot of discussion, particularly as it was suspected that terrorists connected with the September 11 attacks might have used it for covert communications. While no such connection has been proven, the concern points out the effectiveness of steganography as a means of obscuring data. Indeed, along with encryption, steganography is one of the fundamental ways by which data can be kept confidential. This article will offer a brief introductory discussion of steganography: what it is, how it can be used, and the true implications it can have on information security.
Be first to comment this article | Add as favourites (97) | Read more... |
|
|
Written by Daniel Zilli
|
|
Wednesday, 26 January 2005 |
|
Eventually, if you get interested enough in Security, you are going to wonder what a DMZ is and why you should or should not have one. DMZ is an acronym that stands for De-Militarized Zone, and in the 'real' world it is the location between two hostile entities such as North and South Korea. In the Security community, however, it is a separate, untrusted network where boxes serving public services should be placed. It is a buffer zone between a completely untrusted network (like the Internet) and a relatively trusted network (like your private LAN). The primary reason for implementing a DMZ is to keep your public and private assets separated so that a compromise in the public area does not automatically result in a compromise of your private assets as well. There are two main ways to implement a DMZ. The first is using three NICs, as follows
Be first to comment this article | Add as favourites (66) | Read more... |
|
|
|
<< Start < Prev 1 2 3 Next > End >>
|
