You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@hbase.apache.org by "Hiller, Dean (Contractor)" <de...@broadridge.com> on 2011/01/01 00:58:03 UTC

RE: ssh passwordless login "without" public key authentication

Sweet, thanks!
Dean

-----Original Message-----
From: Lalit Kapoor [mailto:lalitkapoor@gmail.com] 
Sent: Friday, December 31, 2010 3:33 PM
To: user@hbase.apache.org
Subject: Re: ssh passwordless login "without" public key authentication

If im not mistaken you can set stricthostkeychecking to no to avoid that
prompt.

--
Lalit Kapoor Via Phone


On Dec 31, 2010, at 4:26 PM, "Hiller, Dean  (Contractor)"
<de...@broadridge.com> wrote:

> Every time we add a blade, getting passwordless login setup seems to
be
> a pain as the master has to be modified to "know" about the node so we
> don't get prompted with do you know this key DF:ER:5R:etc. etc. and
> typically this is done quickly by doing ssh <user>@<newnode> and just
> answering yes  (assuming the .ssh directory is just coming from a
> standard image).
> 
> 
> 
> Word has it there is a way to do automatic login so as we add blades,
> our goal is really just to discover that(some systems are starting to
> have that like cisco UCS) and then automatically add that to the
slaves
> file.  
> 
> 
> 
> Does anyone know how to do passwordless ssh without publich key
> authentication OR at the very least tell the master to "trust" all
nodes
> out there so it never prompts for the do you want to trust the key
> question?
> 
> 
> 
> The authenticity of host 'dhiller ()' can't be established.
> 
> RSA key fingerprint is
94:95:c6:70:9c:ce:48:ca:db:6f:ff:ab:95:47:01:11.
> 
> Are you sure you want to continue connecting (yes/no)?
> 
> 
> 
> Thanks,
> 
> Dean
> 
> 
> This message and any attachments are intended only for the use of the
addressee and
> may contain information that is privileged and confidential. If the
reader of the 
> message is not the intended recipient or an authorized representative
of the
> intended recipient, you are hereby notified that any dissemination of
this
> communication is strictly prohibited. If you have received this
communication in
> error, please notify us immediately by e-mail and delete the message
and any
> attachments from your system.
> 
This message and any attachments are intended only for the use of the addressee and
may contain information that is privileged and confidential. If the reader of the 
message is not the intended recipient or an authorized representative of the
intended recipient, you are hereby notified that any dissemination of this
communication is strictly prohibited. If you have received this communication in
error, please notify us immediately by e-mail and delete the message and any
attachments from your system.