[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#115108: marked as done (liblockdev1: questionable and useless umask(0))



Your message dated Tue, 09 Apr 2002 10:32:27 -0400
with message-id <E16uwfb-0001tx-00@auric.debian.org>
and subject line Bug#115108: fixed in lockdev 1.0.1-4
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; 10 Oct 2001 08:20:10 +0000
>From Enrik.Berkhan@planb.de Wed Oct 10 03:20:10 2001
Return-path: <Enrik.Berkhan@planb.de>
Received: from visby.remote.org (mail.remote.org) [212.227.14.25] (mail)
	by master.debian.org with esmtp (Exim 3.12 1 (Debian))
	id 15rEb4-000280-00; Wed, 10 Oct 2001 03:20:10 -0500
Received: from electra.intern.planb.de (andromeda.planb.de [212.227.19.14])
	by mail.remote.org with esmtp 
	id 15rEb2-0000RV-00; Wed, 10 Oct 2001 10:20:08 +0200
From: Enrik Berkhan <Enrik.Berkhan@planb.de>
Subject: liblockdev1: questionable and useless umask(0)
To: submit@bugs.debian.org
X-Mailer: bug 3.3.10
Message-Id: <E15rEb2-00038I-00@electra.intern.planb.de>
Date: Wed, 10 Oct 2001 10:20:08 +0200
Delivered-To: submit@bugs.debian.org

Package: liblockdev1
Version: 1.0.1-3
Severity: important

Hi,

liblockdev creates device lockfiles with full permissions using umask(00).
A quote from the changelog:

>   * added change in umask value to allow full permissions to lock 
>     files.  (this is questionable: would it be better to add a 
>     suid program to check and remove dangling locks?)

This is in fact questionable and even useless as the directory /var/lock/
is ususally sticky. So only root can delete foreign dangling locks anyway.

Suggestion: Remove umask(2) calls and leave removal of foreign dangling
locks to the system admin.

-- System Information
Debian Release: testing/unstable
Kernel Version: Linux electra 2.4.10-686 #1 Sat Sep 29 19:30:50 EST 2001 i686 unknown

Versions of the packages liblockdev1 depends on:
ii  libc6          2.2.4-3        GNU C Library: Shared libraries and Timezone

---------------------------------------
Received: (at 115108-close) by bugs.debian.org; 9 Apr 2002 14:38:49 +0000
>From katie@auric.debian.org Tue Apr 09 09:38:49 2002
Return-path: <katie@auric.debian.org>
Received: from auric.debian.org [206.246.226.45] (mail)
	by master.debian.org with esmtp (Exim 3.12 1 (Debian))
	id 16uwll-00076I-00; Tue, 09 Apr 2002 09:38:49 -0500
Received: from katie by auric.debian.org with local (Exim 3.12 1 (Debian))
	id 16uwfb-0001tx-00; Tue, 09 Apr 2002 10:32:27 -0400
From: Pawel Wiecek <coven@debian.org>
To: 115108-close@bugs.debian.org
X-Katie: $Revision: 1.10 $
Subject: Bug#115108: fixed in lockdev 1.0.1-4
Message-Id: <E16uwfb-0001tx-00@auric.debian.org>
Sender: Archive Administrator <katie@auric.debian.org>
Date: Tue, 09 Apr 2002 10:32:27 -0400
Delivered-To: 115108-close@bugs.debian.org

We believe that the bug you reported is fixed in the latest version of
lockdev, which is due to be installed in the Debian FTP archive:

liblockdev1-dbg_1.0.1-4_i386.deb
  to pool/main/l/lockdev/liblockdev1-dbg_1.0.1-4_i386.deb
liblockdev1-dev_1.0.1-4_i386.deb
  to pool/main/l/lockdev/liblockdev1-dev_1.0.1-4_i386.deb
liblockdev1-perl_1.0.1-4_i386.deb
  to pool/main/l/lockdev/liblockdev1-perl_1.0.1-4_i386.deb
liblockdev1_1.0.1-4_i386.deb
  to pool/main/l/lockdev/liblockdev1_1.0.1-4_i386.deb
lockdev_1.0.1-4.diff.gz
  to pool/main/l/lockdev/lockdev_1.0.1-4.diff.gz
lockdev_1.0.1-4.dsc
  to pool/main/l/lockdev/lockdev_1.0.1-4.dsc



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 115108@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Pawel Wiecek <coven@debian.org> (supplier of updated lockdev 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 ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Tue,  9 Apr 2002 14:39:54 +0200
Source: lockdev
Binary: liblockdev1-perl liblockdev1-dev liblockdev1 liblockdev1-dbg
Architecture: source i386
Version: 1.0.1-4
Distribution: unstable
Urgency: low
Maintainer: Pawel Wiecek <coven@debian.org>
Changed-By: Pawel Wiecek <coven@debian.org>
Description: 
 liblockdev1 - Run-time shared library for locking devices.
 liblockdev1-dbg - Debugging library for locking devices.
 liblockdev1-dev - Development library for locking devices.
 liblockdev1-perl - perl extension library for locking devices.
Closes: 112558 115108
Changes: 
 lockdev (1.0.1-4) unstable; urgency=low
 .
   * New maintainer (closes: #112558)
   * Removed umask calls (closes: #115108)
   * Now calls ldconfig in postrm instead of prerm
Files: 
 bcc7da131bbb1504eaf472d69d748564 678 libs optional lockdev_1.0.1-4.dsc
 cb02b9c8c72ce9fecf39f5c40c1ad3ce 8587 libs optional lockdev_1.0.1-4.diff.gz
 84a39871ca677c0f745270b26fc6fb57 10746 libs optional liblockdev1_1.0.1-4_i386.deb
 e175c152c0801f767dc374f06f45a699 8184 devel optional liblockdev1-dev_1.0.1-4_i386.deb
 d658a7404ce2cc0447f52e2c45f1f712 66846 devel optional liblockdev1-dbg_1.0.1-4_i386.deb
 c3b75b1edab2c3f5b827b87734bcd15c 17810 interpreters optional liblockdev1-perl_1.0.1-4_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8su4hBOdjEO/Bh3ARAlTAAJsEpv9o7s9A+wYLcEsrbbi+EEyu5ACggjwp
Isg3KUoiwMm9Yn4/aCD8IUY=
=ujWJ
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to debian-qa-packages-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org



Reply to: