Paranoid Penguin - The Future of Linux Security
So those are my thoughts on the future of Linux security. In the mean time, keep on using the techniques this column has focused on over the years: firewalls, virus-scanners, automatic-patch/update tools, VPNs and application-specific security controls such as chroot jails and audit trails.
With that, I bid you farewell, not only for this month but indefinitely. It's time for me to focus on other things for at least a little while and allow fresh voices take over the Paranoid Penguin. I'm continuing in my role as Security Editor and in that capacity will keep on doing my bit to help Linux Journal bring you outstanding security content. I also will try to contribute an article now and then myself, on an ad hoc basis. But the article you are reading now is my last as exclusive author of this column.
Thanks to all of you for five years of support, encouragement and edification—I've never made a mistake in this column that wasn't noticed and corrected by someone out there and always to my benefit. It's been a great five years, and I'm grateful to this terrific magazine's staff and readers alike for all you've done for me!
Resources for this article: /article/8329.
Mick Bauer, CISSP, is Linux Journal's security editor and an IS security consultant in Minneapolis, Minnesota. O'Reilly & Associates recently released the second edition of his book Linux Server Security (January 2005). Mick also composes industrial polka music but has the good taste seldom to perform it.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- Paranoid Penguin - Building a Secure Squid Web Proxy, Part IV
- SUSE LLC's SUSE Manager
- Google's SwiftShader Released
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- Doing for User Space What We Did for Kernel Space