Unpacking Software Livestream

Join our monthly Unpacking Software livestream to hear about the latest news, chat and opinion on packaging, software deployment and lifecycle management!

Learn More

Chocolatey Product Spotlight

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Learn More

Chocolatey Coding Livestream

Join us for the Chocolatey Coding Livestream, where members of our team dive into the heart of open source development by coding live on various Chocolatey projects. Tune in to witness real-time coding, ask questions, and gain insights into the world of package management. Don't miss this opportunity to engage with our team and contribute to the future of Chocolatey!

Learn More

Calling All Chocolatiers! Whipping Up Windows Automation with Chocolatey Central Management

Webinar from
Wednesday, 17 January 2024

We are delighted to announce the release of Chocolatey Central Management v0.12.0, featuring seamless Deployment Plan creation, time-saving duplications, insightful Group Details, an upgraded Dashboard, bug fixes, user interface polishing, and refined documentation. As an added bonus we'll have members of our Solutions Engineering team on-hand to dive into some interesting ways you can leverage the new features available!

Watch On-Demand
Chocolatey Community Coffee Break

Join the Chocolatey Team as we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Watch The Replays
Chocolatey and Intune Overview

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Watch On-Demand
Chocolatey For Business. In Azure. In One Click.

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Watch On-Demand
The Future of Chocolatey CLI

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Watch On-Demand
Hacktoberfest Tuesdays 2022

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Watch On-Demand

Downloads:

32,901

Downloads of v 8.36:

523

Last Update:

27 Oct 2019

Package Maintainer(s):

Software Author(s):

  • Bitvise Limited

Tags:

ssh server admin

Bitvise SSH Server

This is not the latest version of Bitvise SSH Server available.

  • 1
  • 2
  • 3

8.36 | Updated: 27 Oct 2019

Downloads:

32,901

Downloads of v 8.36:

523

Maintainer(s):

Software Author(s):

  • Bitvise Limited

Tags:

ssh server admin

Bitvise SSH Server 8.36

This is not the latest version of Bitvise SSH Server available.

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Bitvise SSH Server, run the following command from the command line or from PowerShell:

>

To upgrade Bitvise SSH Server, run the following command from the command line or from PowerShell:

>

To uninstall Bitvise SSH Server, run the following command from the command line or from PowerShell:

>

Deployment Method:

NOTE

This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to https://community.chocolatey.org/api/v2/)


2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade bitvise-ssh-server -y --source="'INTERNAL REPO URL'" --version="'8.36'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade bitvise-ssh-server -y --source="'INTERNAL REPO URL'" --version="'8.36'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Install bitvise-ssh-server
  win_chocolatey:
    name: bitvise-ssh-server
    version: '8.36'
    source: INTERNAL REPO URL
    state: present

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


chocolatey_package 'bitvise-ssh-server' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '8.36'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


