<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to feature-requests</title><link href="https://sourceforge.net/p/tripwire/feature-requests/" rel="alternate"/><link href="https://sourceforge.net/p/tripwire/feature-requests/feed.atom" rel="self"/><id>https://sourceforge.net/p/tripwire/feature-requests/</id><updated>2018-10-20T21:09:05.549000Z</updated><subtitle>Recent changes to feature-requests</subtitle><entry><title>We've moved!</title><link href="https://sourceforge.net/p/tripwire/feature-requests/16/" rel="alternate"/><published>2018-10-20T21:09:05.549000Z</published><updated>2018-10-20T21:09:05.549000Z</updated><author><name>Brian Cox</name><uri>https://sourceforge.net/u/brc0x1/</uri></author><id>https://sourceforge.net879c8bcd2faa86997f9f6a26c311e2d1aa975388</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi everyone, Open Source Tripwire has moved to Github: &lt;a href="https://github.com/Tripwire/tripwire-open-source" rel="nofollow"&gt;https://github.com/Tripwire/tripwire-open-source&lt;/a&gt; .  The current version available (v2.4.3.7) builds with modern compilers and incorporates a number of bug fixes &amp;amp; feature requests, with broader platform support.  I’m not an admin for this SourceForge project &amp;amp; can’t update the source here, so the project here will be increasingly out of date as time goes on.  I also don’t check SourceForge regularly, so please direct questions, comments, bug reports, etc, to the Github repo.&lt;/p&gt;
&lt;p&gt;Thanks,&lt;br/&gt;
-b&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Webmin module or GUI</title><link href="https://sourceforge.net/p/tripwire/feature-requests/15/" rel="alternate"/><published>2012-11-22T21:42:47Z</published><updated>2012-11-22T21:42:47Z</updated><author><name>Lorenzo</name><uri>https://sourceforge.net/u/laspada/</uri></author><id>https://sourceforge.net0804ef98c80405a232ee207b9a6d800a8f86775e</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I would realy like to have a sort of GUI or a webmin module to manage tripwire.&lt;br /&gt;
Would that be feasible?&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>--root parameter for checking chroot-Sub-Environments</title><link href="https://sourceforge.net/p/tripwire/feature-requests/14/" rel="alternate"/><published>2012-03-11T13:13:35Z</published><updated>2012-03-11T13:13:35Z</updated><author><name/><uri>https://sourceforge.net</uri></author><id>https://sourceforge.netd3bdffb72da627e8aa92599d39225f878c8cdc49</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;For my server I use OpenVZ for virtualisation. This means: my system has a lot of chroot environments under /var/lib/vz/private/* which I want to include into tripwires configuration. The virtual containers themselves should not contain any traces to tripwire - I want to check them from the host file system.&lt;/p&gt;
&lt;p&gt;I could do that by extending the policy file by about 10 almost redundant copies of itself. But this is not what a policy file should be. My /etc/tripwire/twpol.txt would look like this:&lt;br /&gt;
$ grep -E 'rulename.*Other libraries|/usr/lib' /etc/tripwire/twpol.txt&lt;br /&gt;
rulename = "Other libraries",&lt;br /&gt;
/usr/lib    -&amp;gt; $(SEC_BIN) ;&lt;br /&gt;
rulename = "Subsystem 123, Other libraries",&lt;br /&gt;
/var/lib/vz/private/123/usr/lib -&amp;gt; $(SEC_BIN) ;&lt;br /&gt;
rulename = "Subsystem 125, Other libraries",&lt;br /&gt;
/var/lib/vz/private/125/usr/lib -&amp;gt; $(SEC_BIN) ;&lt;br /&gt;
rulename = "Subsystem 631, Other libraries",&lt;br /&gt;
/var/lib/vz/private/631/usr/lib -&amp;gt; $(SEC_BIN) ;&lt;/p&gt;
&lt;p&gt;I'd rather like to create just one policy file for all VMs and let tripwire substitute their paths by using a command line option like --root. Example:&lt;br /&gt;
tripwire -m c -p /etc/tripwire/tw-vm.pol -d /var/lib/tripwire/vm-123.twd --root /var/lib/vz/private/123/&lt;br /&gt;
tripwire -m c -p /etc/tripwire/tw-vm.pol -d /var/lib/tripwire/vm-125.twd --root /var/lib/vz/private/125/&lt;br /&gt;
tripwire -m c -p /etc/tripwire/tw-vm.pol -d /var/lib/tripwire/vm-631.twd --root /var/lib/vz/private/631/&lt;/p&gt;
&lt;p&gt;Other examples of programs which support this option (I'm using debian):&lt;br /&gt;
debsums:&lt;br /&gt;
-r, --root=DIR               root directory to check (default /)&lt;br /&gt;
dpkg:&lt;br /&gt;
--root=&amp;lt;directory&amp;gt;         Install on a different root directory.&lt;/p&gt;
&lt;p&gt;The -c, -p, -d options etc. should still be relative to the path of the host system.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>tripwire for specific dir and run custom script on change</title><link href="https://sourceforge.net/p/tripwire/feature-requests/13/" rel="alternate"/><published>2011-02-17T21:06:23Z</published><updated>2011-02-17T21:06:23Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.net4150a35e423d7e3225427d517b36fcf4ce83aa00</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;i would really like to see tripwire scan a specific directory for the hashes e.g www/ folder and instead of just email you should be able to configure a script to run on change. e.g if you have a static website and someone uploads a shell to your server tripwire will run your custom script (which i would make it delete the files on the server) and the email should say what was changed. THAT would be PERFECT&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Management page</title><link href="https://sourceforge.net/p/tripwire/feature-requests/12/" rel="alternate"/><published>2011-01-26T03:38:27Z</published><updated>2011-01-26T03:38:27Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.netedc1c4530479f4a26503156a9e53765054886534</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Manage Tripwire via a web page instead of only CLI&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Support for ACLs and xattrs (OSX et al)</title><link href="https://sourceforge.net/p/tripwire/feature-requests/11/" rel="alternate"/><published>2008-08-04T16:25:28Z</published><updated>2008-08-04T16:25:28Z</updated><author><name>Chevy</name><uri>https://sourceforge.net/u/monzav8/</uri></author><id>https://sourceforge.net6cd7aa6d0b2ee380ba3697f071342276b36c3b06</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;New versions of OSX (10.4+) support larger amounts of metadata for each inode.  In particular, they support Access Control Lists and arbitrary extended attributes.  ACLs, in particular, make a massive difference in OSX 10.5, since they are checked before POSIX permission metadata.&lt;/p&gt;
&lt;p&gt;It doesn't look like there is much active development being done on Tripwire these days, but I still trust this code base more than any of the newcomers (particularly because no newcomer has emerged in the security community as a trusted alternative).&lt;/p&gt;
&lt;p&gt;Other than a series of warning messages, Tripwire 2.4.1 still compiles and runs fine on OSX 10.5.4.  If no developers are working towards support of ACLs and xattrs, I may try to add code for these myself.  I found some sample code that shows OSX's use of the calls for these features.&lt;/p&gt;
&lt;p&gt;But my code modification skills are 10 years rusty, and the last time I tweaked Tripwire it was still in C.&lt;/p&gt;
&lt;p&gt;Is anyone working on support for ACLs and xattrs, or am I on my own?&lt;/p&gt;
&lt;p&gt;And if I have to make a tweak myself, how do I submit it to this project?&lt;/p&gt;
&lt;p&gt;Thanks for all the hard work on such a vital tool.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>print digest of created report</title><link href="https://sourceforge.net/p/tripwire/feature-requests/10/" rel="alternate"/><published>2005-11-19T05:25:07Z</published><updated>2005-11-19T05:25:07Z</updated><author><name>Michael D. Leonhard</name><uri>https://sourceforge.net/u/mleonhard/</uri></author><id>https://sourceforge.net3c3993b6f9b5ac5bb7a27bcae54551a08999d446</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;The typical tripwire installation has tripwire running&lt;br /&gt;
from a cron job.  It checks the current filesystem&lt;br /&gt;
against the database and creates a signed report.  The&lt;br /&gt;
output from this process is emailed to the host's&lt;br /&gt;
administrators.&lt;/p&gt;
&lt;p&gt;Now imagine that the system is compromised and the&lt;br /&gt;
tripwire binary is replaced.  It seems to me that the&lt;br /&gt;
attacker could replace the existing tripwire reports. &lt;br /&gt;
After the attack is discovered, the admins will have no&lt;br /&gt;
way to know which reports are to be trusted.  This&lt;br /&gt;
indicates a need to copy the reports off the machine,&lt;br /&gt;
to a secure location.  For those situations where&lt;br /&gt;
automatic or manual copying are not feasible, perhaps a&lt;br /&gt;
cryptographic hash of the report file would suffice?&lt;/p&gt;
&lt;p&gt;I propose that tripwire should output the SHA-1 hash of&lt;br /&gt;
the report file after it is written to disk.  Cron&lt;br /&gt;
would then email this information to the&lt;br /&gt;
administrators, where it would be carried off the&lt;br /&gt;
server, to a safe location.  If the machine is later&lt;br /&gt;
cracked, report validity could be&lt;br /&gt;
checked by comparing the SHA-1 digests of the files with&lt;br /&gt;
the previously generated emails.&lt;/p&gt;
&lt;p&gt;-Michael&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Please enable the use of MAILFROMADDRESS.</title><link href="https://sourceforge.net/p/tripwire/feature-requests/9/" rel="alternate"/><published>2005-11-02T06:37:29Z</published><updated>2005-11-02T06:37:29Z</updated><author><name>Mic5100</name><uri>https://sourceforge.net/u/mic5100/</uri></author><id>https://sourceforge.net7e970aa8df066416ea2e8df7b64b5b0a0d21a461</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Please enable the use of MAILFROMADDRESS with &lt;br /&gt;
ConfigFile twcfg.txt(tw.&lt;br /&gt;
cfg) as well as tripwire of the product version. &lt;/p&gt;
&lt;p&gt;Transmission person's information is refused from &lt;br /&gt;
FireWall in my &lt;br /&gt;
environment and it is not possible to transmit. &lt;br /&gt;
In present open source, it &lt;br /&gt;
becomes "user@host.domain", the transmission &lt;br /&gt;
host name is seen, and I do not think the viewpoint of &lt;br /&gt;
security to be &lt;br /&gt;
preferable. &lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Make syslog report level configurable</title><link href="https://sourceforge.net/p/tripwire/feature-requests/8/" rel="alternate"/><published>2005-01-27T13:24:40Z</published><updated>2005-01-27T13:24:40Z</updated><author><name>McSpedon</name><uri>https://sourceforge.net/u/mcspedon/</uri></author><id>https://sourceforge.net5f6567c04967183435c06c5a8bf4f694aa840520</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;The Tripwire information that is ouput to syslog (when&lt;br /&gt;
SYSLOGREPORTING=true) is summary only (level 0). And it&lt;br /&gt;
is not configurable.  A lot of us depend on syslog&lt;br /&gt;
information more than email. Why not make the syslog&lt;br /&gt;
report level configurable in the config file, the same&lt;br /&gt;
way the email report level is configurable?&lt;/p&gt;
&lt;p&gt;e.g.,  SYSLOGREPORTLEVEL=3&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>user definable 'mail from' to emailreport</title><link href="https://sourceforge.net/p/tripwire/feature-requests/7/" rel="alternate"/><published>2003-08-12T14:18:40Z</published><updated>2003-08-12T14:18:40Z</updated><author><name/><uri>https://sourceforge.net</uri></author><id>https://sourceforge.net0a5b8a5b70a97ee6f01649690888a0be44744a6a</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;It would be good to be able to define the sender that&lt;br /&gt;
gets put to email reports. We would only need to add&lt;br /&gt;
new (optional) line to tw.cfg, like 'MAILFROM =&lt;br /&gt;
myname@mydomain.com' and the check if it exists.&lt;br /&gt;
Normally we don't need this but sometimes there's&lt;br /&gt;
machines which don't return reasonable data from&lt;br /&gt;
hostname and then the mailer on the other end refuses&lt;br /&gt;
the mail (i'm talking about a situation where you&lt;br /&gt;
either have no control of the mailserver or other&lt;br /&gt;
reasons to not reconfigure it other way).&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>