... but has the annoying nag message:
`/Applications/TextMate.app/Contents/SharedSupport/Support/lib/tm/process.rb :194: warning: Insecure world writable dir /usr/local in PATH, mode 040777`
every time you run a script been fixed in TextMate 2 (can't upgrade at the moment, too busy)?
Cheers,
Phil...
On 17 Dec 2011, at 19:24, Phil Dobbin wrote:
... but has the annoying nag message:
`/Applications/TextMate.app/Contents/SharedSupport/Support/lib/tm/process.rb :194: warning: Insecure world writable dir /usr/local in PATH, mode 040777`
every time you run a script been fixed in TextMate 2
The warning is from ruby and not TextMate.
You can “fix” it by not making the /usr/local folder group/world writable. If you google the error code you’ll see lots about it.
On 18/12/11 01:07, "Allan Odgaard" mailinglist@textmate.org wrote:
On 17 Dec 2011, at 19:24, Phil Dobbin wrote:
... but has the annoying nag message:
`/Applications/TextMate.app/Contents/SharedSupport/Support/lib/tm/process.rb :194: warning: Insecure world writable dir /usr/local in PATH, mode 040777`
every time you run a script been fixed in TextMate 2
The warning is from ruby and not TextMate.
You can ³fix² it by not making the /usr/local folder group/world writable. If you google the error code you¹ll see lots about it.
Hi.
Yes, I've read all the stuff on Google & figured that TextMate uses Ruby to a great extent (hence the .rb extension) & that's why the same scripts when run in other editors do not show the same warning.
The /tmp & /cache folders have to be world writable in apache2 otherwise PHP frameworks throw errors & won't display correctly.
It's just a minor annoyance.
Thanks,
Cheers,
Phil...
On 18 Dec 2011, at 02:45, Phil Dobbin wrote:
Yes, I've read all the stuff on Google & figured that TextMate uses Ruby to a great extent (hence the .rb extension) & that's why the same scripts when run in other editors do not show the same warning.
The warning is from ruby, TextMate itself is not tied to ruby — other things using the (same) ruby interpreter will show the same warnings.
The /tmp & /cache folders have to be world writable in apache2 otherwise PHP frameworks throw errors & won't display correctly.
Ruby is complaining about /usr/local, not the folders you mention.
On 18/12/11 01:50, "Allan Odgaard" mailinglist@textmate.org wrote:
[...]
The /tmp & /cache folders have to be world writable in apache2 otherwise PHP frameworks throw errors & won't display correctly.
Ruby is complaining about /usr/local, not the folders you mention.
Those folders are in /usr/local. They're the only ones in that directory that are world-writable (the same applies to /opt/local).
Or are you saying that Ruby is complaining about /usr/local regardless?
Cheers,
Phil...
On 18 Dec 2011, at 09:06, Phil Dobbin wrote:
Ruby is complaining about /usr/local, not the folders you mention.
[…] are you saying that Ruby is complaining about /usr/local regardless?
This is the error you quoted: “Insecure world writable dir /usr/local in PATH”.
What this means is:
1. The folder ‘/usr/local’ is “world writable”. This means that any user on your system (incl. guest) can write to that folder. 2. The folder ‘/usr/local’ is in your PATH. This means that when you e.g. type ‘ls’ in a terminal, the system will look for ‘ls’ in ‘/usr/local’. 3. This is insecure because say I get access to your machine (e.g. guest accont login) I can put a script called ‘ls’ which will then be called (later) by a more trusted user, and so I can bootstrap the attack from a simple guest-login to root.
To fix this you do one of the following:
- Run this line in terminal: sudo chmod go-w /usr/local - Remove ‘/usr/local’ from your PATH.
I hope this clears up your confusion.
On 18/12/11 09:44, "Allan Odgaard" mailinglist@textmate.org wrote:
[...]
I hope this clears up your confusion.
Absolutely. Thanks for your time.
Cheers,
Phil...
-
Allan Odgaard -
Phil Dobbin