cChocoPackageInstaller bitvise-ssh-server
{
    Name     = "bitvise-ssh-server"
    Version  = "8.36"
    Source   = "INTERNAL REPO URL"
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'bitvise-ssh-server':
  ensure   => '8.36',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

NOTE

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

Package Approved

This package was approved as a trusted package on 27 Oct 2019.

Description

Bitvise SSH Server (previously WinSSHD) provides secure remote login capabilities. Security is our SSH server's key feature: in contrast with Telnet and FTP servers, Bitvise SSH Server encrypts data during transmission. Thus, no one can sniff your password or see what files you are transferring when you access your computer over SSH.

Bitvise SSH Server is ideal for remote administration of Windows servers; for advanced users who wish to access their home machine from work, or their work machine from home; as well as for a wide spectrum of advanced tasks, such as establishing a VPN using the SSH TCP/IP tunneling feature, or providing a secure file depository using SFTP.

Personal Edition (installed by default) is free for non-commercial, personal use. It has the following limitations:

  • Can use only local Windows accounts (no domains).
  • Can configure only one Windows group ('everyone').
  • Can configure only one virtual group.
  • Has a limit of 10 Windows account entries.
  • Has a limit of 10 virtual account entries.
  • GSSAPI authentication is disabled (Kerberos and NTLM).

For any organizational use (non-commercial or commercial) or to remove the limitations of the Personal Edition, it is required to purchase a Standard Edition license and will require re-installing this package with the parameter -standardedition. See http://www.bitvise.com/ssh-server-license for more information.

Package Parameters

  • '"/installDir=C:\Path\to\installationdirectory"' - overwrite the default installation directory
  • '"/site=site-name"'
  • '"/renameExistingDir=existingDir"'
  • '"/force"'
  • '"/acceptEULA"'
  • '"/interactive"'
  • '"/noRollback"'
  • '"/activationCode=activation-code-hex"'
  • '"/keypairs=keypairs-file"'
  • '"/settings=settings-file"'
  • '"/instanceTypeSettings=fileName"'
  • '"/certificates=fileName"'
  • '"/startService"'
  • '"/startBssCtrl"'

Note: Use two single quotes when double quotes are desired."

Example

  • choco install bitvise-ssh-server -params '"/InstallLocation=C:\temp"'

Please Note: This is an automatically updated package. If you find it is
out of date by more than a day or two, please contact the maintainer(s) and
let them know the package is no longer updating correctly.


tools\chocolateyInstall.ps1
$ErrorActionPreference = 'Stop';

$toolsDir     = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url          = 'https://dl.bitvise.com/BvSshServer-Inst.exe'
$checksum     = '3cd1b063b0e327521941b514ec2a939567d5c0c07b64de88624d85fa45412e90'
$checksumType = 'sha256'

$silentArgs = ''

$packageParameters = Get-PackageParameters

# Default values
#$installDir = "directory"
$defaultSite = $true
#$site = "name"
$force = $false
$acceptEULA = $true
$interactive = $false
$noRollback = $false
#$renameExistingDir = "existingDir"
#$activationCode = "hex-code"
#$keypairs = "file"
#$settings = "file"
#$siteTypeSettings = "file"
$startService = $false
$startBssCtrl = $false

# parse packageParameters with regular expressions
if ( $packageParameters.installDir ) {
  Write-Host "installDir Argument Found"
  $installDir = $packageParameters.installDir
  $silentArgs += " -installDir=" + $installDir
  $defaultSite = $false
} elseif ( $packageParameters.site ) {
  Write-Host "site Argument Found"
  $siteName = $packageParameters.site
  $silentArgs += " -instance=" + $siteName
  $defaultSite = $false
}

# rename install location
if ( $packageParameters.renameExistingDir ) {
  Write-Host "renameExistingDir Argument Found"
  $renameExistingDir = $packageParameters.renameExistingDir
  $silentArgs += " -renameExistingDir=" + $renameExistingDir
}

if ( $packageParameters.force ) {
  Write-Host "force Argument Found"
  $force = $true
}
    
if ( $packageParameters.interactive ) {
  Write-Host "interactive Argument Found"
  $interactive = $true
}
    
if ( $packageParameters.noRollback ) {
  Write-Host "noRollback Argument Found"
  $noRollback = $true
}
    
if ( $packageParameters.activationCode ) {
  Write-Host "activationCode Argument Found"
  $activationCode = $packageParameters.activationCode
  $silentArgs += " -activationCode=" + $activationCode
}
    
if ( $packageParameters.keypairs ) {
  Write-Host "keypairs Argument Found"
  $keypairFile = $packageParameters.keypairs
  $silentArgs += " -keypairs=" + $keypairFile
}
    
if ( $packageParameters.settings ) {
  Write-Host "settings Argument Found"
  $settingsFile = $packageParameters.settings
  $silentArgs += " -settings=" + $settingsFile
}
    
if ( $packageParameters.instanceTypeSettings ) {
  Write-Host "instanceTypeSettings Argument Found"
  $instanceTypeSettings = $packageParameters.instanceTypeSettings
  $silentArgs += " -instanceTypeSettings=" + $instanceTypeSettings
}

if ( $packageParameters.certificates ) {
  Write-Host "certificates Argument Found"
  $certificates = $packageParameters.certificates
  $silentArgs += " -certificates=" + $certificates
}
    
if ( $packageParameters.startService ) {
  Write-Host "startService Argument Found"
  $startService = $true
}
    
if ( $packageParameters.startBssCtrl ) {
  Write-Host "startBssCtrl Argument Found"
  $startBssCtrl = $true
}

if ($force) { $silentArgs += " -force" }
if ($interactive) { $silentArgs += " -interactive" }
if ($noRollback) { $silentArgs += " -noRollback" }
if ($acceptEULA) { $silentArgs += " -acceptEULA" }
if ($defaultSite) { $silentArgs += " -defaultInstance" }
if ($startService) { $silentArgs += " -startService" }
if ($startBssCtrl) { $silentArgs += " -startBssCtrl" }

$packageArgs = @{
  packageName    = $env:ChocolateyPackageName
  unzipLocation  = $toolsDir
  fileType      = 'exe'
  url           = $url
  checksum      = $checksum
  checksumType  = $checksumType
  softwareName  = "Bitvise SSH Server*"
  silentArgs    = $silentArgs
  validExitCodes= @(0..63)
}

Install-ChocolateyPackage @packageArgs
tools\chocolateyUninstall.ps1
$ErrorActionPreference = 'Stop'; # stop on all errors
$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  softwareName  = 'Bitvise SSH Server*'
  fileType      = 'exe'
  silentArgs    = "-unat"
  validExitCodes= @(0, 1) # unattended uninstall exits with code 1
}

$uninstalled = $false

[array]$key = Get-UninstallRegistryKey -SoftwareName $packageArgs['softwareName']

