Well, actually it is straight forward. Just create a ssh_authorized_keys resource for an user for both nodes and store the private key in .ssh/id_rsa or define Identity key file in .ssh/config.
On Sat, Aug 3, 2013 at 7:12 AM, Mark Ruys <[email protected]> wrote: > With the risc I ask a queston answered a hunderd times before (which I > couldn't find)... > > On node A I want to create a ssh key. For this I exec a ssh-keygen. Now I > want the generated public key added to the authorized key file of node B. > Probably I need the ssh_authorized_key resource for this. But then I need > the public key of node A as a string in node B. I can't see how to achieve > this with exported resources. So my guess is that I need to write a custom > fact to read ~/.ssh/id_rsa.pub on node A in order to collect it on node B. > > Is this the way I should go? Or is there a better approach? > > Thanks, Mark > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/puppet-users. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
