Comments on Got freeSSHd (mostly) working

  1. No Subject

    I believe you have to grant the freesshd service access to create system tokens.

    Run gpedit.msc (or apply group policy from the directory)

    replace "sshd" with whatever account the process is running as, the default is SYSTEM

    Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment

    Access this computer from the network -> add sshd
    Act as part of the operating system -> add sshd
    Adjust memory quotas for a process -> add sshd
    Allow log on locally -> add sshd
    Create a token object -> add sshd
    Create global objects -> add sshd
    Log on as a service -> add sshd
    Replace a process level token -> add sshd

  2. No Subject

    Thanks so much; this was the final thing I tried before I basically gave up getting OpenSSH sshd to work on Windows, but it did the job. Great bit of advice.

  3. No Subject

    I have been having the exact same issues. For a few years actually.
    Just set out to see if I could fix things and read this post - it's good to know I'm not alone.
    The weird part is that SFTP login works just fine using NT authentication.
    Well, I guess it's not that weird since the problem is coming from spawning a shell.
    What is weird is that years later, FreeSSHd still has the exact same issue.
    I guess I'll try W. Strucke's fix.
    Thanks for posting.

  4. freesshd on windows 64bit fix

    unexpected close of putty window when loging in. Fix
    1: Stop and Disable Freesshd windows services.
    2: copy and paste the following in a .reg file

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run]
    "sshd"="\"C:\\Program Files (x86)\\freeSSHd\\FreeSSHDService.exe\""

Add your comments #

A comment body is required. No HTML code allowed. URLs starting with http:// or ftp:// will be automatically converted to hyperlinks.