HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Tripwire not sending out emails
Operating System - HP-UX
1832651
Members
2660
Online
110043
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
12-05-2008 08:03 AM
12-05-2008 08:03 AM
Tripwire not sending out emails
Have installed Tripwire from the Internet Express suite in a HP-UX v3 environment. I have created the config and policy files and its detecting the changes to files. But it wont send out an email.
I did the email test and it was successful. This is what my policy looks like
@@section FS
SEC_CRIT = $(IgnoreNone)-SHa ; # Critical files that cannot change
SEC_SUID = $(IgnoreNone)-SHa ; # Binaries with the SUID or SGID flags set
SEC_BIN = $(ReadOnly) ; # Binaries that should not change
SEC_CONFIG = $(Dynamic) ; # Config files that are changed infrequently but accessed often
SEC_LOG = $(Growing) ; # Files that grow, but that should never change ownership
SEC_INVARIANT = +tpug ; # Directories that should never change permission or ownership
SIG_LOW = 33 ; # Non-critical files that are of minimal security impact
SIG_MED = 66 ; # Non-critical files that are of significant security impact
SIG_HI = 100 ; # Critical files that are significant points of vulnerability
MAILTO = root ;
(
rulename = "Critical configuration files",
severity = $(SIG_HI),
emailto = $(MAILTO)
)
{
/etc/cron -> $(SEC_BIN) ;
/etc/default/cron -> $(SEC_BIN) ;
/etc/default -> $(SEC_BIN) ;
/etc/fstab -> $(SEC_BIN) ;
/etc/sbtab -> $(SEC_BIN) ;
/etc/fsdb -> $(SEC_BIN) ;
/etc/group -> $(SEC_BIN) ; # changes should be infrequent
/etc/protocols -> $(SEC_BIN) ;
/etc/services -> $(SEC_BIN) ;
/etc/services.window -> $(SEC_BIN) ;
/etc/rc.config.d/ -> $(SEC_BIN) ;
/etc/passwd -> $(SEC_CONFIG) ;
/etc/rpc -> $(SEC_BIN) ;
/etc/conf -> $(SEC_BIN) ;
/etc/sam -> $(SEC_BIN) ;
/etc/sam/custom -> $(SEC_BIN) ;
/etc/opt/samba/smb.conf -> $(SEC_CONFIG) ;
/etc/nsswitch.compat -> $(SEC_BIN) ;
/etc/nsswitch.hp_defaults -> $(SEC_BIN) ;
/etc/hosts -> $(SEC_CONFIG) ;
/etc/inittab -> $(SEC_CONFIG) ;
/etc/resolv.conf -> $(SEC_CONFIG) ;
/etc/syslog.conf -> $(SEC_CONFIG) ;
/etc/networks -> $(SEC_CONFIG) ;
}
Dont know where else to look. I saw one other post here with the same issue, but no resolution. Any ideas ?
I did the email test and it was successful. This is what my policy looks like
@@section FS
SEC_CRIT = $(IgnoreNone)-SHa ; # Critical files that cannot change
SEC_SUID = $(IgnoreNone)-SHa ; # Binaries with the SUID or SGID flags set
SEC_BIN = $(ReadOnly) ; # Binaries that should not change
SEC_CONFIG = $(Dynamic) ; # Config files that are changed infrequently but accessed often
SEC_LOG = $(Growing) ; # Files that grow, but that should never change ownership
SEC_INVARIANT = +tpug ; # Directories that should never change permission or ownership
SIG_LOW = 33 ; # Non-critical files that are of minimal security impact
SIG_MED = 66 ; # Non-critical files that are of significant security impact
SIG_HI = 100 ; # Critical files that are significant points of vulnerability
MAILTO = root ;
(
rulename = "Critical configuration files",
severity = $(SIG_HI),
emailto = $(MAILTO)
)
{
/etc/cron -> $(SEC_BIN) ;
/etc/default/cron -> $(SEC_BIN) ;
/etc/default -> $(SEC_BIN) ;
/etc/fstab -> $(SEC_BIN) ;
/etc/sbtab -> $(SEC_BIN) ;
/etc/fsdb -> $(SEC_BIN) ;
/etc/group -> $(SEC_BIN) ; # changes should be infrequent
/etc/protocols -> $(SEC_BIN) ;
/etc/services -> $(SEC_BIN) ;
/etc/services.window -> $(SEC_BIN) ;
/etc/rc.config.d/ -> $(SEC_BIN) ;
/etc/passwd -> $(SEC_CONFIG) ;
/etc/rpc -> $(SEC_BIN) ;
/etc/conf -> $(SEC_BIN) ;
/etc/sam -> $(SEC_BIN) ;
/etc/sam/custom -> $(SEC_BIN) ;
/etc/opt/samba/smb.conf -> $(SEC_CONFIG) ;
/etc/nsswitch.compat -> $(SEC_BIN) ;
/etc/nsswitch.hp_defaults -> $(SEC_BIN) ;
/etc/hosts -> $(SEC_CONFIG) ;
/etc/inittab -> $(SEC_CONFIG) ;
/etc/resolv.conf -> $(SEC_CONFIG) ;
/etc/syslog.conf -> $(SEC_CONFIG) ;
/etc/networks -> $(SEC_CONFIG) ;
}
Dont know where else to look. I saw one other post here with the same issue, but no resolution. Any ideas ?
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-05-2008 11:01 AM
12-05-2008 11:01 AM
Re: Tripwire not sending out emails
OK. I put the integrity check in cron and got the email. Weird it doesnt work on the command line.
So now the report that I get is basically the full tripwire report, without a subject. It would be nice if you could tailor the email alert.
So now the report that I get is basically the full tripwire report, without a subject. It would be nice if you could tailor the email alert.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-07-2008 01:30 AM
12-07-2008 01:30 AM
Re: Tripwire not sending out emails
Hello,
Simple solution that works well:
a) Run the test as follows:
# tripwire --check | mail -s "`date '+%Y-%m-%d' | awk '{print}'` Tripwire Report" mysefl@mydomain.dom
b) From memory, the other solution involves
changing the config from:
MAILMETHOD =SENDMAIL
SYSLOGREPORTING =false
MAILPROGRAM =/usr/sbin/sendmail -oi -t
To, for example:
MAILMETHOD =SENDMAIL
SYSLOGREPORTING =false
MAILPROGRAM =/bin/mail
Recompile the configs, and then
run:
# tripwire --check -M
Cheers,
VK2COT
Simple solution that works well:
a) Run the test as follows:
# tripwire --check | mail -s "`date '+%Y-%m-%d' | awk '{print}'` Tripwire Report" mysefl@mydomain.dom
b) From memory, the other solution involves
changing the config from:
MAILMETHOD =SENDMAIL
SYSLOGREPORTING =false
MAILPROGRAM =/usr/sbin/sendmail -oi -t
To, for example:
MAILMETHOD =SENDMAIL
SYSLOGREPORTING =false
MAILPROGRAM =/bin/mail
Recompile the configs, and then
run:
# tripwire --check -M
Cheers,
VK2COT
VK2COT - Dusan Baljevic
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-07-2008 01:36 AM
12-07-2008 01:36 AM
Re: Tripwire not sending out emails
One more comment. The option b) works fine.
Do not forget to add the following option
into the policy file:
Original line:
severity = $(SIG_HI)
New line:
severity = $(SIG_HI), emailto=user@mydomain.dom
Here is the Subject: line in the email
report by default:
Subject: TWReport myhost.mydomain.dom 20081207201230 V:74 S:100 A:0 R:0
C:74
Cheers,
VK2COT
Do not forget to add the following option
into the policy file:
Original line:
severity = $(SIG_HI)
New line:
severity = $(SIG_HI), emailto=user@mydomain.dom
Here is the Subject: line in the email
report by default:
Subject: TWReport myhost.mydomain.dom 20081207201230 V:74 S:100 A:0 R:0
C:74
Cheers,
VK2COT
VK2COT - Dusan Baljevic
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