Before connecting to the internet: You shoud first disable any unnecessary services (say IIS).
For Windows XP You can enable the firewall that comes with Windows XP. (Easy and provides the best protection.)
For Windows 2000 You can use IPSEC. (May be complicated and time consuming.) Set any IP which connect to your vulernerable ports (say, 80, 139, 445... etc) to use IPSEC.
For Windows NT (and beyond) You can use the TCP/IP filtering in the network interface (not IPSEC). (Not a perfect solution, but that's the only method that I know for NT).
FreeBSD is unique and special. These features attracts me:
- Native IPSEC support. The IPSEC support has been tightly integrated into the kernel and the base utilities.
- Random IP ID. Make the increment of ID field in IP packets to be randomize instead of 1.
- Shadow Process. Users except root view their own process.
All the above featues are included in the source/cvs without downloading any patch, a big plus.
There are also many other features or pros of FreeBSD. To name a few: BSD's secure level, sealth firewall, stable TCP/IP stack and VM, random ephemeral port allocation (ported from OpenBSD) and......
Slashdot Mirror
Before connecting to the internet:
You shoud first disable any unnecessary services (say IIS).
For Windows XP
You can enable the firewall that comes with Windows XP. (Easy and provides the best protection.)
For Windows 2000
You can use IPSEC. (May be complicated and time consuming.)
Set any IP which connect to your vulernerable ports (say, 80, 139, 445... etc) to use IPSEC.
For Windows NT (and beyond)
You can use the TCP/IP filtering in the network interface (not IPSEC). (Not a perfect solution, but that's the only method that I know for NT).
That's Redhat. It is a third party patch? (specific to RedHat)
I doubt if it is the default in other Linux distributions.
For FreeBSD, Shadow Process comes with the OS. No patch is needed because FreeBSD is highly integrated.
FreeBSD is unique and special.
......
These features attracts me:
- Native IPSEC support. The IPSEC support has been tightly integrated into the kernel and the base utilities.
- Random IP ID. Make the increment of ID field in IP packets to be randomize instead of 1.
- Shadow Process. Users except root view their own process.
All the above featues are included in the source/cvs without downloading any patch, a big plus.
There are also many other features or pros of FreeBSD. To name a few:
BSD's secure level, sealth firewall, stable TCP/IP stack and VM, random ephemeral port allocation (ported from OpenBSD) and
Although OpenBSD mainly focus on security, it should have SMP support, sooner or later.
The sooner it get started, the better it will be done.
I think OpenBSD may look at the SMP implementation in FreeBSD and try to adopt some code and find bugs during the process.
These websites may be helpful:
. sourceforge.net/
http://www.ipsec-howto.org/
http://ipsec-tools
I've tried compling oo, but get a core dump in idlc arrayoutofboundexception...
In the SMPng section:
0 02 -apr-2002.html#SMPng
Alan Cox has started working on fixing the existing locking in the VM subsystem and moving bits of it out from under Giant.
http://www.freebsd.org/news/status/report-feb-2
oops
^H is backspace..
I downloaded KDE 2.2.2 deb package from /debian/pool/main/.. It runs great with Qt 2.3.1 (it seems Qt 2.3.2 sucks).
It's so beautiful that I'm stunned.