I'm hoping this is not related to the 20040802 wxPython installer, but it needs to be checked out. I walked a friend through installing the latest daily build this morning on a Panther box that didn't have any previous copies of wxPython installed. Prior to doing the install I asked him whether he had a ~/.MacOSX dir or environment.plist in that dir because I wanted to setup a PYTHONPATH environment variable once we had wxPython and PythonCard installed. The answer was "no", they didn't exist. So he did the wxPython install and we were going to create the dir and environment.plist and he said that now there was a file in there with the following key/value pair.
I don't know how the Mac handles authorizing SSL connections but that's what that pair looks like. Maybe this is something on Robin or Kevin O.'s box and just snuck into the file list for the builder/installer? There wasn't anything in the Console about this file either. My friend said that he doesn't have a ~/tmp dir so there are no other folders/files. On my box, I already have an environment.plist file and it wasn't touched by the latest installer.
I'm hoping this is not related to the 20040802 wxPython installer, but it needs to be checked out. I walked a friend through installing the latest daily build this morning on a Panther box that didn't have any previous copies of wxPython installed. Prior to doing the install I asked him whether he had a ~/.MacOSX dir or environment.plist in that dir because I wanted to setup a PYTHONPATH environment variable once we had wxPython and PythonCard installed. The answer was "no", they didn't exist. So he did the wxPython install and we were going to create the dir and environment.plist and he said that now there was a file in there with the following key/value pair.
I don't know how the Mac handles authorizing SSL connections but that's what that pair looks like.
Actually it's SSH, and it looks like that environment var is used by ssh and ssh-agent as the socket address to provide the passphrase to ssh when it needs it.
Maybe this is something on Robin or Kevin O.'s box and just snuck into the file list for the builder/installer? There wasn't anything in the Console about this file either.
As far as I know the Installer doesn't do anything with SSH, unless the "unlock" authentication dialog does something with it... The build script doesn't put an environment.plist file into the build root so there is no way it can end up in the disk image (check the Installer's "Show Files" list to be sure) unless it is a by-product of the install.
Probably more likely is that your friend initiated an ssh connection somewhere and the ssh-agent asked him for his passphrase...
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
Sorry for the red herring. We're going to assume operator error on the part of my friend. He does keep multiple terminals open and some of those are open to remote machines so when he did the initial check for the environment.plist he was probably looking at the wrong box. Doing a Google search on the SSH (ssl was obviously a typo on my part below) I came up with
The friend says he tried using SSH Agent a long time ago and I'm guessing that is where the environment.plist came from so all is well.
ka
···
On Aug 4, 2004, at 2:33 PM, Robin Dunn wrote:
Kevin Altis wrote:
I'm hoping this is not related to the 20040802 wxPython installer, but it needs to be checked out. I walked a friend through installing the latest daily build this morning on a Panther box that didn't have any previous copies of wxPython installed. Prior to doing the install I asked him whether he had a ~/.MacOSX dir or environment.plist in that dir because I wanted to setup a PYTHONPATH environment variable once we had wxPython and PythonCard installed. The answer was "no", they didn't exist. So he did the wxPython install and we were going to create the dir and environment.plist and he said that now there was a file in there with the following key/value pair.
<dict>
<key>SSH_AUTH_SOCK</key>
<string>/tmp/501/nl.uu.phil.SSHAgent.socket</string>
</dict>
I don't know how the Mac handles authorizing SSL connections but that's what that pair looks like.
Actually it's SSH, and it looks like that environment var is used by ssh and ssh-agent as the socket address to provide the passphrase to ssh when it needs it.
Maybe this is something on Robin or Kevin O.'s box and just snuck into the file list for the builder/installer? There wasn't anything in the Console about this file either.
As far as I know the Installer doesn't do anything with SSH, unless the "unlock" authentication dialog does something with it... The build script doesn't put an environment.plist file into the build root so there is no way it can end up in the disk image (check the Installer's "Show Files" list to be sure) unless it is a by-product of the install.
Probably more likely is that your friend initiated an ssh connection somewhere and the ssh-agent asked him for his passphrase...
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!