I have a wrapper script which I wrote to work around hanging TTY issues when starting tomcat over SSH, but upong upgrading my system, it seems to have horribly broken key authentication. Here's the relevant snippet of perl code:

    my %SSH_Prm = (
            "protocol"         => '2',
            "use_pty"          => 0,
            "options"          => ["stricthostkeychecking no"],
            "identity_files"   => ["/home/user/.ssh/id_rsa"],
            "debug"            => 1,
        );
    my $ssh = Net::SSH::Perl->new($server,%SSH_Prm);
    $ssh->login("deploy");
    my ($out,$err,$exit) = $ssh->cmd("/usr/bin/sudo $command");
[download]

The debug was added to get more detailed diagnostic data, which now shows:

server.domain.net: Authentication methods that can continue: publickey
+.
server.domain.net: Next method to try is publickey.
server.domain.net: Trying pubkey authentication with key file '/home/u
+ser/.ssh/id_rsa'
server.domain.net: Authentication methods that can continue: publickey
+.
server.domain.net: Next method to try is publickey.
Permission denied at ./start_tomcat_remote line 88
[download]

Now if I test this ssh key authentication using OpenSSH, it works without issue:

ssh -vv -i /home/user/.ssh/id_rsa deploy@server.domain.net
...
debug1: Offering public key: /home/user/.ssh/id_rsa
debug2: we sent a publickey packet, wait for reply
debug1: Server accepts key: pkalg ssh-rsa blen 277
[download]

Now to my eye, this is a very straightforward perl module failure, but I'm not getting enough information to figure out how to fix it. I've read through other perlmonks issues with Net::SSH::Perl and have found issues with password auth, but nothing else using pre-determined keys. Any idea what I might do next to resolve this?