Your message dated Wed, 21 Sep 2005 16:00:47 -0600
with message-id <[EMAIL PROTECTED]>
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)
--------------------------------------
Received: (at submit) by bugs.debian.org; 2 Feb 2004 12:05:22 +0000
>From [EMAIL PROTECTED] Mon Feb 02 04:05:22 2004
Return-path: <[EMAIL PROTECTED]>
Received: from m229.net195-132-237.noos.fr (hephaistos.nibelungen.rez)
[195.132.237.229]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1AncpN-0001IQ-00; Mon, 02 Feb 2004 04:05:21 -0800
Received: from [192.168.1.7] (helo=dionysos.nibelungen.rez)
by hephaistos.nibelungen.rez with esmtp (Exim 4.30)
id 1Ancom-0001LH-Dc
for [EMAIL PROTECTED]; Mon, 02 Feb 2004 13:04:44 +0100
Received: from moa by dionysos.nibelungen.rez with local (Exim 3.36 #1 (Debian))
id 1Ancop-0000vB-00
for <[EMAIL PROTECTED]>; Mon, 02 Feb 2004 13:04:47 +0100
From: Mathieu Roy <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: RFP: integcheck -- a system integrity checker
X-Debbugs-CC: Mathieu Roy <[EMAIL PROTECTED]>, debian-devel@lists.debian.org
X-GPG-Keyserver: http://pgp.mit.edu
X-GPG-Keynumber: 2DA199B9 2002-04-09
Date: Mon, 02 Feb 2004 13:04:46 +0100
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: Mathieu Roy <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_02_01
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=HAS_PACKAGE,X_DEBBUGS_CC
autolearn=no version=2.60-bugs.debian.org_2004_02_01
X-Spam-Level:
Package: wnpp
Severity: wishlist
* Package name : integcheck
Version : 1.0.0
Upstream Author : Mathieu Roy <[EMAIL PROTECTED]>
* 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 |
+---------------------------------------------------------------------+
---------------------------------------
Received: (at 230769-done) by bugs.debian.org; 21 Sep 2005 22:00:47 +0000
>From [EMAIL PROTECTED] Wed Sep 21 15:00:47 2005
Return-path: <[EMAIL PROTECTED]>
Received: from merkel.debian.org [192.25.206.16] (mail)
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1EICdz-00056J-00; Wed, 21 Sep 2005 15:00:47 -0700
Received: from damog by merkel.debian.org with local (Exim 3.36 1 (Debian))
id 1EICdz-0004Pc-00; Wed, 21 Sep 2005 16:00:47 -0600
To: [EMAIL PROTECTED]
Subject: WNPP bug closing
Message-Id: <[EMAIL PROTECTED]>
From: David Moreno Garza <[EMAIL PROTECTED]>
Date: Wed, 21 Sep 2005 16:00:47 -0600
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-5.0 required=4.0 tests=BAYES_00,VALID_BTS_CONTROL
autolearn=no version=2.60-bugs.debian.org_2005_01_02
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 450 days.
- It hasn't had any activity recently.
As this 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 [EMAIL PROTECTED]
with a body text like this:
reopen 230769
thanks bts
Further comments on the work done in the bug sent to
[EMAIL PROTECTED] 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: <[EMAIL PROTECTED]>.
This is the second massive wnpp closing that is being done. The next close
will be done on inactive RFPs older than 365 days and finally, an automatic
script will close, by default, *inactive* RFPs when they reach one year of
inactivity.
A similar process is being applied to other kind of wnpp bugs.
Thanks for your cooperation,
-- David Moreno Garza <[EMAIL PROTECTED]> Wed, 20 Sep 2005 17:06:42 -0500
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
