In what way is it "not functioning 100% as expected"? On Thursday, August 1, 2024 at 1:21:26 PM UTC-4 Veera wrote:
> > > Yes , We need a RSA format PEM key which is compatible with the > application . > Whenever a OPENSSH PRIVATE Key generated with the playbook is used for > authentication , login to the application is working but its not > functioning 100% as expected . > When a RSA format PEM or id_rsa key ( ssh-keygen -t rsa -b 2048) is used > then login and functioning of the application is working fine. (vendor > recommended RSA format SSH key) > > > > On Thursday, August 1, 2024 at 7:51:33 PM UTC+5:30 Felix Fontein wrote: > >> Hi, >> >> > However the public-key is showing the caption as ssh-rsa .. and the >> > private key is displaying the label as "-----BEGIN OPENSSH PRIVATE >> > KEY----- and -----END OPENSSH PRIVATE KEY-----" >> > >> > I am looking to create an rsa key-pairs with 2048b , something we >> > used to create with the command ssh-keygen -t rsa -b 2048 >> > The private key must begin with "-----BEGIN RSA PRIVATE KEY-----" and >> > ends with "-----END RSA PRIVATE KEY-----" >> >> Could you please elaborate why it **must** start with "-----BEGIN RSA >> PRIVATE KEY-----"? Does your SSH version not accept "-----BEGIN OPENSSH >> PRIVATE KEY-----"? >> >> In any case, I would suggest to look at the private_key_format option >> of the module. >> >> All the best, >> Felix >> >> -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/cb401600-0bf4-4c68-880c-e236af377d7dn%40googlegroups.com.
