Linux in Government: Security Enhanced Linux - The Future is Now
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Sponsored by AMD
If you already use virtualized infrastructure, you are well on your way to leveraging the power of the cloud. Virtualization offers the promise of limitless resources, but how do you manage that scalability when your DevOps team doesn’t scale? In today’s hypercompetitive markets, fast results can make a difference between leading the pack vs. obsolescence. Organizations need more benefits from cloud computing than just raw resources. They need agility, flexibility, convenience, ROI, and control.
Stackato private Platform-as-a-Service technology from ActiveState extends your private cloud infrastructure by creating a private PaaS to provide on-demand availability, flexibility, control, and ultimately, faster time-to-market for your enterprise.
Sponsored by ActiveState
| Containers—Not Virtual Machines—Are the Future Cloud | Jun 17, 2013 |
| Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer | Jun 12, 2013 |
| Weechat, Irssi's Little Brother | Jun 11, 2013 |
| One Tail Just Isn't Enough | Jun 07, 2013 |
| Introduction to MapReduce with Hadoop on Linux | Jun 05, 2013 |
| Android's Limits | Jun 04, 2013 |
- Containers—Not Virtual Machines—Are the Future Cloud
- Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer
- Linux Systems Administrator
- Introduction to MapReduce with Hadoop on Linux
- Senior Perl Developer
- Weechat, Irssi's Little Brother
- Technical Support Rep
- UX Designer
- One Tail Just Isn't Enough
- Android's Limits
- Free is costly
10 min 59 sec ago - Bought photoshop CS5 for developing a website :(
27 min 19 sec ago - Reply to comment | Linux Journal
1 hour 15 min ago - Reply to comment | Linux Journal
1 hour 15 min ago - Replica Watches
3 hours 40 min ago - Reply to comment | Linux Journal
7 hours 51 min ago - on the path to understanding
7 hours 54 min ago - As a fisher,we know that a
1 day 3 hours ago - All I Say Is Worth Share!
1 day 4 hours ago - GeekSays
1 day 4 hours ago
Featured Jobs
| Linux Systems Administrator | Houston and Austin, Texas | Host Gator |
| Senior Perl Developer | Austin, Texas | Host Gator |
| Technical Support Rep | Houston and Austin, Texas | Host Gator |
| UX Designer | Austin, Texas | Host Gator |
| Web & UI Developer (JavaScript & j Query) | Austin, Texas | Host Gator |
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?



Comments
also - systrace?
I'm also interested in a comparison to systrace. Systrace is what OpenBSD uses - and they are not exactly known for not knowing security. It should also be less intrusive, and less ressource-intensive.
What about the TCO hit because of SELinux?
Dear All (these are just my 2c worth):
While SELinux contributes greatly to the technology side of the coin, itfails to address the economics of security. The litmus test is definitely how many nodes will actually RUN SELinux. However, the classification of why they CANNOT run it is also an important piece of information.
SELinux comes out of National Defense paradigm, namely: Achieve the goal no matter what the cost, because there is (relatively) infinite money and infinite resources. This is not practical for a normal business which has cost constraints.
IMHO SELinux doesn't address vital ROI and TCO concerns. I would've liked to see questions regarding that direction in this interview - and i haven't zipped through the book ;) so i am not sure if the good Author has touched on this topic.
Cheers,
Ahmed
targeted policy solves this
The "targeted" policy which is in Fedora Core 3 and will be in Red Hat Enterprise Linux 4 solves this. It restricts only the daemons that are at most danger (network facing daemons initially but as we progress we will add other daemons to the list). This stops quite a number of attack vectors while having no restrictions on users who login to the system. Of course this means that targeted policy doesn't prevent a local user from attacking the system, but that is a trade-off that the administrator can make for ease of use.
A system running the targeted policy should in most cases be indistinguishable from a non-SE system. The only reported problems of the targeted policy are related to Apache - a daemon that needs protection but is very difficult to write policy for because it's so configurable.
In Fedora Core 3 and Red Hat Enterprise Linux 4 SE Linux is enabled by default and installed with only the targeted policy. In Fedora you can convert the system to "strict" policy after completing the install if you desire better security and are happy to trade-off some ease of use to get it.
The standard support agreements for RHEL will only include targeted policy. This does not prevent you from using strict policy on a RHEL system, but the support agreement does not cover problems with strict policy.
Currently we have no plans to make future releases of either Fedora or RHEL default to strict policy.
Hi, It is a good interview
Hi,
It is a good interview but why there are no questions about alternative of SElinux like grsecurity. It would be interesting to have the opinion of Bill about the advantage/inconvenient of selinux comparing to grsecurity.