Bug#230769: marked as done (RFP: integcheck -- a system integrity checker)
Your message dated Mon, 01 Oct 2007 12:00:29 -0600
with message-id <E1IcPZF-0004Dm-4W@merkel.debian.org>
and subject line WNPP bug closing
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: RFP: integcheck -- a system integrity checker
- From: Mathieu Roy <yeupou@gnu.org>
- Date: Mon, 02 Feb 2004 13:04:46 +0100
- Message-id: <m3isipn0v5.fsf@dionysos.nibelungen.rez>
Package: wnpp
Severity: wishlist
* Package name : integcheck
Version : 1.0.0
Upstream Author : Mathieu Roy <yeupou@gnu.org>
* URL or Web page : https://gna.org/projects/integcheck/
* License : GNU GPL
Description : a system integrity checker
Item check is written in Perl.
The idea is to check integrity of exposed systems by getting a list
of md5 of any important file via ssh, to keep this list on a pretty
safe system (a system that do not run any server publicly
available), and, finally, to compare everyday this list and with the
previous one.
As long as the system considered as safe is not compromised, it
should inform administrators of any changes on the others systems.
As others integrity checker, if its own components are corrupted, it
can be fooled. In others words, you cannot have a security policy
entirely relying on an integrity checker, and you should always do
manual checks regularly to be sure that the integrity checker is not
corrupted itself.
So what's the point of this tool, if you are still forced to do
manual checks? In fact, it is way faster to check integrity of
integcheck than integrity of the whole system.
On every system you want to monitor, you have to install the
integcheck-victim package, and on one computer, at least, you must
have to install the integheck-bobby package.
The integcheck-victim package provide a specific shell. The
integcheck-bobby provide cronjob and scripts to get and compare md5
list.
Integcheck is already packaged, using debconf, however the package
is not the cleanest possible and some documentation would probably
be a nice addition. If someone was willing to package integcheck for
Debian, we would gladly collaborate with him, by giving him write
access to the repository directly.
--
Mathieu Roy
+---------------------------------------------------------------------+
| General Homepage: http://yeupou.coleumes.org/ |
| Computing Homepage: http://alberich.coleumes.org/ |
| Not a native english speaker: |
| http://stock.coleumes.org/doc.php?i=/misc-files/flawed-english |
+---------------------------------------------------------------------+
--- End Message ---
--- Begin Message ---
Hello,
This is an automatic mail sent to close the RFP you have reported or
are involved with.
Your RFP wnpp bug is being closed because of the following reasons:
- It is, as of today, older than 365 days.
- It hasn't had any activity recently.
As this is an automatic procedure, it could of course have something
wrong and probably it would be closing some bugs that are not
intended by owners and submitters (like you) to be closed, for
example if the RFP is still of your interest, or there has been
some kind of activity around it. In that case, please reopen the
bug, do it, DO IT NOW! (I don't want to be blamed because of
mass closing and not let people know that they can easily reopen
their bugs ;-).
To re-open it, you simply have to mail control@bugs.debian.org
with a body text like this:
reopen 230769
stop
Further comments on the work done in the bug sent to
230769@bugs.debian.org would be truly welcomed.
Anyway, if you have any kind of problems when dealing with
the BTS, feel free to contact me and I'd be more than happy to help
you on this: <damog@debian.org>.
A similar process is being applied to other kind of wnpp bugs.
Thanks for your cooperation,
-- David Moreno Garza <damog@debian.org>.
--- End Message ---
Reply to: