Displaying 6 results from an estimated 6 matches for "id_rsa_vendor2".
2018 Dec 12
2
SFTP - Private/Public Authentication Keysets Beyond The First Set
...ve.
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. I
initiated the first connection with the second vendor and was asked for the
vendor-provided password which I entered and a successful connection was
ma...
2018 Dec 12
2
SFTP - Private/Public Authentication Keysets Beyond The First Set
...gt;
>
> 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. I
> initiated the first connection with the second vendor and was asked for
the
> vendor-provided password which I entered and a successful co...
2018 Dec 12
3
SFTP - Private/Public Authentication Keysets Beyond The First Set
...tion 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. I
>>> initiated the first connection with the second vendor and was asked for
>> the
>>> vendor-provided password wh...
2018 Dec 12
0
SFTP - Private/Public Authentication Keysets Beyond The First Set
...gt;
>
> 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. I
> initiated the first connection with the second vendor and was asked for the
> vendor-provided password which I entered and a successful co...
2018 Dec 12
0
SFTP - Private/Public Authentication Keysets Beyond The First Set
...hing 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. I
>> initiated the first connection with the second vendor and was asked for
> the
>> vendor-provided password which I entered an...
2018 Dec 12
0
SFTP - Private/Public Authentication Keysets Beyond The First Set
...tion 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. I
>>> initiated the first connection with the second vendor and was asked for
>> the
>>> vendor-provided password wh...