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

Bug#28062: marked as done (fmirror: umask trouble)



Your message dated Wed, 07 Mar 2001 14:56:21 -0500
with message-id <E14ak2n-0003aZ-00@auric.debian.org>
and subject line Bug#28062: fixed in fmirror 2:0.8.4-1
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.)

Darren Benham
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 16 Oct 1998 16:30:10 +0000
Received: (qmail 30403 invoked from network); 16 Oct 1998 16:30:08 -0000
Received: from hilfy.magd.cam.ac.uk (mail@131.111.221.99)
  by master.debian.org with SMTP; 16 Oct 1998 16:30:08 -0000
Received: from gpp10 by hilfy.magd.cam.ac.uk with local (Exim 2.04 #1)
	id 0zUClN-00075C-00 (Debian); Fri, 16 Oct 1998 17:30:01 +0100
From: Giuliano P Procida <gpp10@cam.ac.uk>
Subject: fmirror: umask trouble
To: submit@bugs.debian.org
X-Mailer: bug 3.1.6.1
Message-Id: <E0zUClN-00075C-00@hilfy.magd.cam.ac.uk>
Date: Fri, 16 Oct 1998 17:30:01 +0100

Package: fmirror
Version: 0.8.4beta-1

I specify a dirmode of 02770 (rwxrws---), but fmirror does not honour
this. The trace here is for a directory containing two files. The mask is
only interpreted as octal when preceded by a 0; this should be documented.

$ grep CREAT str.out 
open("/tmp/tmpf17842aaa", O_RDWR|O_CREAT|O_EXCL, 0666) = 4
open("/tmp/tmpf17842baa", O_RDWR|O_CREAT|O_EXCL, 0666) = 5
open("mydir/file1", O_WRONLY|O_CREAT|O_TRUNC, 0200) = 9
open("mydir/file2", O_WRONLY|O_CREAT|O_TRUNC, 0200) = 9

If the user's mask is set to a funny value other people might get to
play with the files in /tmp .

$ grep chmod str.out 
fchmod(9, 0660)                         = 0
fchmod(9, 0660)                         = 0

So the and-mask and or-mask are fine in the end.

$ grep mkdir str.out 
mkdir("mydir", 02770)                     = 0

Oops, this call always takes account of umask which I set to 002 but
which fmirror overrides with:

$ grep umask str.out 
umask(022)                              = 02

The result is that I do not get my directories the way I want them.

Two possible solutions are: ether set umask to 777 and be careful about
modes when creating files; or chmod directories after creation so they
get the right bits.

I hope this is of some use,
Giuliano Procida.

-- System Information
Debian Release: slink
Kernel Version: Linux hilfy 2.0.35 #8 Tue Sep 15 21:01:16 BST 1998 i686 unknown

---------------------------------------
Received: (at 28062-close) by bugs.debian.org; 7 Mar 2001 20:12:00 +0000
>From troup@auric.debian.org Wed Mar 07 14:12:00 2001
Return-path: <troup@auric.debian.org>
Received: from auric.debian.org [::ffff:206.246.226.45] 
	by master.debian.org with esmtp (Exim 3.12 1 (Debian))
	id 14akHw-0004mX-00; Wed, 07 Mar 2001 14:12:00 -0600
Received: from troup by auric.debian.org with local (Exim 3.12 1 (Debian))
	id 14ak2n-0003aZ-00; Wed, 07 Mar 2001 14:56:21 -0500
From: Debian QA Group <debian-qa@lists.debian.org>
To: 28062-close@bugs.debian.org
Subject: Bug#28062: fixed in fmirror 2:0.8.4-1
Message-Id: <E14ak2n-0003aZ-00@auric.debian.org>
Sender: James Troup <troup@auric.debian.org>
Date: Wed, 07 Mar 2001 14:56:21 -0500
Delivered-To: 28062-close@bugs.debian.org

We believe that the bug you reported is fixed in the latest version of
fmirror, which has been installed in the Debian FTP archive:

fmirror_0.8.4-1_i386.deb
  to pool/main/f/fmirror/fmirror_0.8.4-1_i386.deb
fmirror_0.8.4-1.dsc
  to pool/main/f/fmirror/fmirror_0.8.4-1.dsc
fmirror_0.8.4.orig.tar.gz
  to pool/main/f/fmirror/fmirror_0.8.4.orig.tar.gz
fmirror_0.8.4-1.diff.gz
  to pool/main/f/fmirror/fmirror_0.8.4-1.diff.gz
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 28062@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Debian QA Group <debian-qa@lists.debian.org> (supplier of updated fmirror 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, 20 Feb 2001 12:16:47 -0800
Source: fmirror
Binary: fmirror
Architecture: source i386
Version: 2:0.8.4-1
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group <debian-qa@lists.debian.org>
Changed-By: Sean 'Shaleh' Perry <shaleh@debian.org>
Description: 
 fmirror    - memory efficient ftp mirror program
Closes: 28062 48426 70990 78964 83464 85238
Changes: 
 fmirror (2:0.8.4-1) unstable; urgency=low
 .
   * New upstream release, Closes: #70990
   * man page typo corrected, Closes: #85238
   * removed README.Debian, it was useless, Closes: #83464
   * added a postrm that removes the /etc/fmirror dir, Closes: #78964
   * run_mirror not calls sed with -g for its conf handling, Closes: #48426
   * upstream fixed directory mode handling, Closes: #28062
   * gencontrol now called with -isp
   * cron.d entry is not +x anymore
   * orphan package as the maintainer is long MIA
Files: 
 764dd17d85045a05e3a50d9ee10dd46f 611 net optional fmirror_0.8.4-1.dsc
 78652ce5bb50e6c120c9ca0988cb9dca 59831 net optional fmirror_0.8.4.orig.tar.gz
 6f7b8feb4c92ddde6451f85c4a8e720b 9275 net optional fmirror_0.8.4-1.diff.gz
 edcef303a573a1aefc1023900b5d121a 41952 net optional fmirror_0.8.4-1_i386.deb

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

iEYEARECAAYFAjqmhxAACgkQ1GPU2Z7hbxsBwwCgh48OcvG6yowZjhOo7Ifa2fs5
TUwAoKQKxmdLYsCoR68kzCVcYOSoM43s
=euLW
-----END PGP SIGNATURE-----



Reply to: