× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



On Win7, I created a file c:\users\user_name_here\.ssh\authorized_keys, but it did not do anything. RDi still gives the same SSH error and ACS "SSH Terminal" still prompts me for my password.

Thanks




-----Original Message-----
From: Patrik Schindler [mailto:poc@xxxxxxxxxx]
Sent: Monday, May 04, 2020 10:46 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: SSH key setup

Hello Justin,

Am 04.05.2020 um 16:58 schrieb Justin Taylor <JUSTIN@xxxxxxxxxxxxx>:
Step 7 says to put the public key "into the appropriate location on the remote side". How do I know where that is? If it matters, the clients will be Windows 7 and Ubuntu 16, both running RDi and SSH.

Normally this goes to ~/.ssh/authorized_keys. (Tilde = Home of the current user, aka, the one which will connect to the machine.)

Public Keys are always just one long line of printable characters and in authorized_keys can be multiple lines to allow multiple peers to connect.

:wq! PoC

PGP-Key: DDD3 4ABF 6413 38DE - https://www.pocnet.net/poc-key.asc




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.