amrecover using invalid ssh options on Solaris?

My amanda 2.5.1p3 installation on Solaris 9 has been doing backupssmoothly for several weeks using ssh authentication.

I can also do amrecover on the backup server, where I have sizeablespool capacity, and then move files from there across the network using scp.

However, in trying to configure ssh authentication and use amrecover onthe clients, I get:

pilot:/var/tmp# /usr/local/sbin/amrecovercommand-line: line 0: Bad configuration option: PreferredAuthentications

   AMRECOVER Version 2.5.1p3. Contacting server on mormyrid.bio.mor.nsm ...
   [request failed: error sending REQ: write error to : Broken pipe]

A google search indicates that the first error line is an error fromssh. The man pages on Solaris 9 ssh have no indication of an option"PreferredAuthentications". Just for comparison, I ducked into anOpenBSD machine that I have and did a man page on ssh. There is has thisoption. It is OpenSSH_3.9 with OpenSSL 0.9.7d. If I ask for the versionon Solaris 9 (which is based on OpenSSH), I get SSH VersionSun_SSH_1.0.1, protocol versions 1.5/2.0.

So, it seems that amrecover is opening a connection with SSH and thentrying to contact the amanda server on that connection and getting abroken pipe error because the SSH connection attempt failed.

I have followed the instructions fromhttp://wiki.zmanda.com/index.php/Configuring_SSH_authentication, and Ihave set up the amanda_client.conf on the client with the lines:


   conf "daily"            # your config name

   index_server "mormyrid.bio.mor.nsm"     # your amindexd server
   tape_server  "mormyrid.bio.mor.nsm"     # your amidxtaped server
   tapedev      "LIB-162A5"                # your tape device

# auth - authentication scheme to use between server andclient.

   #                 Valid values are "bsd", "krb4", "krb5" and "ssh".
   #                 Default: [auth "bsd"]
   auth "ssh"

ssh_keys "/.ssh/id_rsa_amrecover" # your sshkeys file if you use ssh auth

So, is this an amanda bug? Is there a workaround or patch? Or have Idone something wrong in my setup? If so, what should I be looking for? Idon't want to have to run around to all my Solaris 9 servers and installand configure OpenSSH. Not only would it be a lot of work, but it wouldcomplicate my configurations. Sun SSH is working just fine in all otherrespects. Switching to OpenSSH would have a cascade effect. Sun builttcp-wrappers into their system configuration, as well as various othersecurity items, and if I installed OpenSSH, I would also have to installtcp-wrappers and replicate all the security work on all of my servers.


TIA


---------------

Chris Hoogendyk

-
  O__  ---- Systems Administrator
 c/ /'_ --- Biology & Geology Departments
(*) \(*) -- 140 Morrill Science Center

~~~~~~~~~~ - University of Massachusetts, Amherst

<hoogendyk AT bio.umass DOT edu>

---------------

Erdös 4