Dit is ’n ouer weergawe. Die nuutste weergawe is 9.68. Bitvise SSH Server 9.68 · Vrygestel:
Installeerlêers 9.45
| Argitektuur | Tipe | Bestek | Lêergrootte | Aflaai | SHA256 |
|---|---|---|---|---|---|
| 64-bis | EXE | Alle gebruikers | 30,4 MB | dl.bitvise.com | VirusTotal |
| 32-bis | EXE | Alle gebruikers | 30,4 MB | dl.bitvise.com | VirusTotal |
Die skakel en SHA256 kom uit die gemeenskapsmanifes van die Windows-pakketbestuurder. Vergelyk die hashwaarde van die afgelaaide lêer voordat u dit laat loop.
Vrystellingsnotas
- Installation:
- When using the -keypairs command-line parameter, the SSH Server installer did not support importing passphrase-protected keypairs. Also, the installer would import all keypairs if the file is in the .wkp format (as stored in the Config subdirectory of the SSH Server installation directory); but it would only import the first keypair when using the Bitvise .bkp format, even though the format supports multiple keypairs.
The installer now accepts a -keypairsPass parameter to import passphrase-protected keypairs, and imports all keypairs when using the .bkp format.
- Proxy support:
- When configured to make an outgoing connection via an HTTP CONNECT proxy, the SSH Server now sends an HTTP/1.1 request, including a Host header. Previous versions sent an HTTP/1.0 request (no Host header).
- File transfer:
- If a user was configured with a virtual filesystem mount point with the permission Permit Move Existing, and also Permit Read/Write/Delete New; then after moving or renaming a file, the SSH Server would treat the destination file as a new upload, and permit the user to read, write or delete it; even if the user does not have the corresponding virtual mount point permissions for existing files.
When moving existing files, the SSH Server no longer considers the moved-to file as new.
This issue could have a security impact if you have settings which permit users to move files, but the settings do not account for that previous SSH Server versions will treat moved-to files as new.
