이전 버전입니다. 현재 최신 버전은 9.66입니다. Bitvise SSH Server 9.66 · 출시일:
설치 파일 9.57
| 아키텍처 | 형식 | 설치 범위 | 파일 크기 | 다운로드 | SHA256 |
|---|---|---|---|---|---|
| 64비트 | EXE | 모든 사용자 | 33.2 MB | dl.bitvise.com | VirusTotal |
| 32비트 | EXE | 모든 사용자 | 33.2 MB | dl.bitvise.com | VirusTotal |
링크와 SHA256은 Windows 패키지 관리자 커뮤니티 매니페스트에서 가져왔습니다. 실행하기 전에 다운로드한 파일의 해시를 비교해 보십시오.
릴리스 노트
- Updates:
- In some environments, downloading a new version installer fails with Windows error code 12057 (ERROR_INTERNET_SEC_CERT_REV_FAILED). The Windows error description for this error code is misleading. The update interface now provides an error description which is hopefully more useful.
- Master/follower synchronization:
- The settings interface now checks that a synchronization password is configured, and that at least one host key or fingerprint for the master server is configured in follower settings. Synchronization cannot work without these settings.
- Control Panel:
- In previous versions 9.5x, it was possible for the SSH Server Control Panel to start fully open, instead of creating an icon in the system notification area, if it started before Windows initialized the system notification area. The SSH Server Control Panel now allows extra time for Windows to initialize the system tray. If the tray icon still cannot be created, the Control Panel opens with its window minimized.
- Scriptable settings:
- In previous versions, attempting to use the Bitvise.BssCfg COM object from a process without administrative privileges would result in a 30-second delay, followed by an unhelpful error. This now fails promptly with Access is denied.
- File transfer:
- We have seen that it's possible for Windows API functions to block indefinitely when attempting to connect to a Windows file share (network share), or when accessing a share, or disconnecting from a share.
The SSH Server now implements more granular logging for connection threads which are stuck disconnecting network shares.
When the SSH Server is shutting down, it now aborts prolonged network share disconnects, but Windows APIs may still block threads indefinitely.
We added a Best practices section in our page Accessing network shares, to help administrators increase reliability of Windows file share connections.
