HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- hardening a system with nddconf
Operating System - HP-UX
1833780
Members
2886
Online
110063
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
08-05-2009 10:12 AM
08-05-2009 10:12 AM
hardening a system with nddconf
Using HP-UX 11i v1 on J-Class workstations, I wish to know if any advanced security pro's can suggest any additional entries to /etc/rc.config.d/nddconf to harden the system. Currently my configuration is:
TRANSPORT_NAME[0]=ip
NDD_NAME[0]=ip_ire_gw_probe
NDD_VALUE[0]=0
TRANSPORT_NAME[1]=ip
NDD_NAME[1]=ip_send_source_quench
NDD_VALUE[1]=0
TRANSPORT_NAME[2]=ip
NDD_NAME[2]=ip_forward_src_routed
NDD_VALUE[2]=0
TRANSPORT_NAME[3]=tcp
NDD_NAME[3]=tcp_conn_request_max
NDD_VALUE[3]=4096
TRANSPORT_NAME[4]=ip
NDD_NAME[4]=ip_forwarding
NDD_VALUE[4]=0
TRANSPORT_NAME[5]=ip
NDD_NAME[5]=ip_forward_directed_broadcasts
NDD_VALUE[5]=0
TRANSPORT_NAME[6]=tcp
NDD_NAME[6]=tcp_syn_rcvd_max
NDD_VALUE[6]=1000
TRANSPORT_NAME[7]=ip
NDD_NAME[7]=ip_pmtu_strategy
NDD_VALUE[7]=1
TRANSPORT_NAME[8]=ip
NDD_NAME[8]=ip_send_redirects
NDD_VALUE[8]=0
TRANSPORT_NAME[9]=ip
NDD_NAME[9]=ip_respond_to_echo_broadcast
NDD_VALUE[9]=0
TRANSPORT_NAME[10]=arp
NDD_NAME[10]=arp_cleanup_interval
NDD_VALUE[10]=60000
Thanks.
TRANSPORT_NAME[0]=ip
NDD_NAME[0]=ip_ire_gw_probe
NDD_VALUE[0]=0
TRANSPORT_NAME[1]=ip
NDD_NAME[1]=ip_send_source_quench
NDD_VALUE[1]=0
TRANSPORT_NAME[2]=ip
NDD_NAME[2]=ip_forward_src_routed
NDD_VALUE[2]=0
TRANSPORT_NAME[3]=tcp
NDD_NAME[3]=tcp_conn_request_max
NDD_VALUE[3]=4096
TRANSPORT_NAME[4]=ip
NDD_NAME[4]=ip_forwarding
NDD_VALUE[4]=0
TRANSPORT_NAME[5]=ip
NDD_NAME[5]=ip_forward_directed_broadcasts
NDD_VALUE[5]=0
TRANSPORT_NAME[6]=tcp
NDD_NAME[6]=tcp_syn_rcvd_max
NDD_VALUE[6]=1000
TRANSPORT_NAME[7]=ip
NDD_NAME[7]=ip_pmtu_strategy
NDD_VALUE[7]=1
TRANSPORT_NAME[8]=ip
NDD_NAME[8]=ip_send_redirects
NDD_VALUE[8]=0
TRANSPORT_NAME[9]=ip
NDD_NAME[9]=ip_respond_to_echo_broadcast
NDD_VALUE[9]=0
TRANSPORT_NAME[10]=arp
NDD_NAME[10]=arp_cleanup_interval
NDD_VALUE[10]=60000
Thanks.
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