In WindowsXP where does the key file go?

Report your issues here

Re: In WindowsXP where does the key file go?

Postby raf » Sat Jun 18, 2011 9:10 pm

Hi!,
Your public key goes in the "authorized_keys" file for your user/system in your server.
The specific location depends on the SSH server you're using. For Unix (Linux, Mac, BSD), it goes under .ssh:
/home/YourUser/.ssh/authorized_keys
or
/Users/YourUser/.ssh/authorized_keys

Raf.
raf
Site Admin
 
Posts: 1691
Joined: Sat Oct 09, 2010 12:17 am

Re: In WindowsXP where does the key file go?

Postby raf » Sat Jun 18, 2011 10:42 pm

Some people have had luck with freeSSHd for Windows.
For Windows and OpenSSH, I found this info online:

http://www.experts-exchange.com/Softwar ... 25359.html

It doesn't *have* to be called that - if you go to the sshd_config file and add a line "AuthorizedKeysFile <file path>" into it, and then that becomes the "new" location for the file. this is by default relative to the user's home dir (so .ssh/authorized_keys would be the default value) but if you start it with a / you can make it an absolute path (so /etc/sshkeys/%u would look for a file with the same name as the user in a subdirectory of /etc called sshkeys)

it will then fall back to $HOME/.ssh/authorized_keys though, unless you *also* set AuthorizedKeysFile2 - its an undocumented (well poorly documented, given I know it :) failback for openssh. or you could just remove the dot, so your subdir is called ssh rather than ssh (which is noticably more windows-friendly)


Hope that helps.

Raf.
raf
Site Admin
 
Posts: 1691
Joined: Sat Oct 09, 2010 12:17 am

Re: In WindowsXP where does the key file go?

Postby raf » Tue Sep 06, 2011 12:02 pm

I'm not sure about OpenSSH in windows, and how the public keys are added to the authorized_keys file. In Mac/Linux, this file resides under the user directory / .ssh (hidden directory). Maybe in Windows it's under /Users/username/.ssh?

Regarding your problem with UVNC 1.0.9.6.1, have you tried reverting back to 1.0.9.6?


Last time, getting this far with XP, it was saying "wrong credentials", now it's a time-out with Win7 Pro

Make sure OpenSSH is running, and that either you don't have a firewall running in win7, or if you do, that port 22 is open.

Also, are these two programs 64-bit? Does it matter if they're not, on a 64-bit OS?

Which programs? OpenSSH?
I'm not sure how it works in Windows anymore, I was under the impression that if the os is 64bit, the apps have to be 64bit? (On the Mac, the OS and app can be 32/64 and it all works, and I know this is different than Windows).

Raf.
raf
Site Admin
 
Posts: 1691
Joined: Sat Oct 09, 2010 12:17 am

Re: In WindowsXP where does the key file go?

Postby raf » Wed Sep 07, 2011 11:39 am

With windows, some paths look for the "\" instead, so a valid path would look like ...
C:\program Files\OpenSSH\etc\
Could this have anything to do with it not seeing the Authorized_Keys file, using the config file as it's written now?
[/quote]
Yes, of course, replace with the appropriate path, and with the backslash. Remoter has nothing to do with this, this controlled by your system

What about the other settings, not making a path, but instead, a "yes/no" settings?
Are there others needed to be changed for windows based usage?

Maybe a user with experience setting up SSH on windows can help here. But if you post the configuration file I might be able to guide you.

I know the AMD Turion X2 dual-core CPU supports Virtualization, so, I was getting one to replace this single core CPU anyway, (TMDTL68HAX5DM) so maybe it will help the speed and workings of the 64bit OS.

My understanding of CPU support for virtualization is that it's for use by applications such as VMWare / VirtualBox (to run virtual machines), not for 64/32bit processing. But I do know that the AMD CPUs use the x86-64 instruction set, which supports both 32 and 64bit apps. But then it's up to the OS to do the right thing.

Raf.
raf
Site Admin
 
Posts: 1691
Joined: Sat Oct 09, 2010 12:17 am


Return to Support

Who is online

Users browsing this forum: Bing [Bot] and 15 guests

cron
cron