Why does Samba requires 777 permissions on /tmp

[sindrome]

You can see the sticky bit is indeed set and I'm still getting these errors:

stat -r /tmp
90 7418880 041777 3 0 0 29641368 512 1368950908 1369024120 1369024120
1130953852 16384 4 0 /tmp


/usr/local/lib/ruby/site_ruby/1.8/pkgtools/pkgtools.rb:483: warning:
Insecure world writable dir /tmp/. in PATH, mode 041777
/usr/local/lib/ruby/site_ruby/1.8/pkgtools/pkgtools.rb:1170: warning:
Insecure world writable dir /tmp/. in PATH, mode 041777
/usr/local/lib/ruby/site_ruby/1.8/pkgtools/pkgmisc.rb:108: warning:
Insecure world writable dir /tmp/. in PATH, mode 041777
/usr/local/lib/ruby/site_ruby/1.8/pkgtools/pkgtools.rb:483: warning:
Insecure world writable dir /tmp/. in PATH, mode 041777


On Sun, May 19, 2013 at 4:22 PM, Bob Eager <rde at tavi.co.uk> wrote:

> On Sun, 19 May 2013 15:59:12 -0500
> Jimmy <ljboiler at gmail.com> wrote:
>
> > From the original post that started this thread, I noticed that the
> > error from portupgrade/ruby was showing the permissions that it didn't
> > like as mode 040777 (octal).   This is definitely with the sticky bit
> > turned OFF. It should be 041777.  'stat -r /tmp' will print the
> > permissions in octal rather than the '..rwx...' from ls -l; the
> > permissions is the third group of numbers.
>
> Well, that's true. And it is a security risk not to have the sticky bit
> on /tmp.
>
> Of course (for the avoidance of confusion) the 040000 bit can't be
> changed, being the 'directory' bit.
> _______________________________________________
> freebsd-ports at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
>