Language Selection

English French German Italian Portuguese Spanish

HP ports Virus Throttler to Linux

Filed under
Linux

Hewlett-Packard next week plans to release Linux versions of its Virus Throttler security technology and ProLiant Essentials Intelligent Networking Pack, the company confirmed Friday.

The antivirus software was developed at HP Labs as a tool for mitigating the effects of virus infections. It has been available with the company's ProCurve switches and on Windows versions of its servers since February of this year but had not previously been available for Linux users.

Effective Tuesday, HP will begin selling the Linux version of Virus Throttler with its ProLiant and BladeSystem servers, a company spokeswoman said Friday. The software can either be purchased as part of the ProLiant Essentials Intelligent Networking Pack, which will also support Linux beginning Tuesday, or be purchased separately, the spokeswoman said.

Virus Throttler is able to single out systems that behave as if infected by a computer virus. It can then notify a system administrator of the problem and automatically reduce the number of network connections made by that system, which keeps the computer operational but greatly reduces its ability to spread viruses.

The Intelligent Networking Pack is a suite of server software designed to help boost the performance of computer networks.

ProLiant Essentials Intelligent Networking Pack will be priced starting at $149 per server. The stand-alone Virus Throttler will cost $90 per server. Both products will run on Red Hat Linux, Suse Linux, and Asianux, a Linux distribution developed by developed by China's Red Flag Software and Japan's Miracle Linux.

By Robert McMillan
IDG News Service

More in Tux Machines

Linux and FOSS Events

  • Keynote: State of the Union - Jim Zemlin, Executive Director, The Linux Foundation
    As the open source community continues to grow, Jim Zemlin, Executive Director of The Linux Foundation, says the Foundation’s goal remains the same: to create a sustainable ecosystem for open source technology through good governance and innovation.
  • Open Source for Science + Innovation
    We are bringing together open source and open science specialists to talk about the “how and why” of open source and open science. Members of these communities will give brief talks which are followed by open and lively discussions open to the audience. Talks will highlight the role of openness in stimulating innovation but may also touch upon how openness appears to some to conflict with intellectual property interests.
  • Announcing the Equal Rating Innovation Challenge Winners
    Six months ago, we created the Equal Rating Innovation Challenge to add an additional dimension to the important work Mozilla has been leading around the concept of “Equal Rating.” In addition to policy and research, we wanted to push the boundaries and find news ways to provide affordable access to the Internet while preserving net neutrality. An open call for new ideas was the ideal vehicle.

Docker/Kubernetes/Containers

  • Containerization Leaders Explore Possible Standardized Data Storage Interface
    A group of engineers from every leading container orchestrator maker have gathered together, virtually, around an initiative to explore a common lexicon for container-based data storage. Initially proposed by Mesosphere’s Benjamin Hindman, the Container Storage Interface initiative — which, for now, is essentially a GitHub document — is exploring the issue of whether the community at large, and their users, would benefit from a standardized API for addressing and managing storage volumes.
  • What are the top open source tools for Docker management?
  • Enterprise container DevOps steps up its game with Kubernetes 1.6
    Managing containers isn't easy. That's where such programs as Docker swarm mode, Kubernetes, and Mesosphere can make or break your containers initiatives. Perhaps the most popular of these, Kubernetes, has a new release, Kubernetes 1.6, that expands its reach by 50 percent to 5,000 node clusters. Conservatively, that means Kubernetes can manage 25,000 Docker containers at once.

Security Leftovers

  • Someone is putting lots of work into hacking Github developers [Ed: Dan Goodin doesn't know that everything is under attack and cracking attempts just about all the time?]
    Open-source developers who use Github are in the cross-hairs of advanced malware that has steal passwords, download sensitive files, take screenshots, and self-destruct when necessary.
  • Security Orchestration and Incident Response
    Technology continues to advance, and this is all a changing target. Eventually, computers will become intelligent enough to replace people at real-time incident response. My guess, though, is that computers are not going to get there by collecting enough data to be certain. More likely, they'll develop the ability to exhibit understanding and operate in a world of uncertainty. That's a much harder goal. Yes, today, this is all science fiction. But it's not stupid science fiction, and it might become reality during the lifetimes of our children. Until then, we need people in the loop. Orchestration is a way to achieve that.

Leftover: Development (Linux)

  • Swan: Better Linux on Windows
    If you are a Linux user that has to use Windows — or even a Windows user that needs some Linux support — Cygwin has long been a great tool for getting things done. It provides a nearly complete Linux toolset. It also provides almost the entire Linux API, so that anything it doesn’t supply can probably be built from source. You can even write code on Windows, compile and test it and (usually) port it over to Linux painlessly.
  • Lint for Shell Scripters
    It used to be one of the joys of writing embedded software was never having to deploy shell scripts. But now with platforms like the Raspberry Pi becoming very common, Linux shell scripts can be a big part of a system–even the whole system, in some cases. How do you know your shell script is error-free before you deploy it? Of course, nothing can catch all errors, but you might try ShellCheck.
  • Android: Enabling mainline graphics
    Android uses the HWC API to communicate with graphics hardware. This API is not supported on the mainline Linux graphics stack, but by using drm_hwcomposer as a shim it now is. The HWC (Hardware Composer) API is used by SurfaceFlinger for compositing layers to the screen. The HWC abstracts objects such as overlays and 2D blitters and helps offload some work that would normally be done with OpenGL. SurfaceFlinger on the other hand accepts buffers from multiple sources, composites them, and sends them to the display.
  • Collabora's Devs Make Android's HWC API Work in Mainline Linux Graphics Stack
    Collabora's Mark Filion informs Softpedia today about the latest work done by various Collabora developers in collaboration with Google's ChromeOS team to enable mainline graphics on Android. The latest blog post published by Collabora's Robert Foss reveals the fact that both team managed to develop a shim called drm_hwcomposer, which should enable Android's HWC (Hardware Composer) API to communicate with the graphics hardware, including Android 7.0's version 2 HWC API.