[...]
This doesn't really make sense. Are you sure that you didn't connect
by hand in pather once, and answer the query about whether you would
accept the certificate or not? Once the certificate was accepted,
perl in Panther might have been accessing the user's .ssh?
I reboot the machines and map the disk image to the drive every time.
In Panther, the disk image doesn't have .ssh.
Hmm. So maybe the ssh libraries on Panther and Tiger default to
different behavior when the user's settings are missing?
I do set up an account and password in the disk image. I use password
authorization
to access Panther.
Meaning, the script takes the password (passphrase?) query and answers
it?
But I could not do the same with Tiger. The perl script always ask me
to type in password
by hand.
Is it possibly sending the query on STDERR instead of STDOUT? I think
perl would allow you to redirect STDERR, if that's the case.
But my goal is automation. To avoid this, I have to put a public key
to the target machine and use identity key authorization to access it.
Yeah, keys certificates can be a pain to deal with in their current
form. Would a self-certificate help? Openssl can do self-certificates
as well as keys. (Maybe you've already tried that?)
[...]
Eventually, this kind of thing will get straightened out a bit. But
we who write programs still need to be aware of when we need to
identify and when we need to encrypt and when we can just spit data.
(If we don't, who will?)
The problem is I know I just need to spit data, but I couldn't.
Well, you are the best person to know whether the project wil live long
enough to escape its cage, etc.
I'd suggest compiling and installing rsh or some such, but I really
shouldn't. I think installing keys for ssh will work out simpler in the
end.
--
Joel Rees
If Microsoft is effectively taxing the internet,
should we call it a sin tax?
