Ansible
PS DSC
Downloads:
212,913
Downloads of v 2016.05.30.20160827:
9,067
Last Update:
27 Aug 2016
Package Maintainer(s):
Software Author(s):
- Microsoft
Tags:
win32-openssh admin- Software Specific:
- Software Site
- Software Source
- Software License
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Win32 OpenSSH (Microsoft Port)
This is not the latest version of Win32 OpenSSH (Microsoft Port) available.
- 1
- 2
- 3
2016.05.30.20160827 | Updated: 27 Aug 2016
- Software Specific:
- Software Site
- Software Source
- Software License
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
212,913
Downloads of v 2016.05.30.20160827:
9,067
Maintainer(s):
Software Author(s):
- Microsoft
Win32 OpenSSH (Microsoft Port) 2016.05.30.20160827
This is not the latest version of Win32 OpenSSH (Microsoft Port) available.
Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by Microsoft. The inclusion of Microsoft trademark(s), if any, upon this webpage is solely to identify Microsoft goods or services and not for commercial purposes.
- 1
- 2
- 3
Some Checks Have Failed or Are Not Yet Complete
Not All Tests Have Passed
Validation Testing Passed
Verification Testing Passed
DetailsScan Testing Resulted in Flagged:
This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.
We recommend clicking the "Details" link to make your own decision on installing this package.
Deployment Method: Individual Install, Upgrade, & Uninstall
To install Win32 OpenSSH (Microsoft Port), run the following command from the command line or from PowerShell:
To upgrade Win32 OpenSSH (Microsoft Port), run the following command from the command line or from PowerShell:
To uninstall Win32 OpenSSH (Microsoft Port), run the following command from the command line or from PowerShell:
Deployment Method:
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
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
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
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download win32-openssh --internalize --version=2016.05.30.20160827 --source=https://community.chocolatey.org/api/v2/ -
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'" - Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade win32-openssh -y --source="'INTERNAL REPO URL'" --version="'2016.05.30.20160827'" [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 win32-openssh -y --source="'INTERNAL REPO URL'" --version="'2016.05.30.20160827'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install win32-openssh
win_chocolatey:
name: win32-openssh
version: '2016.05.30.20160827'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'win32-openssh' do
action :install
source 'INTERNAL REPO URL'
version '2016.05.30.20160827'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller win32-openssh
{
Name = "win32-openssh"
Version = "2016.05.30.20160827"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'win32-openssh':
ensure => '2016.05.30.20160827',
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.
Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...
This package was approved as a trusted package on 27 Aug 2016.
Open SSH tools for Windows.
This is the Microsoft PowerShell Team's recent port.
Works in all CLIs and does not require .NET.
Includes the following tools:
* ssh.exe
* ssh-add.exe
* ssh-agent.exe
* ssh-keygen.exe
* ssh-keyscan.exe
* ssh-keysign.exe
* ssh-pkcs11-helper.exe
* scp.exe
* sftp.exe
* sshd.exe (server)
* sftp-server.exe
This package performs the following operations that you normally have to hack at until you get what you want:
* Install Appropriate Bitness for the version of Windows
* Install to Program Files (malware protection and following advice of dev team)
* Add SSH location to System PATH
* Optionally install sshd windows service (Requires parameter - see below)
* Optionally install sshd server "key based authentication" (Requires parameter - see below)
* Cleanly uninstall all of the above (removing config files and server keys requires special switch - see below)
The package also attempts to keep you out of trouble when configuring the sshd service:
* Will not install sshd server if an different sshd server is already running
* Will not delete server keys on uninstall or reinstall (unless you override with switch below)
* Will not upgrade or uninstall if the service is running and you did not specify /SSHServerFeature (you forget about the service on a machine where you want to upgrade the client tools)
* If you use the server's Key Based Authentication feature, install and uninstall behave differently to account for the integration of this component
This package supports the following parameters:
-params '"/SSHServerFeature"' (Install and Uninstall)
Also install sshd Windows Service - including opening port 22.
If this parameter is not included on an upgrade or uninstall and
the sshd server is installed - an error is generated. You must
use this switch to indicate you have made preparations for the
sshd service to be interrupted or removed.
-params '"/SSHServerFeature /KeyBasedAuthenticationFeature"'
Also install sshd Windows Service - including opening port 22 and
it with Key Based Authentication (reboot required before active)
-params '"/SSHServerFeature /KeyBasedAuthenticationFeature /DeleteServerKeysAfterInstalled"'
Also install sshd Windows Service - including opening port 22 and
it with Key Based Authentication (reboot required before active)
Server keys are deleted after added to the ssh-agent (you will not have an opportunity to copy them)
-params '"/DeleteConfigAndServerKeys"' (Uninstall)
By default an uninstall does not remove config files nor server keys.
-params '"/UseNTRights"'
By default the install uses PowerShell code that was tested on Nano - which means it should work on server core without WOW64.
If this code does not work for you, you can use this switch to invoke the 32-bit ntrights.exe
Please be aware that 32-bit ntrights.exe will NOT work on Windows Systems that doe not have WOW64 installed - this would mainly
affect Server Core where this feature is optional and not installed by default and Server Nano where 32-bit is not supported.
param($accountToAdd)
#written by Ingo Karstein, http://blog.karstein-consulting.com
# v1.0, 01/03/2014
## <--- Configure here
if( [string]::IsNullOrEmpty($accountToAdd) ) {
Write-Host "no account specified"
exit
}
## ---> End of Config
$sidstr = $null
try {
$ntprincipal = new-object System.Security.Principal.NTAccount "$accountToAdd"
$sid = $ntprincipal.Translate([System.Security.Principal.SecurityIdentifier])
$sidstr = $sid.Value.ToString()
} catch {
$sidstr = $null
}
Write-Host "Account: $($accountToAdd)" -ForegroundColor DarkCyan
if( [string]::IsNullOrEmpty($sidstr) ) {
Write-Host "Account not found!" -ForegroundColor Red
exit -1
}
Write-Host "Account SID: $($sidstr)" -ForegroundColor DarkCyan
$tmp = [System.IO.Path]::GetTempFileName()
Write-Host "Export current Local Security Policy" -ForegroundColor DarkCyan
secedit.exe /export /cfg "$($tmp)"
$c = Get-Content -Path $tmp
$currentSetting = ""
foreach($s in $c) {
if( $s -like "SeServiceLogonRight*") {
$x = $s.split("=",[System.StringSplitOptions]::RemoveEmptyEntries)
$currentSetting = $x[1].Trim()
}
}
if( $currentSetting -notlike "*$($sidstr)*" ) {
Write-Host "Modify Setting ""Logon as a Service""" -ForegroundColor DarkCyan
if( [string]::IsNullOrEmpty($currentSetting) ) {
$currentSetting = "*$($sidstr)"
} else {
$currentSetting = "*$($sidstr),$($currentSetting)"
}
Write-Host "$currentSetting"
$outfile = @"
[Unicode]
Unicode=yes
[Version]
signature="`$CHICAGO`$"
Revision=1
[Privilege Rights]
SeServiceLogonRight = $($currentSetting)
"@
$tmp2 = [System.IO.Path]::GetTempFileName()
Write-Host "Import new settings to Local Security Policy" -ForegroundColor DarkCyan
$outfile | Set-Content -Path $tmp2 -Encoding Unicode -Force
#notepad.exe $tmp2
Push-Location (Split-Path $tmp2)
try {
secedit.exe /configure /db "secedit.sdb" /cfg "$($tmp2)" /areas USER_RIGHTS
#write-host "secedit.exe /configure /db ""secedit.sdb"" /cfg ""$($tmp2)"" /areas USER_RIGHTS "
} finally {
Pop-Location
}
} else {
Write-Host "NO ACTIONS REQUIRED! Account already in ""Logon as a Service""" -ForegroundColor DarkCyan
}
Write-Host "Done." -ForegroundColor DarkCyan
$ErrorActionPreference = 'Stop'; # stop on all errors
$packageName= 'win32-openssh'
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$OSBits = Get-ProcessorBits
#On 64-bit, always favor 64-bit Program Files no matter what our execution is now (works back past XP / Server 2003)
If ($env:ProgramFiles.contains('x86'))
{
$PF = $env:ProgramFiles.replace(' (x86)','')
}
Else
{
$PF = $env:ProgramFiles
}
#$TargetFolder = "$PF\OpenSSH"
$TargetFolder = "$PF\OpenSSH-Win$($OSBits)"
$TargetFolderOld = "$PF\OpenSSH-Win$($OSBits)"
# Default the values
$SSHServerFeature = $false
$KeyBasedAuthenticationFeature = $false
$arguments = @{};
$packageParameters = $env:chocolateyPackageParameters;
# Now parse the packageParameters using good old regular expression
if ($packageParameters) {
$match_pattern = "\/(?<option>([a-zA-Z]+)):(?<value>([`"'])?([a-zA-Z0-9- _\\:\.]+)([`"'])?)|\/(?<option>([a-zA-Z]+))"
#"
$option_name = 'option'
$value_name = 'value'
if ($packageParameters -match $match_pattern ){
$results = $packageParameters | Select-String $match_pattern -AllMatches
$results.matches | % {
$arguments.Add(
$_.Groups[$option_name].Value.Trim(),
$_.Groups[$value_name].Value.Trim())
}
}
else
{
throw "Package Parameters were found but were invalid (REGEX Failure)"
}
if ($arguments.ContainsKey("SSHServerFeature")) {
Write-Host "/SSHServerFeature - Uninstalling SSH Server Feature if Present."
$SSHServerFeature = $true
}
if ($arguments.ContainsKey("DeleteConfigAndServerKeys")) {
Write-Host "/DeleteConfigAndServerKeys - Removing SSH Config and Server Keys."
$DeleteConfigAndServerKeys = $true
}
} else {
Write-Debug "No Package Parameters Passed in";
}
$SSHServiceInstanceExistsAndIsOurs = ([bool]((Get-WmiObject win32_service | ?{$_.Name -ilike 'sshd'} | select -expand PathName) -ilike "*$TargetFolder*"))
If ($SSHServerFeature -AND (!$SSHServiceInstanceExistsAndIsOurs) -AND (Get-Service sshd -ErrorAction SilentlyContinue))
{
$ExistingSSHDInstancePath = (Get-WmiObject win32_service | ?{$_.Name -ilike 'sshd'} | select -expand PathName)
Throw "You have requested that the SSHD service be uninstalled, but this system appears to have an instance of an SSHD service configured for another folder ($ExistingSSHDInstancePath). Ignoring /SSHServerFeature"
$SSHServerFeature = $False
}
If ((!$SSHServerFeature) -AND $SSHServiceInstanceExistsAndIsOurs)
{
Throw "There is a configured instance of the SSHD service, please specify the /SSHServerFeature to confirm it is OK to UNINSTALL the SSHD service at this time."
}
If ([bool](get-process ssh -erroraction silentlycontinue | where {$_.Path -ilike "*$TargetPath*"}))
{
Throw "It appears you have instances of ssh.exe (client) running from the folder this package installs to, please terminate them and try again."
}
If ($SSHServiceInstanceExistsAndIsOurs -AND ([bool](Get-Service SSHD -ErrorAction SilentlyContinue | where {$_.Status -ieq 'Running'})))
{
#Shutdown and unregister service for upgrade
Stop-Service SSHD -Force
Start-Sleep -seconds 3
If (([bool](Get-Service SSHD | where {$_.Status -ieq 'Running'})))
{
Throw "Could not stop the SSHD service, please stop manually and retry this package."
}
Stop-Service ssh-agent -Force
Start-Sleep -seconds 3
If (([bool](Get-Service ssh-agent | where {$_.Status -ieq 'Running'})))
{
Throw "Could not stop the ssh-agent service, please stop manually and retry this package."
}
}
If ((get-item 'Registry::HKLM\System\CurrentControlSet\Control\Lsa').getvalue("authentication packages") -contains 'msv1_0\0ssh-lsa.dll')
{
$KeyBasedAuthenticationFeatureINSTALLED = $True
}
If ($SSHServiceInstanceExistsAndIsOurs -AND ([bool](Get-Service SSHD | where {$_.Status -ieq 'Running'})))
{
#Shutdown and unregister service for upgrade
Stop-Service sshd -Force
If (([bool](Get-Service SSHD | where {$_.Status -ieq 'Running'})))
{
Throw "Could not stop the SSHD service, please stop manually and retry this package."
}
Stop-Service ssh-agent -Force
Start-Sleep -seconds 3
If (([bool](Get-Service ssh-agent | where {$_.Status -ieq 'Running'})))
{
Throw "Could not stop the ssh-agent service, please stop manually and retry this package."
}
}
If ($SSHServiceInstanceExistsAndIsOurs -AND ($SSHServerFeature))
{
Stop-Service sshd
sc.exe delete sshd 1> null
Stop-Service ssh-agent
sc.exe delete ssh-agent 1> null
}
If ($KeyBasedAuthenticationFeatureINSTALLED)
{
If (Test-Path "$env:windir\sysnative")
{ #We are running in a 32-bit process under 64-bit Windows
$sys32dir = "$env:windir\sysnative"
}
Else
{ #We are on a 32-bit OS, or 64-bit proc on 64-bit OS
$sys32dir = "$env:windir\system32"
}
$AuthpkgToRemove = 'msv1_0\0ssh-lsa.dll'
foreach ($authpackage in (get-item 'Registry::HKLM\System\CurrentControlSet\Control\Lsa').getvalue("authentication packages"))
{
If ($authpackage)
{
If ($authpackage -ine "$AuthpkgToRemove")
{
[string[]]$Newauthpackages += "$authpackage"
}
}
}
Set-ItemProperty "HKLM:\SYSTEM\CurrentControlSet\Control\Lsa\" "Authentication Packages" $Newauthpackages
del "$sys32dir\ssh-lsa.dll" -force
}
#Don't remove config in case they reinstall.
If ($DeleteConfigAndServerKeys)
{
Write-Warning "Removing all config and server keys as requested by /DeleteConfigAndServerKeys"
If (Test-Path $TargetFolder) {Remove-Item "$TargetFolder\*" -Recurse -Force}
If (Test-Path $TargetFolderOLD) {Remove-Item "$TargetFolderOLD\*" -Recurse -Force}
}
Else
{
If (Test-Path $TargetFolder) {Remove-Item "$TargetFolder\*.*" -include *.exe,*.dll,*.cmd -Recurse -Force}
If (Test-Path $TargetFolderOLD) {Remove-Item "$TargetFolder\*.*" -include *.exe,*.dll,*.cmd -Recurse -Force}
Write-Warning "NOT REMOVED: Config files and any keys in `"$TargetFolder`" were NOT REMOVED - you must remove them manually or use the package uninstall parameter /DeleteConfigAndServerKeys."
}
netsh advfirewall firewall delete rule name='SSHD Port win32-openssh'
$PathToRemove = "$TargetFolder"
foreach ($path in [Environment]::GetEnvironmentVariable("PATH","Machine").split(';'))
{
If ($Path)
{
If (($path -ine "$PathToRemove") -AND ($path -ine "$PathToRemove\"))
{
[string[]]$Newpath += "$path"
}
}
}
$AssembledNewPath = ($newpath -join(';')).trimend(';')
[Environment]::SetEnvironmentVariable("PATH",$AssembledNewPath,"Machine")
md5: 416C43AEB17252EE33048BD1F277D2A5 | sha1: 085DEB77551F9F6201E5AA352B62CAD91C3005E5 | sha256: F46BAA1B6227226518E42263E9B4808F81C27D060207DF160F9AC64DEAE4F4F5 | sha512: 3155DE3FB04F1DF246D6CECFA1C89F8AE9963C18BE1CE717731FF210AB39D537BE01231002A54D4346B4116E3505F387C92DFECC18A80CE7EB99C6D33E5F1F2A
<#
.\Plaininstall.ps1 -SSHServerFeature -KeyBasedAuthenticationFeature
#>
Param (
[Parameter(HelpMessage="Including SSH Server Feature.")]
[switch]$SSHServerFeature,
[Parameter(HelpMessage="Using ntrights.exe to set service permissions (will not work, but generate warning if WOW64 is not present on 64-bit machines)")]
[switch]$UseNTRights,
[Parameter(HelpMessage="Deleting server private keys after they have been secured.")]
[switch]$DeleteServerKeysAfterInstalled,
[Parameter(HelpMessage="Use key based authentication for SSHD, must also use -SSHServerFeature")]
[switch]$KeyBasedAuthenticationFeature
)
#$passedargList += $MyInvocation.BoundParameters.GetEnumerator() | foreach {$curarg = $_ ;"$(. { switch ($($curarg.Value)) {'true' { "-$($curarg.Key)" } 'false' { '' } default { "-$($curarg.Key) $($curarg.Value)" } }})"}
. ".\chocolateyinstall.ps1"
Log in or click on link to see number of positives.
- ntrights.exe (f46baa1b6227) - ## / 68
- sftp-server.exe (a1694276656c) - ## / 53
- sftp.exe (9cb4a2224e13) - ## / 56
- ssh-add.exe (3fa10500ace0) - ## / 54
- ssh-agent.exe (cc69a21ab9e3) - ## / 54
- ssh-keygen.exe (0a2c8752adfa) - ## / 53
- ssh-lsa.dll (e6146964bbb6) - ## / 53
- ssh-shellhost.exe (3a472cbdb934) - ## / 50
- ssh.exe (c4a7ee34b240) - ## / 53
- sshd.exe (ac24981e6375) - ## / 54
- sftp-server.exe (8c18a19dae9e) - ## / 53
- sftp.exe (31c8246edf5a) - ## / 53
- ssh-add.exe (061dc611ee48) - ## / 55
- ssh-agent.exe (33a6a40a7f8f) - ## / 54
- ssh-keygen.exe (e55f654ba49c) - ## / 54
- ssh-lsa.dll (030fd7c2a310) - ## / 49
- ssh-shellhost.exe (3cedd8a63ead) - ## / 54
- ssh.exe (10b17d54cb96) - ## / 54
- sshd.exe (8ec713f594c0) - ## / 54
- OpenSSH-Win64.zip (e20176b41ac4) - ## / 56
- OpenSSH-Win32.zip (b8ff1df7a32a) - ## / 55
- win32-openssh.2016.05.30.20160827.nupkg (59b200d9a742) - ## / 55
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 |
|---|---|---|---|---|
| [DEPRECATED] Win32 OpenSSH (Microsoft Port) 2016.05.30.20160922 | 27481 | Thursday, September 22, 2016 | Approved | |
| Win32 OpenSSH (Microsoft Port) 2016.05.30.20160908 | 24400 | Saturday, September 10, 2016 | Approved | |
| Win32 OpenSSH (Microsoft Port) 2016.05.30.20160902 | 12451 | Saturday, September 3, 2016 | Approved | |
| Win32 OpenSSH (Microsoft Port) 2016.05.30.20160827 | 9067 | Saturday, August 27, 2016 | Approved | |
| Win32 OpenSSH (Microsoft Port) 2016.05.30.20160807 | 6201 | Thursday, August 11, 2016 | Approved | |
| Win32 OpenSSH (Microsoft Port) 2016.05.30 | 12503 | Saturday, June 4, 2016 | Approved | |
| Win32 OpenSSH (Microsoft Port) 2016.05.15 | 647 | Wednesday, May 18, 2016 | Approved | |
| Win32 OpenSSH (Microsoft Port) 2016.04.05 | 115814 | Wednesday, April 6, 2016 | Approved | |
| Win32 OpenSSH (Microsoft Port) 2016.03.19 | 908 | Sunday, March 20, 2016 | Approved | |
| Win32 OpenSSH (Microsoft Port) 2016.02.25.20150315 | 673 | Tuesday, March 15, 2016 | Approved | |
| Win32 OpenSSH (Microsoft Port) 2016.02.25.20150310 | 669 | Thursday, March 10, 2016 | Approved | |
| Win32 OpenSSH (Microsoft Port) 2016.02.25 | 757 | Sunday, February 28, 2016 | Approved | |
| Win32 OpenSSH (Microsoft Port) 2015.12.22 | 732 | Monday, February 15, 2016 | Approved | |
| Win32 OpenSSH (Microsoft Port) 0.0.0.9 | 525 | Sunday, September 18, 2016 | Approved |
Microsoft
WARNING: Target folder is changing to re-align with current Win32-OpenSSH installation from the product team.
It is recommended that you uninstall and reinstall if you have an older version.
With switch /UseNTRights Package uses ntrights.exe on 32-bit windows and on 64-bit windows - ONLY IF THE 32-bit SUBSYSTEM IS INSTALLED - otherwise it attempts to use Posh Code to grant logonasaservice right.
Code used for setting rights WITHOUT /UseNTRights was tested as working on Nano, which means it should work on server core without WOW64.
Package explicity sets log level to QUIET because on some systems the current version of sshd repeatedly logs the same line at a rate of about 1 GB / 2 hours with default log settings.
Package incorporates securing of the server keys using the SSH agent as per the product release notes below.
Product release notes: https://github.com/PowerShell/Win32-OpenSSH/releases/tag/5_15_2016
https://github.com/PowerShell/Win32-OpenSSH/releases/tag/5_30_2016
This package has no dependencies.
Ground Rules:
- This discussion is only about Win32 OpenSSH (Microsoft Port) and the Win32 OpenSSH (Microsoft Port) 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 Win32 OpenSSH (Microsoft Port), 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.