- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Security issue: cpqhealth in non-module kernels do...
ProLiant Servers (ML,DL,SL)
1752805
Members
5546
Online
108789
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-30-2003 08:24 AM
10-30-2003 08:24 AM
Security issue: cpqhealth in non-module kernels doesn't work
We integrated cpqasm and cpqevt (from hpasm-6.40.0-16.Redhat8_0.i386.rpm) into our
self-compiled linux-2.4.22 kernel image (to linux/drivers/cpqhealth).
In my attachment, you can see the patches we did.
After booting we can access /proc/cpqfan but we get only a header.
The module-version of cpqhealth give the status of all fans.
In the attachment there are our dmesg-boot-messages as well.
At our site we a running our linux servers without module-support.
Modules are the number-one rootkit hooks. We even protect our /dev/kmem etc
with the grsecurity.net-patch.
Because we don't want to lower out security level, we would have to stop our
migration process from our netservers to proliants..!
In order to succeed, we need a casm/cevt that works in 2.4.22 kernel images.
Sincerely,
Matthias
self-compiled linux-2.4.22 kernel image (to linux/drivers/cpqhealth).
In my attachment, you can see the patches we did.
After booting we can access /proc/cpqfan but we get only a header.
The module-version of cpqhealth give the status of all fans.
In the attachment there are our dmesg-boot-messages as well.
At our site we a running our linux servers without module-support.
Modules are the number-one rootkit hooks. We even protect our /dev/kmem etc
with the grsecurity.net-patch.
Because we don't want to lower out security level, we would have to stop our
migration process from our netservers to proliants..!
In order to succeed, we need a casm/cevt that works in 2.4.22 kernel images.
Sincerely,
Matthias
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP