
- #GRSYNC WINDOWS PASSWORD ACTIVATION CODE#
- #GRSYNC WINDOWS PASSWORD SOFTWARE#
- #GRSYNC WINDOWS PASSWORD LICENSE#
- #GRSYNC WINDOWS PASSWORD WINDOWS#
Filesystem permissions on these directories are configured properly by default by Windows.
#GRSYNC WINDOWS PASSWORD WINDOWS#
If you are unfamiliar with Windows permissions, we suggest installing into a standard location such as C:\Program Files or C:\Program Files (x86). This is achieved by configuring permissions using Windows File Explorer. For example, if you are installing under D:\Programs, you must ensure that only administrators have the right to rename or modify files and subdirectories under this location. To fix this problem, you must set up Windows filesystem permissions on the parent directory into which you are installing Bitvise software.

If the filesystem permissions are not fixed, a problem can still arise if non-administrative accounts are added later.
#GRSYNC WINDOWS PASSWORD SOFTWARE#
Recent versions of our software will warn about this situation, and will do so even if the system does not currently have any non-administrative users. This means that any other user on the system who is able to rename a Bitvise software installation directory, or to rename or modify files it contains, can use this limited access to give themselves complete administrative access to the system. The SSH Server runs as Local System or equivalent, and the SSH Client can be run by administrators. This can happen if you created a custom parent directory such as D:\Programs into which you are installing Bitvise software, but you have not taken care to configure Windows filesystem permissions on that directory.īitvise software generally runs with high privileges. Why is it insecure, and what can I do about it? The SSH Server or Client installer warns me that the "installation directory is insecure". On Windows Server 2016, right-click the installer executable in Windows Explorer, click Properties, and see if you need to check Unblock on the General tab. How do I start it?ĭepending on your Windows version, security settings, and how the installer was downloaded, you may need to take an extra step to start it.

When I try to run the SSH Server or Client installer, nothing happens. The Personal Edition is available only for users who are both personal and non-commercial, and are therefore likely to be unaffected by the above limitations.
#GRSYNC WINDOWS PASSWORD LICENSE#
All organizations, as well as personal users who do not qualify as non-commercial, must purchase a license for the Standard Edition. If you are deciding whether to use the Personal or Standard Edition – in most cases, this is not a technical decision.


#GRSYNC WINDOWS PASSWORD ACTIVATION CODE#
No activation code is needed to use Bitvise SSH Server for personal use. Where do I get an activation code for personal use? Whenever you have a problem, the SSH server log files are the first place you should look. These are located by default in the 'Logs' subdirectory of the SSH server installation directory. Bitvise SSH Server writes warnings and errors into the Application section of the Windows Event Log, but it also writes more detailed information to textual log files. Frequently Asked Questions about Bitvise SSH ServerĪs an administrator of Bitvise SSH Server, you should first become comfortable with the SSH server's log files.
