[Pkg-samba-maint] r995 - trunk

[Steve Langasek]

On Tue, Jan 24, 2006 at 11:46:40PM +0000, Peter Eisentraut wrote:
> Added: trunk/smbfs.lintian
> ===================================================================
> --- trunk/smbfs.lintian	2006-01-24 22:43:20 UTC (rev 994)
> +++ trunk/smbfs.lintian	2006-01-24 23:46:39 UTC (rev 995)
> @@ -0,0 +1,4 @@
> +smbfs: setuid-binary sbin/mount.cifs 4755 root/root
> +smbfs: setuid-binary sbin/umount.cifs 4755 root/root
> +smbfs: setuid-binary usr/bin/smbumount 4755 root/root
> +smbfs: setuid-binary usr/bin/smbmnt 4755 root/root

I have been resisting this because suid binaries are a big deal, and I'm not
really all that comfortable with the audit status of the binaries in
question.  Has anybody even looked at sbin/umount.cifs to make sure it's
safe to have it suid root?  I know we have users that have *asked* for this,
but just because mount.cifs supports particular kinds of user mounts when
suid doesn't mean it's safe to do so.

> Modified: trunk/source.lintian-overrides
> ===================================================================
> --- trunk/source.lintian-overrides	2006-01-24 22:43:20 UTC (rev 994)
> +++ trunk/source.lintian-overrides	2006-01-24 23:46:39 UTC (rev 995)
> @@ -1,11 +1,12 @@
> -samba source: invalid-arch-string-in-source-relation m32r
> -samba source: invalid-arch-string-in-source-relation s390x
> -samba source: invalid-arch-string-in-source-relation sh3
> -samba source: invalid-arch-string-in-source-relation sh3eb
> -samba source: invalid-arch-string-in-source-relation sh4
> -samba source: invalid-arch-string-in-source-relation sh4eb
> +samba source: invalid-arch-string-in-source-relation m32r [build-depends: libacl1-dev (>= 2.2.11-1) [i386 ia64 alpha amd64 arm hppa m32r m68k mips mipsel powerpc ppc64 s390 s390x sh3 sh3eb sh4 sh4eb sparc]]
> +samba source: invalid-arch-string-in-source-relation s390x [build-depends: libacl1-dev (>= 2.2.11-1) [i386 ia64 alpha amd64 arm hppa m32r m68k mips mipsel powerpc ppc64 s390 s390x sh3 sh3eb sh4 sh4eb sparc]]
> +samba source: invalid-arch-string-in-source-relation sh3 [build-depends: libacl1-dev (>= 2.2.11-1) [i386 ia64 alpha amd64 arm hppa m32r m68k mips mipsel powerpc ppc64 s390 s390x sh3 sh3eb sh4 sh4eb sparc]]
> +samba source: invalid-arch-string-in-source-relation sh3eb [build-depends: libacl1-dev (>= 2.2.11-1) [i386 ia64 alpha amd64 arm hppa m32r m68k mips mipsel powerpc ppc64 s390 s390x sh3 sh3eb sh4 sh4eb sparc]]
> +samba source: invalid-arch-string-in-source-relation sh4 [build-depends: libacl1-dev (>= 2.2.11-1) [i386 ia64 alpha amd64 arm hppa m32r m68k mips mipsel powerpc ppc64 s390 s390x sh3 sh3eb sh4 sh4eb sparc]]
> +samba source: invalid-arch-string-in-source-relation sh4eb [build-depends: libacl1-dev (>= 2.2.11-1) [i386 ia64 alpha amd64 arm hppa m32r m68k mips mipsel powerpc ppc64 s390 s390x sh3 sh3eb sh4 sh4eb sparc]]

Wouldn't it be better to just get lintian fixed...?

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
vorlon at debian.org                                   http://www.debian.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-samba-maint/attachments/20060124/133a2c98/attachment.pgp