if ($key.Count -eq 1) {
  $key | ForEach-Object {
    $packageArgs['file'] = "$($_.DisplayIcon)" # contains path to uninst.exe
    # uninst.exe needs product name as an additional parameter for uninstallation
    $packageArgs['silentArgs'] = "`"$($_.ProductName)`" $($packageArgs['silentArgs'])"

    Uninstall-ChocolateyPackage @packageArgs
  }
} elseif ($key.Count -eq 0) {
  Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
  Write-Warning "$($key.Count) matches found!"
  Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
  Write-Warning "Please alert package maintainer the following keys were matched:"
  $key | ForEach-Object {Write-Warning "- $($_.DisplayName)"}
}

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
Bitvise SSH Server 9.31 926 Monday, September 25, 2023 Approved
Bitvise SSH Server 9.29 953 Sunday, July 23, 2023 Approved
Bitvise SSH Server 9.28 130 Sunday, July 2, 2023 Approved
Bitvise SSH Server 9.27 1514 Tuesday, February 14, 2023 Approved
Bitvise SSH Server 9.26 625 Monday, January 16, 2023 Approved
Bitvise SSH Server 9.25 590 Sunday, October 30, 2022 Approved
Bitvise SSH Server 9.24 195 Sunday, October 9, 2022 Approved
Bitvise SSH Server 9.23 685 Monday, June 6, 2022 Approved
Bitvise SSH Server 9.22 84 Tuesday, May 31, 2022 Approved
Bitvise SSH Server 9.21 68 Monday, May 30, 2022 Approved
Bitvise SSH Server 9.19 65 Sunday, May 29, 2022 Approved
Bitvise SSH Server 8.49 2418 Wednesday, September 15, 2021 Approved
Bitvise SSH Server 8.48 824 Monday, May 24, 2021 Approved
Bitvise SSH Server 8.47.0.20210420 347 Tuesday, April 20, 2021 Approved
Bitvise SSH Server 8.47 406 Sunday, April 4, 2021 Approved
Bitvise SSH Server 8.45 730 Wednesday, December 30, 2020 Approved
Bitvise SSH Server 8.44 919 Sunday, October 4, 2020 Approved
Bitvise SSH Server 8.43 1442 Sunday, June 7, 2020 Approved
Bitvise SSH Server 8.42 576 Sunday, May 10, 2020 Approved
Bitvise SSH Server 8.41 1178 Saturday, February 15, 2020 Approved
Bitvise SSH Server 8.39 591 Friday, January 17, 2020 Approved
Bitvise SSH Server 8.38 197 Monday, January 13, 2020 Approved
Bitvise SSH Server 8.37 633 Monday, November 25, 2019 Approved
Bitvise SSH Server 8.36 523 Sunday, October 27, 2019 Approved
Bitvise SSH Server 8.35 656 Tuesday, August 20, 2019 Approved
Bitvise SSH Server 8.34 385 Monday, June 17, 2019 Approved
Bitvise SSH Server 8.33 305 Wednesday, May 29, 2019 Approved
Bitvise SSH Server 8.32 472 Friday, April 19, 2019 Approved
Bitvise SSH Server 8.31 232 Tuesday, April 16, 2019 Approved
Bitvise SSH Server 8.29 330 Saturday, March 23, 2019 Approved
Bitvise SSH Server 8.28 233 Friday, March 15, 2019 Approved
Bitvise SSH Server 8.27 261 Monday, March 4, 2019 Approved
Bitvise SSH Server 8.26 269 Friday, February 22, 2019 Approved
Bitvise SSH Server 8.25 227 Monday, February 18, 2019 Approved
Bitvise SSH Server 8.24 290 Sunday, January 27, 2019 Approved
Bitvise SSH Server 8.22 416 Friday, December 21, 2018 Approved
Bitvise SSH Server 8.21 226 Wednesday, December 19, 2018 Approved
Bitvise SSH Server 8.19.0.20181218 230 Tuesday, December 18, 2018 Approved
Bitvise SSH Server 8.19 1111 Saturday, December 8, 2018 Approved
Bitvise SSH Server 7.39 1328 Thursday, January 25, 2018 Approved
Bitvise SSH Server 7.34 918 Wednesday, August 2, 2017 Approved
Bitvise SSH Server 7.33 562 Wednesday, July 12, 2017 Approved
Bitvise SSH Server 7.29 694 Saturday, April 1, 2017 Approved
Bitvise SSH Server 7.26 626 Wednesday, February 8, 2017 Approved
Bitvise SSH Server 7.25 482 Monday, January 23, 2017 Approved
Bitvise SSH Server 7.24 435 Saturday, January 14, 2017 Approved
Bitvise SSH Server 7.23 495 Wednesday, January 11, 2017 Approved
Bitvise SSH Server 7.22 443 Wednesday, January 4, 2017 Approved
Bitvise SSH Server 7.21 489 Saturday, December 31, 2016 Approved
Bitvise SSH Server 7.16 492 Saturday, December 10, 2016 Approved
Bitvise SSH Server 7.15 618 Thursday, October 20, 2016 Approved
Bitvise SSH Server 7.14 697 Thursday, August 4, 2016 Approved
Bitvise SSH Server 6.47 542 Saturday, June 11, 2016 Approved
Discussion for the Bitvise SSH Server Package

Ground Rules:

  • This discussion is only about Bitvise SSH Server and the Bitvise SSH Server package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Bitvise SSH Server, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus