Your message dated Wed, 31 Aug 2005 05:32:08 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#325468: fixed in polygen 1.0.6-9
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; 28 Aug 2005 21:41:11 +0000
>From [EMAIL PROTECTED] Sun Aug 28 14:41:11 2005
Return-path: <[EMAIL PROTECTED]>
Received: from anchor-post-35.mail.demon.net [194.217.242.85]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1E9Utp-0000lK-00; Sun, 28 Aug 2005 14:41:09 -0700
Received: from xibalba.demon.co.uk ([80.176.227.229])
by anchor-post-35.mail.demon.net with esmtp (Exim 4.42)
id 1E9Uop-0008Ja-Iz
for [EMAIL PROTECTED]; Sun, 28 Aug 2005 21:35:59 +0000
Date: Sun, 28 Aug 2005 22:41:52 +0100
From: Justin B Rye <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: polygen: ignores umask
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Reportbug-Version: 3.8
User-Agent: Mutt/1.5.9i
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=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Package: polygen
Version: 1.0.6-7
Severity: critical
Tags: security
Justification: root security hole
/var/lib/dpkg/info/polygen-data.postinst invokes /usr/bin/polygen on
all its /usr/share/polygen/*/*.grm data files to create corresponding
.grm.o files. Unfortunately polygen ignores the umask and creates
all these output files with a mode of 0666.
On Sat, Aug 13, Enrico Zini wrote:
> Oh! That's a bad bug, security-related, critical severity. Could you
> please report it?
Sorry about the delay. I can't see quite how the exploit would
work, even as a "grave" user-versus-user attack, but it smells
vaguely of buffer-overflow risk as well as being a violation of
policy 10.9 and generally bad behaviour.
-- System Information:
Debian Release: 3.1
Architecture: i386 (i586)
Kernel: Linux 2.6.11.hurakan
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Versions of packages polygen depends on:
ii ocaml-base-nox [ocaml-base-no 3.08.3-3 Runtime system for ocaml bytecode
-- no debconf information
--
JBR
Ankh kak! (Ancient Egyptian blessing)
---------------------------------------
Received: (at 325468-close) by bugs.debian.org; 31 Aug 2005 12:39:19 +0000
>From [EMAIL PROTECTED] Wed Aug 31 05:39:19 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
id 1EARlA-0007zT-00; Wed, 31 Aug 2005 05:32:08 -0700
From: Enrico Zini <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#325468: fixed in polygen 1.0.6-9
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Wed, 31 Aug 2005 05:32:08 -0700
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=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Source: polygen
Source-Version: 1.0.6-9
We believe that the bug you reported is fixed in the latest version of
polygen, which is due to be installed in the Debian FTP archive:
polygen-data_1.0.6-9_all.deb
to pool/main/p/polygen/polygen-data_1.0.6-9_all.deb
polygen_1.0.6-9.diff.gz
to pool/main/p/polygen/polygen_1.0.6-9.diff.gz
polygen_1.0.6-9.dsc
to pool/main/p/polygen/polygen_1.0.6-9.dsc
polygen_1.0.6-9_all.deb
to pool/main/p/polygen/polygen_1.0.6-9_all.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Enrico Zini <[EMAIL PROTECTED]> (supplier of updated polygen package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Wed, 31 Aug 2005 13:34:20 +0200
Source: polygen
Binary: polygen-data polygen
Architecture: source all
Version: 1.0.6-9
Distribution: unstable
Urgency: high
Maintainer: Enrico Zini <[EMAIL PROTECTED]>
Changed-By: Enrico Zini <[EMAIL PROTECTED]>
Description:
polygen - generator of random sentences from grammar definitions
polygen-data - grammar definitions for PolyGen
Closes: 325468
Changes:
polygen (1.0.6-9) unstable; urgency=high
.
* Directly install the .grm.o files built at build time, and remove the need
for postinst and postrm. It removes the annoying delays at install time,
and really closes: #325468.
* Urgency set to high since we close a security bug (hopefully for real this
time).
* Need a postinst to compensate for previously existing broken postrm from
previous polygens
Files:
0fac411f0057bb6e3162451461917bd0 612 games optional polygen_1.0.6-9.dsc
2e19d5448d27431c92649d2a92df4ea9 4292 games optional polygen_1.0.6-9.diff.gz
e4d20c44192d2ce6a72cb580a5e61432 86008 games optional polygen_1.0.6-9_all.deb
3cc8bc7faef0ec100ff298ac2a42a481 1250868 games optional
polygen-data_1.0.6-9_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFDFaDu9LSwzHl+v6sRAqGvAJ4pZNsw5b4N+dvHAuwK/yMMYBT3WgCghMGk
0LxRlIVNSawtxDvbMgGLUt0=
=fTsA
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
