HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- security_patch_check catalog
Operating System - HP-UX
1836361
Members
2973
Online
110100
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
Forums
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
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
04-03-2002 06:34 AM
04-03-2002 06:34 AM
security_patch_check catalog
Hi,
running the security_patch_check tool with a current security_catalog file from today I realized a change in behaviour compared to older revisions. (at least I believe it was different, before...)
Many patches were recommended to be installed, which apparently were from the "current" column of the security patch matrix, rather than "original". From my understanding this will result in unnecessary patching, as only the "original" patches (or any of their successors) should be required for fixing security holes, but not always the latest and greatest ones in a patch family.
Does anyone know why the catalog selection was done this way?
Cheers!
Michael
running the security_patch_check tool with a current security_catalog file from today I realized a change in behaviour compared to older revisions. (at least I believe it was different, before...)
Many patches were recommended to be installed, which apparently were from the "current" column of the security patch matrix, rather than "original". From my understanding this will result in unnecessary patching, as only the "original" patches (or any of their successors) should be required for fixing security holes, but not always the latest and greatest ones in a patch family.
Does anyone know why the catalog selection was done this way?
Cheers!
Michael
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP