Re: SOLVED: Keychain use on Mac OS 10.5

On Wed, 12 Mar 2008, Claus Atzenbeck wrote:

>> I don't quite understand the underlying 'magic' that screen uses.  But
>> this sounds like screen does something (like run under another user?)
>> that makes any app unable to talk to the keychain because it can't
>> "connect to the window server".  I don't exactly know how that works too,
>> but it essentially requires the user to really be there live, not ssh-ed in
>> for example.
>
> As I mentioned, Fink's screen distribution works, even though it is the exact 
> version of screen that Apple ships with Leopard. Apple's screen on Tiger also 
> did not have that problem. (I don't know the difference of Leopard's and 
> Tiger's screen.)

As a final close-up and reference for others who might come across this 
problem later, here is the most likely reason that caused my problem. 
(Sorry for being off-topic. This will be the last time.)

I found out that Matt's guess was correct:

$ ls -la /sw/bin/screen*
lrwxr-xr-x 1 root admin     12 2008-03-12 21:27 /sw/bin/screen -> screen-4.0.3*
-rwsr-xr-x 1 root admin 377952 2008-03-12 21:27 /sw/bin/screen-4.0.3*
$ ls -la /usr/bin/screen
-rwxr-xr-x 1 root wheel 601296 2007-09-24 04:11 /usr/bin/screen*

As you can see, Fink's screen has a sticky bit turned on which makes one 
of the screen instances run as root, the other as user. This seems to 
cause the problem of Alpine not being able to connect to the keychain 
when running inside /usr/bin/screen.

Cheers,
/CA
_______________________________________________
Pine-info mailing list
[email protected]
http://mailman1.u.washington.edu/mailman/listinfo/pine-info