[Developers] Development plan for SSHKeychain

[TjL]

On 1/9/08, Eric Warnke <ericew at gmail.com> wrote:
>
> #2  I have launchd and a location for that.  Set up a "proxy/
> untrusted" location that proxies everything through socks5 localhost
> 3333.  I then dropped this into Library/LaunchAgents/proxy.plist
>
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd
> ">
> <plist version="1.0">
> <dict>
>          <key>Label</key>
>          <string>proxy.myserver</string>
>          <key>ProgramArguments</key>
>          <array>
>                  <string>/usr/bin/ssh</string>
>                  <string>-D</string>
>                  <string>3333</string>
>                  <string>-o</string>
>                  <string>ExitOnForwardFailure=yes</string>
>                  <string>-N</string>
>                  <string>user at myserver</string>
>          </array>
>          <key>RunAtLoad</key>
>          <false/>
> </dict>
> </plist>
>
>
> and so I switch to the location and run launchctl start proxy.myserver
> and I'm good to go.

Thanks... and I'm not meaning to be dense, I just.... well, that's
what I want SSHKeychain to do, to avoid me having to write my own
PLIST and worry about launchctl and a location.  Wouldn't it be easier
to have this all in the same app that controls my SSH keys already?

I realize there are other ways of doing this (and I appreciate these
examples and may use them myself) but in response to the question
"What's the future of this app now that Leopard has built part of it
in?" my answer is "Take tunneling out of the realm of people who
can/will do these things, and make it so simple that the average Mac
user can secure their laptop on public WiFi w/o having to do anything
but get into SSHKeychain.

That would be something.

TjL