|
| 1 | +# Created with YamlCreate.ps1 Dumplings Mod |
| 2 | +# yaml-language-server: $schema=https://aka.ms/winget-manifest.defaultLocale.1.12.0.schema.json |
| 3 | + |
| 4 | +PackageIdentifier: Bitvise.SSH.Server |
| 5 | +PackageVersion: "9.58" |
| 6 | +PackageLocale: en-US |
| 7 | +Publisher: Bitvise Limited |
| 8 | +PublisherUrl: https://bitvise.com/ |
| 9 | +PublisherSupportUrl: https://bitvise.com/contact |
| 10 | +PrivacyUrl: https://bitvise.com/privacy-policy |
| 11 | +Author: Bitvise Limited |
| 12 | +PackageName: Bitvise SSH Server |
| 13 | +PackageUrl: https://bitvise.com/ssh-server |
| 14 | +License: Proprietary |
| 15 | +LicenseUrl: https://bitvise.com/ssh-server-license |
| 16 | +Copyright: Copyright (C) 2000-2026 by Bitvise Limited. |
| 17 | +CopyrightUrl: https://bitvise.com/terms-of-use |
| 18 | +ShortDescription: Secure file transfer and terminal shell access for Windows |
| 19 | +Description: |- |
| 20 | + Our SSH server supports all desktop and server versions of Windows, 32-bit and 64-bit, from Windows XP SP3 and Windows Server 2003, up to the most recent – Windows 11 and Windows Server 2025. |
| 21 | + Bitvise SSH Server includes the following: |
| 22 | + - SFTP server: Secure file transfer using SFTP - compatible with a wide variety of clients |
| 23 | + - SCP server: Secure file transfer using SCP - compatible with command line and graphical clients |
| 24 | + - FTPS server: Secure file transfer using FTP over TLS/SSL - compatible with secure FTPS clients |
| 25 | + - SSH server: Secure remote access via console - vt100, xterm and bvterm are supported |
| 26 | + - Secure remote access via GUI - Remote Desktop or WinVNC required |
| 27 | + - Secure, effortless Git integration |
| 28 | + - Secure TCP/IP connection tunneling (port forwarding) |
| 29 | +Moniker: bitvisesshserver |
| 30 | +Tags: |
| 31 | +- sftp |
| 32 | +- ssh |
| 33 | +- sshd |
| 34 | +Agreements: |
| 35 | +- AgreementLabel: End User License Agreement (EULA) |
| 36 | + AgreementUrl: https://bitvise.com/ssh-server-license |
| 37 | +ReleaseNotes: |- |
| 38 | + - Startup: |
| 39 | + - During SSH Server startup, it is unusual, but possible, for Windows APIs to block initialization of SSH Server components for long periods of time. If the delay was very long, the Long Operations Monitor, a new component in versions 9.5x, could exit unexpectedly if other components have not yet initialized. |
| 40 | + The initialization sequence is now reorganized to avoid this type of issue. Additionally, long delays during component initialization are now logged at Info or Trace level, depending on the duration. |
| 41 | + - FTPS: |
| 42 | + - For FTPS connections, the SSH Server no longer adds the authorized_keys mount point (by default, "/.ssh") if SSH public key management using authorized_keys is enabled for the user. |
| 43 | + Previous 9.5x versions would add this mount point for FTPS, even though SSH public key management is not supported using FTPS. Connections that tried to access this path via FTPS would become unresponsive, although the connection would still respond to disconnect. |
| 44 | +ReleaseNotesUrl: https://www.bitvise.com/ssh-server-version-history-9-5#958 |
| 45 | +PurchaseUrl: https://bitvise.com/ssh-server-pricing |
| 46 | +Documentations: |
| 47 | +- DocumentLabel: Printable Documentation |
| 48 | + DocumentUrl: https://bitvise.com/printable-docs/ssh-server-doc-printable |
| 49 | +- DocumentLabel: Users' Guide |
| 50 | + DocumentUrl: https://bitvise.com/ssh-server-users-guide |
| 51 | +- DocumentLabel: FAQ |
| 52 | + DocumentUrl: https://bitvise.com/ssh-server-usage-faq |
| 53 | +ManifestType: defaultLocale |
| 54 | +ManifestVersion: 1.12.0 |
0 commit comments