search for: rsa_vendor2

...server. During successive connections I was not again asked for the password. This allowed me to create fully automated batch file transfers.my objective. Setting up my second vendor is not going as smoothly. I did exactly the same thing for my second vendor with the exception of typing "rsa_vendor2" during keyset generation (I assumed I had to use a different name for the new keyset). # ssh-keygen -t rsa_vendor2 Files "id_rsa_vendor2" and "id_rsa_vendor2.pub" were created in "/root/.ssh/" and I gave "id_rsa_vendor2.pub" to the second vendor...

...ctions I was not again asked for the password. This > allowed me to create fully automated batch file transfers.my objective. > Setting up my second vendor is not going as smoothly. > > > > I did exactly the same thing for my second vendor with the exception of > typing "rsa_vendor2" during keyset generation (I assumed I had to use a > different name for the new keyset). > > > > # ssh-keygen -t rsa_vendor2 > > > > Files "id_rsa_vendor2" and "id_rsa_vendor2.pub" were created in > "/root/.ssh/" and I gave &quot...

...>> allowed me to create fully automated batch file transfers.my objective. >>> Setting up my second vendor is not going as smoothly. >>> >>> >>> >>> I did exactly the same thing for my second vendor with the exception of >>> typing "rsa_vendor2" during keyset generation (I assumed I had to use a >>> different name for the new keyset). >>> >>> >>> >>> # ssh-keygen -t rsa_vendor2 >>> >>> >>> >>> Files "id_rsa_vendor2" and "id_rsa_vendor2...

...tions I was not again asked for the password. This > allowed me to create fully automated batch file transfers.my objective. > Setting up my second vendor is not going as smoothly. > > > > I did exactly the same thing for my second vendor with the exception of > typing "rsa_vendor2" during keyset generation (I assumed I had to use a > different name for the new keyset). > > > > # ssh-keygen -t rsa_vendor2 > > > > Files "id_rsa_vendor2" and "id_rsa_vendor2.pub" were created in > "/root/.ssh/" and I gave &quot...

...the password. > This >> allowed me to create fully automated batch file transfers.my objective. >> Setting up my second vendor is not going as smoothly. >> >> >> >> I did exactly the same thing for my second vendor with the exception of >> typing "rsa_vendor2" during keyset generation (I assumed I had to use a >> different name for the new keyset). >> >> >> >> # ssh-keygen -t rsa_vendor2 >> >> >> >> Files "id_rsa_vendor2" and "id_rsa_vendor2.pub" were created in >>...

...>> allowed me to create fully automated batch file transfers.my objective. >>> Setting up my second vendor is not going as smoothly. >>> >>> >>> >>> I did exactly the same thing for my second vendor with the exception of >>> typing "rsa_vendor2" during keyset generation (I assumed I had to use a >>> different name for the new keyset). >>> >>> >>> >>> # ssh-keygen -t rsa_vendor2 >>> >>> >>> >>> Files "id_rsa_vendor2" and "id_rsa_vendor2...

...first.site.com User remoteuserid IdentityFile /home/myuser/.ssh/id_rsa # sftp otheruserid at second.other.com == Host site2 HostName second.other.com User otheruserid IdentityFile /home/myuser/.ssh/rsa_vendor2 #EOF Then just run 'sftp site1' or 'sftp site2' to connect as required. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrne mailto:Byr...