Package: chkrootkit Version: N/A Severity: normal Tags: patch Dear Debian maintainer,
On Thursday, February 07, 2008, I notified you of the beginning of a review process concerning debconf templates for chkrootkit. The debian-l10n-english contributors have now reviewed these templates, and the proposed changes are attached to this bug report. Please review the suggested changes are suggested, and if you have any objections, let me know in the next 3 days. Please try to avoid uploading chkrootkit with these changes right now. The second phase of this process will begin on Monday, February 25, 2008, when I will coordinate updates to translations of debconf templates. The existing translators will be notified of the changes: they will receive an updated PO file for their language. Simultaneously, a general call for new translations will be sent to the debian-i18n mailing list. Both these calls for translations will request updates to be sent as individual bug reports. That will probably trigger a lot of bug reports against your package, but these should be easier to deal with. The call for translation updates and new translations will run until about Monday, March 17, 2008. Please avoid uploading a package with fixed or changed debconf templates and/or translation updates in the meantime. Of course, other changes are safe. Please note that this is an approximative delay, which depends on my own availability to process this work and is influenced by the fact that I simultaneously work on many packages. Around Tuesday, March 18, 2008, I will contact you again and will send a final patch summarizing all the updates (changes to debconf templates, updates to debconf translations and new debconf translations). Again, thanks for your attention and cooperation. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash
--- chkrootkit.old/debian/templates 2008-01-25 06:11:55.793191524 +0100 +++ chkrootkit/debian/templates 2008-02-22 07:08:55.684666088 +0100 @@ -1,25 +1,35 @@ +# These templates have been reviewed by the debian-l10n-english +# team +# +# If modifications/additions/rewording are needed, please ask +# [EMAIL PROTECTED] for advice. +# +# Even minor modifications require translation updates and such +# changes should be coordinated with translators and reviewers. + Template: chkrootkit/run_daily Type: boolean Default: false -_Description: Would you like to run chkrootkit automatically every day? - chkrootkit can be run automatically via cron.daily if you like. If you - answer yes to this question, you'll also be given the opportunity to +_Description: Should chkrootkit be run automatically every day? + The chkrootkit program can be run automatically via a daily cron job. If you + choose this option, you'll also be given the opportunity to specify options for the daily run. Template: chkrootkit/run_daily_opts Type: string -_Default: -q -_Description: What arguments would you like to pass to the daily chkrootkit run? +Default: -q +_Description: Arguments to use with chkrootkit in the daily run: The following are useful arguments to pass to chkrookit: - * -r <root> specifies an alternate root directory - * -n do not attempt to analyze nfs mounted files - * -q run in quiet mode [highly recommended] + -r <root>: use an alternate root directory; + -n : do not attempt to analyze NFS-mounted files; + -q : run in quiet mode [highly recommended]. Template: chkrootkit/diff_mode Type: boolean Default: false -_Description: Only report problems if they differ from yesterday's problems? - Choosing yes here instructs the cron.daily call of chkrootkit to - only report problems if they differ from the previous day's run. +_Description: Only report problems if they differ from previous day's problems? + If you choose this option, chkrootkit will + only report problems when they differ from the previous day's run. . - Use this option with care. + Using this option is not recommended as it is likely to hide existing + security problems. --- chkrootkit.old/debian/control 2008-01-25 06:11:55.793191524 +0100 +++ chkrootkit/debian/control 2008-02-19 19:30:02.401924954 +0100 @@ -4,25 +4,20 @@ Maintainer: lantz moore <[EMAIL PROTECTED]> Standards-Version: 3.6.2 Build-Depends: debhelper (>> 4.0.0), libc6.1-dev [ia64], po-debconf +Homepage: http://www.chkrootkit.org/ Package: chkrootkit Architecture: any Depends: ${shlibs:Depends}, binutils, net-tools, debconf | debconf-2.0, procps -Description: Checks for signs of rootkits on the local system - chkrootkit identifies whether the target computer is infected with a rootkit. - Some of the rootkits that chkrootkit identifies are: - 1. lrk3, lrk4, lrk5, lrk6 (and some variants); - 2. Solaris rootkit; - 3. FreeBSD rootkit; - 4. t0rn (including latest variant); - 5. Ambient's Rootkit for Linux (ARK); - 6. Ramen Worm; - 7. rh[67]-shaper; - 8. RSHA; - 9. Romanian rootkit; - 10. RK17; - 11. Lion Worm; - 12. Adore Worm. - Please note that this is not a definitive test, it does not ensure that the - target has not been cracked. In addition to running chkrootkit, one should - perform more specific tests. +Description: rootkit detector + The chkrootkit security scanner searches the local system for signs + that it is infected with a 'rootkit'. Rootkits are set of programs + and hacks designed to take control of a target machine by using known + security flaws. + . + Types that chkrootkit can identify are listed on the project's home page. + . + Please note that where chkrootkit detects no intrusions, this does + not guarantee that the system is uncompromised. In addition to + running chkrootkit, more specific tests should always be performed. +
