Re: Portupgrade Ruby | warning: Insecure world
On Wednesday 05 April 2006 14:38, Jonas Jacobsen wrote: When i use portupgrade, i get this Warning all the time /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:980: warning: Insecure world writable dir /tmp, mode 041777 have any of you seen that warning before,? and do you know how to make it go away ? Not seen it but check the ouput of $ ls -ld /tmp (mode should be drwxrwxrwt) Maybe it is drwxrwxrwx, in which case # chmod o+t /tmp will fix it. Otherwise I'm not sure. Ashley ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Portupgrade Ruby | warning: Insecure world
have any of you seen that warning before,? and do you know how to make it go away ? Not seen it but check the ouput of $ ls -ld /tmp (mode should be drwxrwxrwt) Maybe it is drwxrwxrwx, in which case # chmod o+t /tmp will fix it. Otherwise I'm not sure. Using portmanager would make it go away, and save you a ton of time =) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade Ruby | warning: Insecure world
At 3:38 PM +0200 4/5/06, Jonas Jacobsen wrote: When i use portupgrade, i get this Warning all the time /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:980: warning: Insecure world writable dir /tmp, mode 041777 have any of you seen that warning before,? and do you know how to make it go away ? This comes from a recent security-minded change made to ruby. Your PATH references something in /tmp, and since other userids *could* change things in /tmp, this is warning that you might have a security problem. I think several ruby users have found this recent change is perhaps a bit over-zealous in it's warning. Which is to say, it is annoying. You could change your setting of PATH to avoid this. Perhaps the pkgtools.rb script could be changed to automatically change the PATH, but in this case it would have no idea *why* you reference some directory under /tmp in your PATH. So it's probably a bad idea for the script to change the value. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
