Permissions errors on conf file

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Opening tunnelblick, editing the conf file
2. running the conf file 

What is the expected output? What do you see instead?
Tunnelblick reports to the console:
15/10/2009 Oct 15 | 22:33:55    Tunnelblick[84625]  Unlocking alternate 
configuration file 
/Library/Tunnelblick/Ewan/openvpn.conf failed in 5 attempts
15/10/2009 Oct 15 | 22:33:55    Tunnelblick[84625]  Configuration file 
/Library/Tunnelblick/Ewan/openvpn.conf has permissions: 0644, is owned by 501 
and needs 
repair...

What version of Tunnelblick are you using? On what version of OS X? PPC or 
Intel?
TunnelBlick 3b20 build 1206 / OS X Snow Leopard 10.6.1 / Intel

Please provide any additional information below.
attempted to change permissions to root, no luck. This also does it with a 
tunnelblick created 
conf file.

I have enabled shadow file copy, to no avail

Original issue reported on code.google.com by echami...@gmail.com on 15 Oct 2009 at 9:41

[GoogleCodeExporter]

Is your home folder on something other than your computer's main hard drive? If 
not, make sure shadow 
copying is DISabled by deleting that preference item.

Is the configuration file (in ~/Library/openvpn) locked? If so, unlock it and 
try again.

Are you logged in as a computer administrator? If not, try logging in as a 
computer administrator. Let us 
know if that fixes the problem -- it shouldn't be necessary but maybe there's a 
bug.

If neither of those works, try moving the openvpn folder out of ~/Library (to 
the Desktop, for example) and let 
Tunnelblick recreate the folder and a sample openvpn.conf file, then replace 
the contents of the folder with 
the contents of the folder on your Desktop. (Don't just copy the folder itself 
to ~/Library, copy all the items in 
the folder into the new ~/Library/openvpn folder.)

In any case, please post your results.

Original comment by jkbull...@gmail.com on 16 Oct 2009 at 3:15

[GoogleCodeExporter]

On further reflection, Tunnelblick clearly thinks the file is locked, and is 
failing to unlock it.

If the file IS locked, then this is probably a bug in Tunnelblick's method of 
unlocking of a locked file; probably 
what worked in Leopard doesn't work in Snow Leopard. You can get around this by 
unlocking the file yourself.

If the file ISN'T locked, this is probably a bug in Tunnelblick's detection of 
a locked file; probably what worked 
in Leopard doesn't work in Snow Leopard. You probably can't get around this.

Unfortunately, a fix from me will have to wait until sometime next week as I am 
away from my development 
computer until then.

Original comment by jkbull...@gmail.com on 16 Oct 2009 at 3:46

[GoogleCodeExporter]

Tunnelblick should not change the status of a locked configuration file. r286 
warns the user if the configuration 
file is locked. It is then up to the user to unlock it.

The case of creating shadow configuration files is different. In that case, 
Tunnelblick will silently copy the file. 
(Copying locked files is permissible and appropriate in this case because it 
does not involve changing the locked 
file.

Original comment by jkbull...@gmail.com on 17 Nov 2009 at 9:45

• Changed state: Fixed