Quote:

---

Hi all!

With regard to 'Access denied' problem, I've found this: when you install freeSSHd as a Windows Service, with 'manual' startup (so that you have to start the service manually), and then you start freeSSHd console from start men�, you're able to start/stop server from console (you can see the green/red icon, and with netstat -a you see that port 22 is in use), but if you try to connect, you get the 'Access denied' message (and if you see from services list inside of control panel of windows, you see the the freeSSHd service is always stopped). Instead, if you start freeSSHd service from Control Panel ->...->Services, you get in the tray area the icon of freeSSHd console, as usual (and you can start to administer srver with the console; and, of course, with netstat -a you can see that port 22 is in use, again), and if you try to connect, everything goes fine! BUT: if you stop and then restart service from inside the console, you get the 'Access denied' error again; if you stop and restart service from Windows services, eveything goes fine.

Conclusion: if you install freeSSHd as a windows service, you cannot use freeSSHd console for starting/stopping server, you have to use Windows Services.

Hope this can help!

Bye!

---

Ok, after struggling with this (and reading through this thread quite a bit) I've found the exact process is that the public key files you create for freesshd have to contain the EXACT public key text that you see in the Puttygen window in order to authenticate properly.

Quote:

---

Ok, after struggling with this (and reading through this thread quite a bit) I've found the exact process is that the public key files you create for freesshd have to contain the EXACT public key text that you see in the Puttygen window in order to authenticate properly.

---

This is what second post in this topic says:

Quote:

---

Step 3
Generate keys using PuTTYgen. Save your private key wherever you want, but somewhere safe, of course. Now, use a text editor (Notepad will do) to create a file in your public key folder. Copy the OpenSSH public key from PuTTYgen screen and paste it into this new file. Save it with a name same as your login.

---

Hi, I know that my question is out of field this forum, but I dont know where ask for it. My problem is access to stored public key. I have 2 PC. 1. PC -> FreeSSHd(authentication by keys). 2.PC-> Putty. I start putty -> write IP -> open. Appears dialog box with message: ... store public key SSH server? I click YES. But I dont know where is stored the key?? I find out that it is in registry. Sometimes I need delete this key, but I cant find it in registry. Do you have a idea how solve it?
Thanks

Hi

I cannot get this to work because my computer does not know what $HOME is. What is this. Is this initilzied by %USERPROFILE% environment variable?

Public key cannot be found because of this problem.

I am on windows xp pro.

What is the solution. I do not want to hardcode the public key path as then this will not work for multiple users.

Hi,
@none:
$HOME is a global variable of XP which is initiated by logon of an user. Though the only possibility why the system doesn't know it, is if no user is logged on.

Why do think your system doesn't know $HOME?


@mono:
Why do you need to delete the key?

Andrwe

Quick Question. I have freeSSHd v1.2.1 installed on Server 2008. Working great. I just received a public key (id_dsa.pub) and need to import it so they can connect using their Public Key they sent me.

All I recieved was id_dsa.pub - How do I import it into freeSSHd so this single user use their key?

Thanks in advance!!!

Hi,

you have to type $HOME\folder_you_want\ as "public key folder" under "Authentication". Then put the public key into the folder of the owning user where the name of the key should be the same of the user.
In this case each user who want to authenticate with a public key should have a local profile on the maschine.
Additionaly you have to create the user in your freeSSHd but the name should be the same as the profile name. As authentication method choose "Public key (SSH only)".

An other way is to store all public keys into one folder which is set as "public key folder". If you choose this way you only need to create the users in freeSSHd and name the keys like the user who use it.


Andrwe

Hi,

Thanks for the help. I have installed the cert and will have to wait to see if it works. Thanks again for the help!!!

Hi,
I am still having a problem with importing a Public Key that has been provided to me by a client. They originally emailed me a Public Key “id_dsa.pub” I followed the instructions I found and did the following.
1. I created a folder on the root of D called SFTPKEY
2. I copied the “id_dsa.pub” key and also renamed the key (a copy) to “interax.pub” – the user
3. I redirected the Authentication to Public Folder Key: d:SFTPKEY
4. I modified the user to use – Authorization: Public Key (SSH only)
5. Also under Authentication I modified “Password authentication to DISABLED.
I then restarted the service and un-loaded/loaded FreeSSHd.
This is what is received in the log file:
10-28-2008 11:52:42 HOST dcccc.imr4.com SSH interax submitted a bad key.
10-28-2008 11:52:45 HOST dcccc.imr4.com SSH interax disconnected.
Please note: This is a Windows 2008 Server running without a Domain
Please let me know what I am doing wrong to import this users Public Key.