DOCSLIB.ORG

Hardening Freebsd: an Approach to a Secure System Remy

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Hardening Freebsd: an Approach to a Secure System Remy Hardening FreeBSD: An Approach to a Secure System Remy Baumgarten University of Hawaii [email protected] October 4th, 2009 Hardening FreeBSD 知己知彼 百戰不殆 If you know both yourself and your enemy, you can win a hundred battles without a single loss. Sun Tzu's The Art of War “Operating System are not broken into; the programs running on the operating system are.” -Micheal W. Lucas General Summary: Hardware and Software Specifications Foreword and Forewarn Who are our Adversaries? Updating and Package Auditing Mailing Lists Permissions Networking and Firewalls Kernel Security Remote Logging Command Logging Secure Remote Access with SOCKS Proxy Forwarding Web Browsing Encryption Auditing Further Reading Hardware Specifications: Intel Core i7 920 Nehalem 2.66GHz 4 x 256KB L2 Cache 8MB L3 Cache LGA 1366 130W Quad-Core Processor ASUS P6T6 WS Revolution LGA 1366 Intel X58 ATX Intel Motherboard CORSAIR XMS3 6GB (3 x 2GB) 240-Pin DDR3 SDRAM DDR3 1333 (PC3 10666) Triple Channel CORSAIR CMPSU-850TX 850W ATX12V 2.2 / EPS12V 2.91 SLI Ready CrossFire Ready Active PFC Power Supply 2x - EVGA 896-P3-1260-TR GeForce GTX 260 896MB 448-bit GDDR3 PCI Express 2.0 x16 HDCP Ready SLI Supported Video Card LG W2452T-TF Black 24" 2ms(GTG) Widescreen LCD Monitor 400 cd/m2 10000:1 DCR with HDCP support LG Black 22X (CAV) DVD+R 8X DVD+RW 16X DVD+R DL 22X (CAV) DVD-R 6X DVD-RW 12X DVD-RAM 16X DVD-ROM 48X CD-R 32X CD-RW 48X CD-ROM 2MB Cache SATA 22X DVD¬±R DVD Burner Antec Nine Hundred Black Steel ATX Mid Tower Computer Case Software Specifications: FreeBSD 7.3 AMD64 Minimal Customized Compiled Kernel Installed Packages of Relevance: tripwire-2.4.1.2 lynis-1.2.6 snort-2.8.4.1_1 john-1.7.2_1 scponly-4.8 munin-main-1.2.6 postfix-2.6.5,1 mysql-server-5.0.86 portupgrade-2.4.6_3,2 portaudit-0.5.13 netcat-1.10_2 nmap-5.00 oinkmaster-2.0_1 Foreword and Forewarn: Security tips are mostly useless unless one understands why and how that tip works with other practices to protect your system from attacks. While securing your operating system may make it a little bit harder in some aspects for the attacker, a process listening on the network with root privileges with just one small bug could for example make a lot of the following I am going to talk about largely irrelevant. Security must to be covered as a whole, starting with the person or persons managing the system to the most intricate technical detail about the way the kernel manages the addresses of memory in the stack and the various mechanisms that make it work and everything in between. This paper is not about how to install or use FreeBSD. I assume you are mildly familiar with this operating system and are attempting to secure it against attacks. This is a brief overview meant to be starting guide to point you in the right direction and give you an idea of what security features FreeBSD has to offer. It is by no means a comprehensive or advanced guide. It would take many books worth of information to cover each of topics covered here and there simply isn’t enough room or time for anyone to cover all of these in depth. Who are our Adversaries? Skiddies (script kiddies) Botnets Internal Users Skilled Attackers Updating and Package Auditing: The most effective defense against attacks is simply keeping your system up to date. FreeBSD offers many tools for this. I prefer to use portsnap and portupgrade. If you are not able to login to your system daily, you should place these commands to be executed by cron and use the ports random delay flag as to not overload the FreeBSD servers. Portaudit is another great tool that checks your installed packages against known vulnerabilities. Simply install portaudit from ports and follow the instructions. Here is a sample run. Note that it performs the following execution daily and when you update your ports. sudo portaudit -Fda Password: auditfile.tbz 100% of 57 kB 66 kBps New database installed. Database created: Mon Oct 5 03:05:02 UTC 2009 0 problem(s) in your installed packages found. If a problem is found it will advise you to upgrade your package and include a link for more information. FreeBSD also sends out daily security mail if your mail server is correctly setup and you add your alias to your mailers configuration. This feeds the output of portaudit into your mail daily. It is also very important to read or grep the UPDATING file located in /usr/ports for information or warnings about packages that you are about to upgrade. If you don’t do this and install a new version of PERL for example, you may start to wonder why your system is not acting correctly. Do yourself a favor and look at the latest changes before upgrading. Subscribe to FreeBSD Security Mailing List I can’t emphasize this enough. Reading the listings daily on your commute will assist in understanding what attacks may be headed on the way. For example, if there is a 0day discovery and it affects a package you’re using, it may be wise to suspend its service until there is a patch or workaround. Also subscribe to BugTraq and CERT mailing lists. These have a higher volume then FreeBSD, but well worth the time. Permissions FreeBSD users are created with their group the same as their user, so it is ok if you want to chmod your /home/$user directory to 660. This makes sense on a system which is shared with other users or when you have daemons listening on ports as privileged users. For example, if you have a webserver and its running as the www user and an attacker performs RFI (remote file inclusion) against a vulnerable php script that spawns a perl connect back shell to their remote host to bypass your firewall, the shell will be running as user www. User www may have access, depending on how apache was configured, to write to /tmp, so arbitrary files may be downloaded there and executed. It’s best to prevent the attacker from looking in your /home/$user directory and chmod 660 will prevent this from happening if they are not able to perform a local privilege escalation attack. It is also a good idea to not allow other users to see what is in your crontabs. Issue the following commands to make them unreadable to other users: chmod 0640 /etc/crontab While your at it, also chmod /root to 750 chmod 0750 /root Recognize that if an attacker exploits one of your programs and escalates to root, all the strict permissions in the world won’t be able to help you. Networking and Firewalls Attacks typically start here. It’s best practice to disable any listening sockets that you do not use. Sockstat is a great tool for this. Use sockstat -4 to see what sockets are listening on ipv4 and ipv6. Disable any processes that you are not using. Don’t ignore ipv6. Using ipv6 is a great way for attackers to exfiltrate data without the user recognizing whats going on, and many firewall rule sets don’t take this into consideration. FreeBSD comes with an excellent way to control your network traffic, its called Packet Filtering or PF for short. It works at the kernel level and does a comparison of all traffic against your PF ruleset. $cat /etc/mypf.conf ext_if = "re0" services = "{5734}" # services on ports set skip on lo0 scrub in all antispoof for $ext_if block drop all pass out all keep state pass proto tcp from any to $ext_if port $services flags S/SA synproxy state This is an example of a packet filter ruleset. It has been minimized for the convenience of the reader. Note that pinging your server will result in no response. To learn more about creating a good PF ruleset, you should read the various online tutorials on PF or get your hands on a copy of The Book of PF (No Starch Press). For computers where you will be using openssh server (sshd), you should change the port it listens on to a non-standard port to mitigate bots that will fill your logs up with brute force attempts. If you want to leave openssh on its standard port of 22 you can use PF to block repeated attempts. I recommend doing this even if you listen on a different port for obvious reasons. Append the following to your rc.conf: pf_enable="YES" pf_rules="/etc/mypf.conf" pf_flags="" pflog_enable="YES" pflog_logfile="/var/log/pflog" pflog_flags="" Then add this to your /etc/mypf.conf: table <bruteforce> persist file "/var/db/blacklist" block quick from <bruteforce> This states that: There exists a table called bruteforce, which should be loaded from /var/db/blacklist. Everything in table bruteforce is immediately blocked. Everything incoming to SSH is allowed (if not already blocked from the bruteforce table). Now lets create (as root) our blacklist file that contains the IP’s of repeat offenders. touch /var/db/blacklist chmod 644 /var/db/blacklist Download the script located at http://home.earthlink.net/~valiantsoul/pf.html There are other options instead of using PF for this, but I provided the above as a demonstration of how you can script with PF. Personally I recommend using SSHGuard, it does all the above for you. Simply use ports to install: cd /usr/ports/security/sshguard && make install clean It’s a good idea to enable some configuration options if you decide not to use PF.
Load more

