Knit 1, perl 5.6.0

[avram]

Not all is happiness and chowder in OSX land. My feet were set upon the path of troubles by ScriptGUI, a splendid little app that lets me run scripts (perl, shell) by double-clicking on them. This lets me keep a drawer full of scripts behind a pop-up tab at the edge of my monitor (pop-up tabs at the edges of one’s monitor are where all oft-used commands and icons belong). ScriptGUI is even willing to pop up a window to display STDOUT output and accept STDIN input, which is where the trouble comes in.

See, I’ve got a couple of scripts I use to move files between my home box and my server, using scp, the secure copy utility, which hides my sensitive password and other info behind a wall of encryption, safe from spying packet-sniffing cyber-noses. There are perl modules that’ll act as front ends for scp (and ssh, the related secure shell), but I’ve never successfully gotten any of them to work. Not much of a problem, though, since in the case of both my scripts, the scp transfer is the last thing that happens, so rather than bothering perl’s pretty little code about it, I just have the last statement in the perl script be an exec that calls scp with the relevant parameters. The perl script ends, invoking scp with its dying gasp, and the shell takes over, prompting me for my password. Works fine.

Not so fine with ScriptGUI, which isn’t willing to just fob things off on the shell. Time to rewrite the scripts to do things the formal way, interacting with ssh via the modules and asking for my password via STDOUT and STDIN. Off to CPAN to download the modules. Net::SSH::Perl has a lot of dependencies — other modules which need to be installed before it. OK, no prob, CPAN has those, too. Uh oh, they’ve got dependencies too, and one of them just won’t install, it can’t find gmp.h, which is the header file for, um, a GNU math library of some kind, I think. Crap. At least there seems to be a stable version in Fink, but geez, I don’t even have Fink installed, and I seem to have used up my gumption for the day. Time to just sit down and read comics.

Comments

[mneme]

I was going to suggest this too, since it's just -so- much more conventient not to have to enter your password every time (especially since I use SSH for cvs checkins).

What I've found re problems is that they're usually caused by one of two things:

1. The permissions on .ssh or ..ssh/authorized_keys on the -SERVER- are set
   too permissively, and SSH refuses to honor them. Solution : make .ssh and below have permissions of 700 or more restrictive.
   
2. You are using one type of key (RSA1 or DSA), and the server doesn't recognize that type for one reason or another. Solution: create a different type of key, and use that.