On Fri, May 13, 2011 at 10:27:45PM +0100, Tyler J. Wagner wrote:
> On Fri, 2011-05-13 at 16:54 -0400, Neal Becker wrote:
> > I had tried ssh -v from backuppc on server to root on client. It
> > showed trying
> > rsa and dsa keys (I use dsa), then falling back to asking for password.
>
> Did it l
On Fri, 2011-05-13 at 16:54 -0400, Neal Becker wrote:
> I had tried ssh -v from backuppc on server to root on client. It showed
> trying
> rsa and dsa keys (I use dsa), then falling back to asking for password.
Did it list which keys it tried? It should identify the filename it is
trying. Are y
Richard Shaw wrote:
> On Fri, May 13, 2011 at 2:18 PM, Neal Becker wrote:
>> Tried to setup as before so backuppc user on server can ssh as root on
>> client. No luck. If I test, public key doesn't work.
>
> You probably did things this way but you didn't specify so I'm just checking.
>
> When
On 5/13/2011 2:18 PM, Neal Becker wrote:
> Tried to setup as before so backuppc user on server can ssh as root on client.
> No luck. If I test, public key doesn't work.
>
> Yes, on client .ssh permissions are OK, and there are no log messages saying
> otherwise.
Add -vv to the ssh command line fo
On Fri, May 13, 2011 at 2:18 PM, Neal Becker wrote:
> Tried to setup as before so backuppc user on server can ssh as root on client.
> No luck. If I test, public key doesn't work.
You probably did things this way but you didn't specify so I'm just checking.
When I'm setting up a client I don't
Tried to setup as before so backuppc user on server can ssh as root on client.
No luck. If I test, public key doesn't work.
Yes, on client .ssh permissions are OK, and there are no log messages saying
otherwise.
I did see some selinux warnings, but selinux is set to permissive - so that
thes
