Package: ucf Version: 2.005 Severity: normal -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
hi manoj, try something like the following to get the idea of what i'm talking about: dmesg > /tmp/foo ucf /tmp/foo/something[wierd] good so far, but then: ucf --purge /tmp/foo/something[wierd] the file is not purged. taking a glancing look through the source, it looks like the file is passed almost verbatim to grep, which would explain things. similarly, other strangly concocted filenames could have similar result, i don't think there's any way this could be more than annoying and pathological corner case (no security or catastrophic possibilities as far as i can see). - -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-686 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages ucf depends on: ii debconf [debconf-2.0] 1.4.71 Debian configuration management sy Versions of packages ucf recommends: ii debconf-utils 1.4.71 debconf utilities - -- debconf-show failed -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFETTG9ynjLPm522B0RAhhqAJoCg+dnwgGmwj9kKpyBigdxuI6NdACeL3nv bQODyTLUV4x+r7z2Mejefoo= =uwl2 -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
