Tripwire可以对要求校验的系统文件进行类似md5的运行，而生成一个唯一的标识，即“快照”snapshot。当这些系统文件的大小、inode号、权限、时间等任意属性被修改后，再次运行Tripwire，其会进行前后属性的对比，并生成相关的详细报告。
系统：CentOS release 6.4
软件：tripwire-2.4.2.2
一、下载安装软件
wget http://nchc.dl.sourceforge.net/project/tripwire/tripwire-src/tripwire-2.4.2.2/tripwire-2.4.2.2-src.tar.bz2
# 下载文件
tar jxvf tripwire-2.4.2.2-src.tar.bz2
# 解压文件
cd tripwire-2.4.2.2-src
# 进入解压的文件夹
./configure –prefix=/usr/local/tripwire
# 将tripwire安装在/usr/local/tripwire目录中
make
# 编译，下面省略过程…………过程中可能会出现缺少gcc，gcc-c++编译软件的情况，请自行yum install 安装
make install
#====================安装过程开始====================
# 编译后的安装 ……以下过程省略，注意红色字体部分
Making install in man
make[1]: Entering directory `/root/tripwire-2.4.2.2-src/man’
Making install in man4
make[2]: Entering directory `/root/tripwire-2.4.2.2-src/man/man4′
make[3]: Entering directory `/root/tripwire-2.4.2.2-src/man/man4′
make[3]: Nothing to be done for `install-exec-am’.
test -z “/usr/local/tripwire/share/man/man4” || mkdir -p — . “/usr/local/tripwire/share/man/man4”
/usr/bin/install -c -m 644 ‘./twconfig.4’ ‘/usr/local/tripwire/share/man/man4/twconfig.4’
/usr/bin/install -c -m 644 ‘./twpolicy.4’ ‘/usr/local/tripwire/share/man/man4/twpolicy.4’
make[3]: Leaving directory `/root/tripwire-2.4.2.2-src/man/man4′
make[2]: Leaving directory `/root/tripwire-2.4.2.2-src/man/man4′
Making install in man5
make[2]: Entering directory `/root/tripwire-2.4.2.2-src/man/man5′
make[3]: Entering directory `/root/tripwire-2.4.2.2-src/man/man5′
make[3]: Nothing to be done for `install-exec-am’.
test -z “/usr/local/tripwire/share/man/man5” || mkdir -p — . “/usr/local/tripwire/share/man/man5”
/usr/bin/install -c -m 644 ‘./twfiles.5’ ‘/usr/local/tripwire/share/man/man5/twfiles.5’
make[3]: Leaving directory `/root/tripwire-2.4.2.2-src/man/man5′
make[2]: Leaving directory `/root/tripwire-2.4.2.2-src/man/man5′
Making install in man8
make[2]: Entering directory `/root/tripwire-2.4.2.2-src/man/man8′
make[3]: Entering directory `/root/tripwire-2.4.2.2-src/man/man8′
make[3]: Nothing to be done for `install-exec-am’.
test -z “/usr/local/tripwire/share/man/man8” || mkdir -p — . “/usr/local/tripwire/share/man/man8”
/usr/bin/install -c -m 644 ‘./siggen.8’ ‘/usr/local/tripwire/share/man/man8/siggen.8’
/usr/bin/install -c -m 644 ‘./tripwire.8’ ‘/usr/local/tripwire/share/man/man8/tripwire.8’
/usr/bin/install -c -m 644 ‘./twadmin.8’ ‘/usr/local/tripwire/share/man/man8/twadmin.8’
/usr/bin/install -c -m 644 ‘./twintro.8’ ‘/usr/local/tripwire/share/man/man8/twintro.8’
/usr/bin/install -c -m 644 ‘./twprint.8’ ‘/usr/local/tripwire/share/man/man8/twprint.8’
make[3]: Leaving directory `/root/tripwire-2.4.2.2-src/man/man8′
make[2]: Leaving directory `/root/tripwire-2.4.2.2-src/man/man8′
make[2]: Entering directory `/root/tripwire-2.4.2.2-src/man’
make[3]: Entering directory `/root/tripwire-2.4.2.2-src/man’
make[3]: Nothing to be done for `install-exec-am’.
make[3]: Nothing to be done for `install-data-am’.
make[3]: Leaving directory `/root/tripwire-2.4.2.2-src/man’
make[2]: Leaving directory `/root/tripwire-2.4.2.2-src/man’
make[1]: Leaving directory `/root/tripwire-2.4.2.2-src/man’
Making install in src
make[1]: Entering directory `/root/tripwire-2.4.2.2-src/src’
Making install in cryptlib
make[2]: Entering directory `/root/tripwire-2.4.2.2-src/src/cryptlib’
make[3]: Entering directory `/root/tripwire-2.4.2.2-src/src/cryptlib’
make[3]: Nothing to be done for `install-exec-am’.
make[3]: Nothing to be done for `install-data-am’.
make[3]: Leaving directory `/root/tripwire-2.4.2.2-src/src/cryptlib’
make[2]: Leaving directory `/root/tripwire-2.4.2.2-src/src/cryptlib’
Making install in core
make[2]: Entering directory `/root/tripwire-2.4.2.2-src/src/core’
make[3]: Entering directory `/root/tripwire-2.4.2.2-src/src/core’
make[3]: Nothing to be done for `install-exec-am’.
make[3]: Nothing to be done for `install-data-am’.
make[3]: Leaving directory `/root/tripwire-2.4.2.2-src/src/core’
make[2]: Leaving directory `/root/tripwire-2.4.2.2-src/src/core’
Making install in db
make[2]: Entering directory `/root/tripwire-2.4.2.2-src/src/db’
make[3]: Entering directory `/root/tripwire-2.4.2.2-src/src/db’
make[3]: Nothing to be done for `install-exec-am’.
make[3]: Nothing to be done for `install-data-am’.
make[3]: Leaving directory `/root/tripwire-2.4.2.2-src/src/db’
make[2]: Leaving directory `/root/tripwire-2.4.2.2-src/src/db’
Making install in fco
make[2]: Entering directory `/root/tripwire-2.4.2.2-src/src/fco’
make[3]: Entering directory `/root/tripwire-2.4.2.2-src/src/fco’
make[3]: Nothing to be done for `install-exec-am’.
make[3]: Nothing to be done for `install-data-am’.
make[3]: Leaving directory `/root/tripwire-2.4.2.2-src/src/fco’
make[2]: Leaving directory `/root/tripwire-2.4.2.2-src/src/fco’
Making install in fs
make[2]: Entering directory `/root/tripwire-2.4.2.2-src/src/fs’
make[3]: Entering directory `/root/tripwire-2.4.2.2-src/src/fs’
make[3]: Nothing to be done for `install-exec-am’.
make[3]: Nothing to be done for `install-data-am’.
make[3]: Leaving directory `/root/tripwire-2.4.2.2-src/src/fs’
make[2]: Leaving directory `/root/tripwire-2.4.2.2-src/src/fs’
Making install in tw
make[2]: Entering directory `/root/tripwire-2.4.2.2-src/src/tw’
make[3]: Entering directory `/root/tripwire-2.4.2.2-src/src/tw’
make[3]: Nothing to be done for `install-exec-am’.
make[3]: Nothing to be done for `install-data-am’.
make[3]: Leaving directory `/root/tripwire-2.4.2.2-src/src/tw’
make[2]: Leaving directory `/root/tripwire-2.4.2.2-src/src/tw’
Making install in twcrypto
make[2]: Entering directory `/root/tripwire-2.4.2.2-src/src/twcrypto’
make[3]: Entering directory `/root/tripwire-2.4.2.2-src/src/twcrypto’
make[3]: Nothing to be done for `install-exec-am’.
make[3]: Nothing to be done for `install-data-am’.
make[3]: Leaving directory `/root/tripwire-2.4.2.2-src/src/twcrypto’
make[2]: Leaving directory `/root/tripwire-2.4.2.2-src/src/twcrypto’
Making install in twparser
make[2]: Entering directory `/root/tripwire-2.4.2.2-src/src/twparser’
make[3]: Entering directory `/root/tripwire-2.4.2.2-src/src/twparser’
make[3]: Nothing to be done for `install-exec-am’.
make[3]: Nothing to be done for `install-data-am’.
make[3]: Leaving directory `/root/tripwire-2.4.2.2-src/src/twparser’
make[2]: Leaving directory `/root/tripwire-2.4.2.2-src/src/twparser’
Making install in util
make[2]: Entering directory `/root/tripwire-2.4.2.2-src/src/util’
make[3]: Entering directory `/root/tripwire-2.4.2.2-src/src/util’
make[3]: Nothing to be done for `install-exec-am’.
make[3]: Nothing to be done for `install-data-am’.
make[3]: Leaving directory `/root/tripwire-2.4.2.2-src/src/util’
make[2]: Leaving directory `/root/tripwire-2.4.2.2-src/src/util’
Making install in twprint
make[2]: Entering directory `/root/tripwire-2.4.2.2-src/src/twprint’
make[3]: Entering directory `/root/tripwire-2.4.2.2-src/src/twprint’
test -z “/usr/local/tripwire/sbin” || mkdir -p — . “/usr/local/tripwire/sbin”
/usr/bin/install -c ‘twprint’ ‘/usr/local/tripwire/sbin/twprint’
make[3]: Nothing to be done for `install-data-am’.
make[3]: Leaving directory `/root/tripwire-2.4.2.2-src/src/twprint’
make[2]: Leaving directory `/root/tripwire-2.4.2.2-src/src/twprint’
Making install in twadmin
make[2]: Entering directory `/root/tripwire-2.4.2.2-src/src/twadmin’
make[3]: Entering directory `/root/tripwire-2.4.2.2-src/src/twadmin’
test -z “/usr/local/tripwire/sbin” || mkdir -p — . “/usr/local/tripwire/sbin”
/usr/bin/install -c ‘twadmin’ ‘/usr/local/tripwire/sbin/twadmin’
make[3]: Nothing to be done for `install-data-am’.
make[3]: Leaving directory `/root/tripwire-2.4.2.2-src/src/twadmin’
make[2]: Leaving directory `/root/tripwire-2.4.2.2-src/src/twadmin’
Making install in siggen
make[2]: Entering directory `/root/tripwire-2.4.2.2-src/src/siggen’
make[3]: Entering directory `/root/tripwire-2.4.2.2-src/src/siggen’
test -z “/usr/local/tripwire/sbin” || mkdir -p — . “/usr/local/tripwire/sbin”
/usr/bin/install -c ‘siggen’ ‘/usr/local/tripwire/sbin/siggen’
make[3]: Nothing to be done for `install-data-am’.
make[3]: Leaving directory `/root/tripwire-2.4.2.2-src/src/siggen’
make[2]: Leaving directory `/root/tripwire-2.4.2.2-src/src/siggen’
Making install in tripwire
make[2]: Entering directory `/root/tripwire-2.4.2.2-src/src/tripwire’
make[3]: Entering directory `/root/tripwire-2.4.2.2-src/src/tripwire’
test -z “/usr/local/tripwire/sbin” || mkdir -p — . “/usr/local/tripwire/sbin”
/usr/bin/install -c ‘tripwire’ ‘/usr/local/tripwire/sbin/tripwire’
make[3]: Nothing to be done for `install-data-am’.
make[3]: Leaving directory `/root/tripwire-2.4.2.2-src/src/tripwire’
make[2]: Leaving directory `/root/tripwire-2.4.2.2-src/src/tripwire’
make[2]: Entering directory `/root/tripwire-2.4.2.2-src/src’
make[3]: Entering directory `/root/tripwire-2.4.2.2-src/src’
make[3]: Nothing to be done for `install-exec-am’.
make[3]: Nothing to be done for `install-data-am’.
make[3]: Leaving directory `/root/tripwire-2.4.2.2-src/src’
make[2]: Leaving directory `/root/tripwire-2.4.2.2-src/src’
make[1]: Leaving directory `/root/tripwire-2.4.2.2-src/src’
make[1]: Entering directory `/root/tripwire-2.4.2.2-src’
make[2]: Entering directory `/root/tripwire-2.4.2.2-src’
make[2]: Nothing to be done for `install-exec-am’.
make install-data-hook
make[3]: Entering directory `/root/tripwire-2.4.2.2-src’
prefix=”/usr/local/tripwire” sysconfdir=”/usr/local/tripwire/etc”
path_to_vi=”/bin/vi” path_to_sendmail=”/usr/sbin/sendmail”
./install/install.sh
Installer program for:
Tripwire(R) 2.4 Open Source
Copyright (C) 1998-2000 Tripwire (R) Security Systems, Inc. Tripwire (R)
is a registered trademark of the Purdue Research Foundation and is
licensed exclusively to Tripwire (R) Security Systems, Inc.
LICENSE AGREEMENT for Tripwire(R) 2.4 Open Source
Please read the following license agreement. You must accept the
agreement to continue installing Tripwire.
Press ENTER to view the License Agreement.
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
License is intended to guarantee your freedom to share and change free
software–to make sure the software is free for all its users. This
General Public License applies to most of the Free Software
Foundation’s software and to any other program whose authors commit to
using it. (Some other Free Software Foundation software is covered by
the GNU Library General Public License instead.) You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. You must make sure that they, too, receive or can get the
source code. And you must show them these terms so they know their
rights.
We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.
Also, for each author’s protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors’ reputations.
Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that redistributors of a free
program will individually obtain patent licenses, in effect making the
program proprietary. To prevent this, we have made it clear that any
patent must be licensed for everyone’s free use or not licensed at all.
The precise terms and conditions for copying, distribution and
modification follow.
^L
GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains
a notice placed by the copyright holder saying it may be distributed
under the terms of this General Public License. The “Program”, below,
refers to any such program or work, and a “work based on the Program”
means either the Program or any derivative work under copyright law:
that is to say, a work containing the Program or a portion of it,
either verbatim or with modifications and/or translated into another
language. (Hereinafter, translation is included without limitation in
the term “modification”.) Each licensee is addressed as “you”.
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running the Program is not restricted, and the output from the Program
is covered only if its contents constitute a work based on the
Program (independent of having been made by running the Program).
Whether that is true depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program’s
source code as you receive it, in any medium, provided that you
conspicuously and appropriately publish on each copy an appropriate
copyright notice and disclaimer of warranty; keep intact all the
notices that refer to this License and to the absence of any warranty;
and give any other recipients of the Program a copy of this License
along with the Program.
You may charge a fee for the physical act of transferring a copy, and
you may at your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion
of it, thus forming a work based on the Program, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) You must cause the modified files to carry prominent notices
stating that you changed the files and the date of any change.
b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.
c) If the modified program normally reads commands interactively
when run, you must cause it, when started running for such
interactive use in the most ordinary way, to print or display an
announcement including an appropriate copyright notice and a
notice that there is no warranty (or else, saying that you provide
a warranty) and that users may redistribute the program under
these conditions, and telling the user how to view a copy of this
License. (Exception: if the Program itself is interactive but
does not normally print such an announcement, your work based on
the Program is not required to print an announcement.)
^L
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Program.
In addition, mere aggregation of another work not based on the Program
with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
3. You may copy and distribute the Program (or a work based on it,
under Section 2) in object code or executable form under the terms of
Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of Sections
1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your
cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be
distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer
to distribute corresponding source code. (This alternative is
allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such
an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for
making modifications to it. For an executable work, complete source
code means all the source code for all modules it contains, plus any
associated interface definition files, plus the scripts used to
control compilation and installation of the executable. However, as a
special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary
form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component
itself accompanies the executable.
If distribution of executable or object code is made by offering
access to copy from a designated place, then offering equivalent
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.
^L
4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
void, and will automatically terminate your rights under this License.
However, parties who have received copies, or rights, from you under
this License will not have their licenses terminated so long as such
parties remain in full compliance.
5. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Program or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Program (or any work based on the
Program), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Program or works based on it.
6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the
original licensor to copy, distribute or modify the Program subject to
these terms and conditions. You may not impose any further
restrictions on the recipients’ exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.
7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Program at all. For example, if a patent
license would not permit royalty-free redistribution of the Program by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply and the section as a whole is intended to apply in other
circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
^L
8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding
those countries, so that distribution is permitted only in or among
countries not thus excluded. In such case, this License incorporates
the limitation as if written in the body of this License.
9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the Program
specifies a version number of this License which applies to it and “any
later version”, you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation. If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.
10. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission. For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this. Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS
—————————
Tripwire Trademark Information
The developer of the original code and/or files is Tripwire, Inc. Portions
created by Tripwire, Inc. are copyright 2000 Tripwire, Inc. Tripwire is a
registered trademark of Tripwire, Inc. All rights reserved.
This program is free software. The contents of this file are subject to the
terms of the GNU General Public License as published by the Free Software
Foundation; either version 2 of the License, or (at your option) any later
version. You may redistribute it and/or modify it only in compliance with the
GNU General Public License.
This program is distributed in the hope that it will be useful. However, this
program is distributed “AS-IS” WITHOUT ANY WARRANTY; INCLUDING THE IMPLIED
WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Please see
the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with
this program; if not, write to the Free Software Foundation, Inc., 59 Temple
Place – Suite 330, Boston, MA 02111-1307, USA.
Nothing in the GNU General Public License or any other license to use the code
or files shall permit you to use Tripwire’s trademarks, service marks, or
other intellectual property without Tripwire’s prior written consent.
If you have any questions, please contact Tripwire, Inc. at either
info@tripwire.org or www.tripwire.org.
End of Tripwire Trademark Information
———————————————
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the “copyright” line and a pointer to where the full notice is found.
<one line to give the program’s name and a brief idea of what it does.>
Copyright (C) 19yy <name of author>
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Also add information on how to contact you by electronic and paper mail.
If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) 19yy name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w’.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c’ for details.
The hypothetical commands `show w’ and `show c’ should show the appropriate
parts of the General Public License. Of course, the commands you use may
be called something other than `show w’ and `show c’; they could even be
mouse-clicks or menu items–whatever suits your program.
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a “copyright disclaimer” for the program, if
necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the program
`Gnomovision’ (which makes passes at compilers) written by James Hacker.
<signature of Ty Coon>, 1 April 1989
Ty Coon, President of Vice
This General Public License does not permit incorporating your program into
proprietary programs. If your program is a subroutine library, you may
consider it more useful to permit linking proprietary applications with the
library. If this is what you want to do, use the GNU Library General
Public License instead of this License.
Please type “accept” to indicate your acceptance of this
license agreement. [do not accept] accept 表示同意
Using configuration file ./install/install.cfg
Checking for programs specified in install configuration file….
/usr/sbin/sendmail -oi -t exists. Continuing installation.
/bin/vi exists. Continuing installation.
———————————————-
Verifying existence of binaries…
./bin/siggen found
./bin/tripwire found
./bin/twprint found
./bin/twadmin found
This program will copy Tripwire files to the following directories:
TWBIN: /usr/local/tripwire/sbin
TWMAN: /usr/local/tripwire/man
TWPOLICY: /usr/local/tripwire/etc
TWREPORT: /usr/local/tripwire/lib/tripwire/report
TWDB: /usr/local/tripwire/lib/tripwire
TWSITEKEYDIR: /usr/local/tripwire/etc
TWLOCALKEYDIR: /usr/local/tripwire/etc
CLOBBER is false.
Continue with installation? [y/n] y 输入y
———————————————-
Creating directories…
/usr/local/tripwire/sbin: already exists
/usr/local/tripwire/etc: created
/usr/local/tripwire/lib/tripwire/report: created
/usr/local/tripwire/lib/tripwire: already exists
/usr/local/tripwire/etc: already exists
/usr/local/tripwire/etc: already exists
/usr/local/tripwire/man: created
/usr/local/tripwire/doc/tripwire: created
———————————————-
Copying files…
/usr/local/tripwire/doc/tripwire/COPYING: copied
/usr/local/tripwire/doc/tripwire/TRADEMARK: copied
/usr/local/tripwire/doc/tripwire/policyguide.txt: copied
/usr/local/tripwire/etc/twpol-Linux.txt: copied
———————————————-
The Tripwire site and local passphrases are used to
sign a variety of files, such as the configuration,
policy, and database files.
Passphrases should be at least 8 characters in length
and contain both letters and numbers.
See the Tripwire manual for more information.
———————————————-
Creating key files…
(When selecting a passphrase, keep in mind that good passphrases typically
have upper and lower case letters, digits and punctuation marks, and are
at least 8 characters in length.)
Enter the site keyfile passphrase: #这里输入site keyfile 密钥，必须要记住
Verify the site keyfile passphrase: #这里再次输入site keyfile 密钥，必须要记住
Generating key (this may take several minutes)…Key generation complete.
(When selecting a passphrase, keep in mind that good passphrases typically
have upper and lower case letters, digits and punctuation marks, and are
at least 8 characters in length.)
Enter the local keyfile passphrase: #这里输入local keyfile 密钥，必须要记住
Verify the local keyfile passphrase: #这里再次输入local keyfile 密钥，必须要记住
Generating key (this may take several minutes)…Key generation complete.
———————————————-
Generating Tripwire configuration file…
———————————————-
Creating signed configuration file…
Please enter your site passphrase: #请输入你的 site keyfile密钥
Wrote configuration file: /usr/local/tripwire/etc/tw.cfg
A clear-text version of the Tripwire configuration file
/usr/local/tripwire/etc/twcfg.txt
has been preserved for your inspection. It is recommended
that you delete this file manually after you have examined it.
———————————————-
Customizing default policy file…
———————————————-
Creating signed policy file…
Please enter your site passphrase: #请输入你的 site keyfile密钥
Wrote policy file: /usr/local/tripwire/etc/tw.pol
A clear-text version of the Tripwire policy file
/usr/local/tripwire/etc/twpol.txt
has been preserved for your inspection. This implements
a minimal policy, intended only to test essential
Tripwire functionality. You should edit the policy file
to describe your system, and then use twadmin to generate
a new signed copy of the Tripwire policy.
———————————————-
The installation succeeded.
Please refer to
for release information and to the printed user documentation
for further instructions on using Tripwire 2.4 Open Source.
make[3]: Leaving directory `/root/tripwire-2.4.2.2-src’
make[2]: Leaving directory `/root/tripwire-2.4.2.2-src’
make[1]: Leaving directory `/root/tripwire-2.4.2.2-src’
#====================安装过程结束====================
配置文件：定义数据库、策略文件和Tripwire可执行文件的位置：
/usr/local/tripwire/etc/twcfg.txt
策略：定义检测的对象及违规时采取的行为：
/usr/local/tripwire/etc/twpol.txt
数据库：用于存放生成的快照：
/usr/local/tripwire/lib/tripwire/$(HOSTNAME).twd
另外，Tripwire为了自身的安全，防止自身被篡改，也会对自身进行加密和签名处理。其中，包括两个密钥：
site密钥：用于保护策略文件和配置文件，只要使用相同的策略和配置的机器，都可以使用相同的site密钥：
/usr/local/tripwire/etcsite.key
local密钥：用户保护数据库和分析报告，这肯定不会重复的：
/usr/local/tripwire/etc/$(HOSTNAME)-local.key
二.设置tripwire
vi /etc/tripwire/twcfg.txt ← 修改文本格式的Tripwire配置文件
LOOSEDIRECTORYCHECKING =false ← 找到这一个行，将false的值变为true（不监测所属目录的数据完整性）
↓
LOOSEDIRECTORYCHECKING =true ← 变为此状态
REPORTLEVEL =3 ← 找到这一行，将3变为4（改变监测结果报告的等级）
↓
REPORTLEVEL =4 ← 变为此状态
#/usr/local/tripwire/sbin/twadmin –create-cfgfile -S site.key twcfg.txt ← 从文本配置文件建立加密格式配
置文件
Please enter your site passphrase: ← 输入“site keyfile”口令
Wrote configuration file: /usr/local/tripwire/etc/tw.cfg
编辑twpol.txt来控制对哪些目录进行检查,把不需要扫描的路径注释或删除即可.
修改完成后保存twpool.txt文件。
三.初始化数据库
#/usr/local/tripwire/sbin/tripwire –init
Please enter your local passphrase: ← 输入“local keyfile”口令
Parsing policy file: /usr/local/tripwire/etc/tw.pol
Generating the database…
*** Processing Unix File System ***
The object: “/sys” is on a different file system…ignoring.
——————-
——过程———
——省略———
——————-
Wrote database file: /usr/local/tripwire/lib/tripwire/localhost.localdomain.twd
The database was successfully generated.
四.更新数据库
当你更新了twpol.txt后需用此命令更新数据库
cd /usr/local/tripwire
#./sbin/tripwire –update-policy –secure-mode low /usr/local/tripwire/etc/twpol.txt
Parsing policy file: /usr/local/tripwire/etc/twpol.txt
Please enter your local passphrase: ← 输入“local keyfile”口令
Please enter your site passphrase: ← 输入“site keyfile”口令
======== Policy Update: Processing section Unix File System.
======== Step 1: Gathering information for the new policy.
The object: “/sys” is on a different file system…ignoring.
——————-
——过程———
——省略———
——————-
### Continuing…
Wrote database file: /usr/local/tripwire/lib/tripwire/localhost.localdomain.twd
The database was successfully generated.
五.检查文件异动
安装完tripwire后你可以定期检查文件是否存在异动
加上interactive在当前显示结果
./sbin/tripwire –check –interactive
Parsing policy file: /usr/local/tripwire/etc/tw.pol
*** Processing Unix File System ***
——————-
——过程———
——省略———
——————-
六.查看报告
所有tripwire的报告以.twr后缀保存在lib/tripwire目录下，需要使用twprint命令来转化成文本格式
#/sbin/twprint –print-report –twrfile /lib/tripwire/report/localhost.localdomain-20100225-
164220.twr>/tmp/tripwire_readable.txt
#cat /tmp/tripwire_readable.txt
七.修改环境变量
需要注意的是，一般情况下，这仅仅对于普通用户适用，避免修改根用户的环境定义文件，因为那样可能会造成潜在的危险。
$vi .bash_profile #修改环境变量定义文件。
然后编辑你的PATH声明，其格式为：
PATH=$PATH:/usr/local/tripwire/sbin/
执行命令使其立刻生效
$source .bash_profile
Tripwire的使用和维护都比较简单。但要实现对系统的监控，关键还是需要依靠管理员定制完整的策略和检查周期，以
便及时发现问题。另外，Tripwire只能告诉您那些文件被修改，以及修改的属性。