Recommended publications
  • Linux Security: What You Need to Know
    Linux Security: What you need to know Dr. James Stanger Chief Technology Evangelist CompTIA Your presenter . James Stanger, PhD Chief Technology Evangelist - CompTIA Security+, Network+, MCSE, LPI Linux, Symantec STA Responsible for CompTIA’s cerGficaGons and conGnuing educaGon • Security analyGcs • Risk management • PenetraGon tesGng, risk assessment, and intrusion detecon • Linux and open source Twier: @jamesstanger • Network administraGon • VirtualizaGon CompTIA hub: • Web technologies hps://Gnyurl.com/y94u3v7j • CerGficaGon development • Award-winning author and instructor Poll quesGon(s) 1. What animal is the Linux mascot? 2. What is the Linux mascot’s name? 3. How did this mascot get chosen, anyway? Why Linux is important to security? Linux is table stakes for security • You’ll be securing Linux-based systems – Web servers and databases – Cloud and virtualizaon • Nearly 1 in 3 Azure virtual machines are Linux • Majority of cloud services use Linux • You will use a Linux system to perform audits – End points (e.g., IoT, mobile devices, ICS) – Many tools available – Flexibility, scalability, and cost • Used as foundaonal components for major business and security soluGons by companies worldwide Most open source security – Fortune 500 tools are built naGvely in Linux – SMB Plaorms you’ll be asked to secure • Content management systems – Wordpress – SharePoint (has other uses) • Web servers • Databases • Network infrastructure – Firewalls, routers and VPN servers – Edge devices (e.g., micro datacenters) – Mobile – DNS especially • End
    [Show full text]
  • Drukkar P66 Android-X86 4.4 RC P67 Hotshots P68 Rcssmin P68 Gipfel P69 Lynx P69 Flpsed P70 Lynis P68 Nightmaretris P70 Zatacka P71
    FOSSPICKS Drukkar p66 Android-x86 4.4 RC p67 HotShots p68 rCSSmin p68 Gipfel p69 Lynx p69 Flpsed p70 Lynis p68 NightmareTris p70 Zatacka p71 Sparkling gems and new releases from the world of FOSSpicks Free and Open Source Software Mike Saunders has spent a decade mining the internet for open source treasures. Here’s the result of his latest haul… Lightweight blog platform Drukkar 2.0 http://drukkar.sourceforge.net ituation: you want to set up entries as simple XML files, and is your own blog. Options: a designed with minimum bandwidth Smillion and one competing overheads, so the “content should blog platforms, each one trying to account for most of your web be more feature-rich, flashy and traffic” as the developer puts it. Web 4.0 than the last. End result: you get tired of trying to work out Nice and simple what’s right for you, give up, and go To install Drukkar, extract its .zip to the pub instead. file directly into a location on your Sounds familiar? Most of us web server (note that it won’t create don’t need whizz-bang WordPress a subdirectory during extraction). installations with all the trimmings Then edit config.xml and set for our day-to-day musings, and the base_url and base_location Drukkar does a splendid job with settings to match your installation minimal requirements. It doesn’t path. Finally, make sure that the need a database or special Apache entries, files and cache directories Drukkar’s default theme, “flat”, is clean and simple. To change the modules or anything like that – its are writable by your web server text on the right, edit inc/sidebar.php.
    [Show full text]
  • Hey Lynis, Audit This by Russ Mcree – ISSA Senior Member, Puget Sound (Seattle), USA Chapter
    toolsmith Hey Lynis, Audit This By Russ McRee – ISSA Senior Member, Puget Sound (Seattle), USA Chapter Prerequisites/dependencies solution will include the existing Lynis Unix/Linux operating systems client that we’ll cover here, a management and reporting interface, as well as related plugins. Michael says they’re making great progress and each appy Holidays to all readers, the ISSA community, day brings them closer to an official first version. Specific to and infosec tool users everywhere. As part of De- the plugins, while a work in progress, they create specialized cember’s editorial theme for the ISSA Journal, Di- hooks via the client. As an example, imagine heuristics scan- Hsaster Recovery/Disaster Planning, I thought I’d try to con- ning with correlation at the central node to detect security in- nect tooling and tactics to said theme. I’m going to try and do trusions. Compliance checking for the likes of Basel II, GLBA, this more often so you don’t end up with a web application HIPAA, PCI DSS, and SOX is another likely plugin candidate. hacking tool as part of the forensics and analysis issue. I can The short-term road map consists of finishing the web inter- hear Thom (editor) and Joel (editorial advisory board chair) face, followed by the presenting and supporting documents. now: “Congratulations Russ, it only took you seven years to This will include documentation, checklists, control over- catch up with everyone else, you stubborn git.” views, and materials for system administrators, security pro- Better late than never I always say, so back to it.
    [Show full text]
  • 2.6 Auditing Linux/Unix Systems
    Processing engine for security health checks Christofer Huynh, Jesper Gustafsson Department of Computer Science © Christofer Huynh, Jesper Gustafsson. LTH School of Engineering Lund University Box 882 SE-251 08 Helsingborg Sweden LTH Ingenjörshögskolan vid Campus Helsingborg Lunds universitet Box 882 251 08 Helsingborg Printed in Sweden. Lunds University Lund 2017 Abstract Computer security is still an often neglected field even though the IT industry is huge and still growing. Making sure that systems are secure is something that is very important but can take a lot of man hours. This thesis contains the research and documentation for an auditing tool created on behalf of a company that specialises in computer security, TrueSec. The audit tool uses the log files that are built from the scripts that TrueSec uses to runs various unix commands as a base, but it has been designed in such a way to allow the addition of other types of logs. The tool was designed with future development in mind. It uses configuration files that are seperated from the code itself to declare rules which the log files are checked against, allowing the tool to evolve with time by adding new rules. At the request of TrueSec a simple web service as a proof of concept for an online service with an authentication model with log in and user roles for uploading log files and storing the output from the audit tool was also developed. Keywords: audit tool, computer security, security audit, analysis engine, security health check 3 Sammanfattning Datasäkerhet är fotfarande ofta ett misskött fält även fast IT- sektorn är stor och fortfarande växer.
    [Show full text]
  • Lynis Enterprise on the Other Hand Has Much More Possibilities to Display Data, Including Extended Reports in Several Formats
    Lynis Lynis Installation and Usage • Introduction • Installation • Using Lynis • Basics • Commands, Options, and Arguments • Suggestions and Warnings • Behind the scenes • Profiles • HostIDs Introduction Lynis is an open source security tool. It helps with auditing systems running UNIX-alike systems (Linux, macOS, BSD), and providing guidance for system hardening and compliance testing. This document contains the basics to use the software. Installation The installation of Lynis is explained in the Get Started guide. Using Lynis Basics By running 'lynis' the program is started and will provide the basic parameters available. If you manually extracted Lynis (or used Git), then use './lynis' to start the program from the local directory. The most common command to start Lynis is using audit system command. This still start the security scan. To run Lynis you should meet one requirement: have write access to /tmp (temporary files) Commands, Options, and Arguments Introduction The behavior of programs can influenced with commands, arguments, and options. These terms are often mixed up, so we start with a quick introduction. Commands tell the program what to do. An option tells the program how to do it. If an argument is used, it tell on what it applies. Arguments usually follow an option, like a filename, or a target. Example $ ./lynis audit system --quick --auditor "The Auditor" In this example we tell Lynis to audit (command), with the target system (argument). By using the --quick (option), we tell it not to wait. We used --auditor (option) and defined it as "The Auditor" (argument). Lynis Commands The Lynis tool requires a minimum amount of parameters to run.
    [Show full text]
  • Akraino Release 3: Proposal for Mandatory Tests
    Akraino Release 3: Proposal for Mandatory Tests March 12, 2020 Introduction › The Akraino TSC has discussed the Release 3 requirements in the face-to-face meeting (see the following two slides) › This presentation is a proposal for the mandatory tests in Release 3 › Again, the tests are mandatory only as relevant 2 3 4 Proposal For Incubation projects (that For Mature projects additionally: have been in R1 and R2): › HA tests: etcd_ha, ha/*, › Redfish ceph_service › Kubernetes Conformance › 1.17 › Lynis › Vuls › Kubehunter 5 Open questions › Do we still need the OpenStack tests? › What to do with Linux Testing Project? › Is Kubernetes Conformance 1.17 ok for all? › What to do with the results of Lynis/Vuls/Kubehunter? 6 Summary › Docker › K8s › Networking › Docker Bench for Security › Conformance › Helloworld › Hardware › Etcd_ha › OpenStack › Bios_version › HA › Ceph_service › Hp_baremetal › Ha_calico_dns_proxy › Tempest › Redfish › Ha_etcd_api_ctl_sch › Os › Helm › Ha_services › Cyclictest › Helm_chart › Ha_worker › Ltp (Linux Testing Project) › Helm_repository › Kube-hunter › Lynis › Vuls 7 Docker Bench for Security › https://github.com/docker/d ocker-bench-security › “The Docker Bench for Security is a script that checks for dozens of common best-practices around deploying Docker containers in production” 8 Redfish › https://github.com/DMTF/Redfish-Usecase-Checkers › “collection of python3 tools to exercise and validate common use cases for Redfish” › https://github.com/DMTF/Redfish-Test-Framework › “a python3 tool and a model for
    [Show full text]
  • Lynis Report of Ubuntu 18.04
    10/17/2019 report.html [ Lynis 2.7.5 ] ################################################################################ Lynis comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under the terms of the GNU General Public License. See the LICENSE file for details about using this software. 2007-2019, CISOfy - https://cisofy.com/lynis/ Enterprise support available (compliance, plugins, interface and tools) ################################################################################ [+] Initializing program ------------------------------------ - Detecting OS... [ DONE ] - Checking profiles... [ DONE ] --------------------------------------------------- Program version: 2.7.5 Operating system: Linux Operating system name: Ubuntu Linux Operating system version: 18.04 Kernel version: 4.15.0 Hardware platform: x86_64 Hostname: pc07 --------------------------------------------------- Profiles: /etc/lynis/default.prf Log file: /var/log/lynis.log Report file: /var/log/lynis-report.dat Report version: 1.0 Plugin directory: /etc/lynis/plugins --------------------------------------------------- Auditor: [Not Specified] Language: en Test category: all Test group: all --------------------------------------------------- - Program update status... [ NO UPDATE ] [+] System Tools ------------------------------------ - Scanning available tools... - Checking system binaries... [+] Plugins (phase 1) ------------------------------------ Note: plugins have more extensive tests and may take several minutes to complete
    [Show full text]
  • Geek Guide > Self-Audit
    GEEK GUIDE SELF-AUDIT: CHECKING ASSUMPTIONS AT THE DOOR Table of Contents About the Sponsor .......................................................... 4 Introduction .................................................................... 5 Two Steps Necessary for Security ................................. 7 Verify Configurations ...................................................... 9 Assume Security Has Been Compromised .................. 10 Tools to Scan for Malware ............................................ 11 rkhunter �������������������������������������������������������������������������������������������������12 chkrootkit ����������������������������������������������������������������������������������������������13 LMD�������������������������������������������������������������������������������������������������������14 lynis �������������������������������������������������������������������������������������������������������19 Checking for Stealth Ports ........................................... 22 lsof ��������������������������������������������������������������������������������������������������������23 unhide ���������������������������������������������������������������������������������������������������24 Rootkits ......................................................................... 25 Conclusion .................................................................... 27 GREG BLEDSOE is VP of Operations at Personal, Inc. (http://www.personal.com). He is CEH and CPT certified and has 20 years of hard-fought experience
    [Show full text]
  • INSECURE-Mag-18.Pdf
    Welcome to another issue of (IN)SECURE filled with a variety of hot topics. It!s been a busy summer and we have a lot on the table for you. I had the pleasure to visit Greece earlier this month for the 1st NIS Summer School. From what I!ve seen, information and network security in Europe are in good hands. More about this fine event at page 13. In other news, Jo Stewart-Rattray, who was one of the authors featured in the November 2007 issue of (IN)SECURE, wanted to apologize for omitting proper attribution in her article - "Information Security, the Nuts and Bolts". The attribution that should have been included is “Information Security Governance: Guidance for Boards of Directors and Executive Management, 2nd Edition”, IT Governance Institute, 2006. The article has been removed from our archives as soon as questions have been raised and we are satisfied with her prompt response. Mirko Zorz Chief Editor Visit the magazine website at www.insecuremag.com (IN)SECURE Magazine contacts Feedback and contributions: Mirko Zorz, Chief Editor - [email protected] Marketing: Berislav Kucan, Director of Marketing - [email protected] Distribution (IN)SECURE Magazine can be freely distributed in the form of the original, non modified PDF document. Distribution of modified versions of (IN)SECURE Magazine content is prohibited without the explicit permission from the editor. Copyright HNS Consulting Ltd. 2008. www.insecuremag.com Kaspersky Internet Security and Anti-Virus 2009 versions Kaspersky Lab announced the North American release of Kaspersky Internet Security 2009 and Kaspersky Anti-Virus 2009. Kaspersky has entirely rebuilt its award-winning anti-malware security engine.
    [Show full text]
  • How to Securely Isolate and Execute Lynis from Kali Linux
    How to securely isolate and execute Lynis from Kali Linux Version 0.1, Last Updated: 11 Oct 2020 Table of Contents 1. Introduction . 1 2. Requirements. 3 2.1. Writing Conventions . 3 2.2. VirtualBox . 3 2.2.1. Clean VirtualBox Networking. 3 2.2.2. Add VirtualBox Networking . 4 2.3. Vagrant. 5 2.4. Kali Linux and Damn Vulnerable Web Application (DVWA) . 5 2.4.1. Vagrantfile . 5 2.4.2. bootstrap.sh . 8 3. Lynis. 12 3.1. Lynis output on Kali Linux VM . 14 3.2. Lynis Output on RHEL 7 VM . 25 3.3. Running Lynis on a Remote Server . 35 4. Conclusion . 36 5. Appendix . 37 1. Introduction The motivation behind this paper is to explore using the tool Lynis that comes with Kali Linux. What is this tool: "Lynis is an open source security auditing tool. Its main goal is to audit and harden Unix and Linux based systems. It scans the system by performing many security control checks. Examples include searching for installed software and determine possible configuration flaws. Many tests are part of common security guidelines and standards, with on top additional security tests. After the scan a report will be displayed with all discovered findings. To provide you with initial guidance, a link is shared to the related Lynis control." source: Kali Linux "Since Lynis is flexible, it is used for several different purposes. Typical use cases for Lynis include: - Security auditing - Compliance testing (e.g. PCI, HIPAA, SOx) - Penetration testing - Vulnerability detection - System hardening " source: Lynis What does Lynus run on? "Lynis runs on almost all UNIX-based systems and versions, including: - AIX - FreeBSD - HP-UX - Linux - macOS - NetBSD - NixOS - OpenBSD - Solaris - and others It even runs on systems like the Raspberry Pi, IoT devices, and QNAP storage devices." source: Lynis "Lynis scanning is modular and opportunistic.
    [Show full text]
  • Automated Hardening of a Linux Web Server
    Automated Hardening of a Linux Web Server Olencin,ˇ Michal and Perhác,ˇ Ján Abstract: This article is dedicated to the de- web servers. In this paper, we are focused on sign and implementation of automated hardening the results of our recent work with the automated a Linux web server after the clean installation. The securing of the Linux webserver. We start with article deals with the analysis of the cybersecurity, focus, and scope of the configuration. Based on a brief description of the current state in the that, was made a design of an automated security area. We compare existing solutions, and analyze configuration with a detailed description. The main technological possibilities. Then, we describe the accomplishment of the work is a configuration details of the designs and our implementation. in script. The script is compared and evaluated with the final section, we evaluate our implementation. existing solutions and it achieved the best rating in security audits. We compare it with other popular solutions in the field by performing standard security audits. Index Terms: cybersecurity, Linux security, Web 2. MOTIVATION security The cybersecurity and protection of sensitive data are frequently discussed topics today. There 1. INTRODUCTION is a growing interest in this area mainly due to the increase in cyberattacks and theft of sensitive HE PAPER is oriented on designing an au- data. tomated hardening of a Linux web server T After installation of a web server, a basic con- and subsequently on implementing and evaluation figuration is used and it is necessary to configure of the designed solution.
    [Show full text]
  • Development Tools on Freebsd
    FOR NOVICE AND ADVANCED USERS Development tools on FreeBSD Experimenting with XEN Model View Whatever Introduction to origins NetBSD 10 Things Your CIO Should Know About TrueNAS Vol. 09 No. 11 ISSUE 75 1898-9144 1 2 EDITORS’ WORD Dear Readers, I know that many of you don’t celebrate Christmas, so I will not wish you Merry Christmas. But I hope that for all of you, December and the end of the year will be a wonderful time, no matter where you come from, which language you speak or what your beliefs are. I also know that you have been waiting for more FreeBSD re- Editor in Chief: lated articles. So, here they are. Marta Ziemianowicz Great, as always, David Carlier will introduce you to Develop- ment Tools on FreeBSD. If you would like to switch from Linux [email protected] to FreeBSD, this article is definitely for you. Contributing: The next article is an introduction to NetBSD. Siju Oommen David Carlier, Siju Oommen, Damian Czernous, Michael Boelem, Valerie George wrote a guide for you that is another must read for all Heatley, Mark VonFange, Roger Pau Monne and Rob Somerville. beginners, but I hope that professionals and old timers will like it as well. Top Betatesters & Proofreaders: After BSD, it is time for something new. Say “Hi” to Damian Annie Zhang, Denise Ebery, Eric Geissinger, Luca Ferrari, Imad Soltani, Czernous and the origins of Model View Whatever. Not really Olaoluwa Omokanwaye, Radjis Mahangoe, Mani Kanth, Ben Milman, Mark VonFange and David Carlier related to Open Source? Maybe it will be useful for some of you anyway and will broaden your horizons.
    [Show full text]