Use Microsoft's OpenSSH #92
Draft
+1,464
−1,634
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aramprice
force-pushed
the
use-ms-open-ssh
branch
from
56019c2 to
3eae817
Compare
cf-foundation-community-automation
bot
moved this to Inbox
in Foundational Infrastructure Working Group
aramprice
force-pushed
the
use-ms-open-ssh
branch
5 times, most recently
from
a575dcf to
5261d4e
Compare
aramprice
force-pushed
the
use-ms-open-ssh
branch
5 times, most recently
from
1fc8ddc to
a5a48b2
Compare
aramprice
force-pushed
the
use-ms-open-ssh
branch
from
1efb9ff to
df5a408
Compare
aramprice
force-pushed
the
use-ms-open-ssh
branch
from
df5a408 to
e61fd2a
Compare
For the packer-built stemcells install OpenSSH as part of VM setup, not WinRM because executing `Add-WindowsCapability` via WinRM does not appear to be allowed. So instead move the installation of OpenSSH.Server to the various IaaS pre-boot scrips which are not executed via WinRM. The installations of OpenSSSH.Server happens as follows: - Azure: add a `custom_script` parameter to packer config - AWS: added to `setup_winrm.txt` - GCP: add to `setup-winrm.ps1` and use `sysprep-specialize-script-ps1` - vSphere: TODO [1] https://learn.microsoft.com/en-us/windows-server/administration/openssh/openssh_install_firstuse
For the stembuild-built stemcells install OpenSSH as part of VM setup, not WinRM because executing `Add-WindowsCapability` via WinRM does not appear to be allowed. So instead installation of OpenSSH.Server happens via `govc guest.run` to the various IaaS pre-boot scrips which are not executed via WinRM. [1] https://learn.microsoft.com/en-us/windows-server/administration/openssh/openssh_install_firstuse
In order to validate installation of Microsoft's OpenSSH specs need to check for a differently named firewall rule. This commit adds parameters to Concourse tasks to specifiy the firewal rule name.
aramprice
force-pushed
the
use-ms-open-ssh
branch
from
e61fd2a to
bffb049
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR should be rebased after #94 has been merged