Downloads:
78
Downloads of v 0.3.5.20240423:
10
Last Update:
23 Apr 2024
Published Date:
23 Apr 2024
Package Maintainer(s):
Software Author(s):
- Shayne Sweeney
Tags:
wsl wsl2 hosts ip address- 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
wsl2host
(Ready for review)
- 1
- 2
- 3
0.3.5.20240423 | Updated: 23 Apr 2024
- 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:
78
Downloads of v 0.3.5.20240423:
10
Published:
23 Apr 2024
Maintainer(s):
Software Author(s):
- Shayne Sweeney
wsl2host 0.3.5.20240423
(Ready for review)
- 1
- 2
- 3
All Checks are Passing
3 Passing Tests
This version is in moderation and has not yet been approved. This means it doesn't show up under normal search.
- Until approved, you should consider this package version unsafe - it could do very bad things to your system (it probably doesn't but you have been warned, that's why we have moderation).
- This package version can change wildly over the course of moderation until it is approved. If you install it and it later has changes to this version, you will be out of sync with any changes that have been made to the package. Until approved, you should consider that this package version doesn't even exist.
- You cannot install this package under normal scenarios. See How to install package version under moderation for more information.
- There are also no guarantees that it will be approved.
There are versions of this package awaiting moderation (possibly just this one). See the Version History section below.
A workaround for accessing the WSL2 VM from the Windows host.
This program installs as a service and runs under the local user account. It automatically updates your Windows hosts file with the WSL2 VM's IP address.
MIT License
Copyright (c) 2019-2020 Shayne Sweeney and contributers
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.
The application has been downloaded from the official distribution and can
be verified by:
1. Go to the binary distribution page
https://github.com/shayne/go-wsl2-host/releases
and download the installer wsl2host.exe
using the links in the relevant assets section of the page.
Alternatively the installers can be downloaded directly from
URL64: https://github.com/shayne/go-wsl2-host/releases/download/v0.3.5/wsl2host.exe
2. The installer can be validated by comparing checksums
- Use powershell function 'Get-Filehash' - Get-Filehash -Algorithm sha256 wsl2host.exe
- Use chocolatey utility 'checksum.exe' - checksum -t sha256 -f wsl2host.exe
File64: wsl2host.exe
Type64: sha256
Checksum64: 619581883D5D58436BE954417EF4B9F12F0B89BE4F06C4D023556E64FEBE2094
Contents of file LICENSE.txt is obtained from https://raw.githubusercontent.com/shayne/go-wsl2-host/main/LICENSE
$toolsDir = "$(Split-Path -Parent $MyInvocation.MyCommand.Definition)"
$binaryLocation = "$(Get-ToolsLocation)\wsl2host"
. $toolsDir\Uninstall-ChocolateyPath.ps1
Remove-Item `
-Path $binaryLocation `
-Recurse -Force
Uninstall-ChocolateyPath `
-PathToUninstall $binaryLocation
# Copyright 2011 - Present RealDimensions Software, LLC
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
function Uninstall-ChocolateyPath {
<#
.SYNOPSIS
**NOTE:** Administrative Access Required when `-PathType 'Machine'.`
This puts a directory to the PATH environment variable of the
requested scope (Machine or User).
.DESCRIPTION
Removes path from target path scope. Removes multiple occurances (if they exist)
and all occurances with or without a trailing slash.
.NOTES
This command will assert UAC/Admin privileges on the machine if
`-PathType 'Machine'`.
This is used when the application/tool is not being linked by Chocolatey
(not in the lib folder).
.INPUTS
None
.OUTPUTS
None
.PARAMETER PathToUninstall
The full path to a location to remove from the PATH.
.PARAMETER PathType
Which PATH to remove it from. If specifying `Machine`, this requires admin
privileges to run correctly.
.PARAMETER IgnoredArguments
Allows splatting with arguments that do not apply. Do not use directly.
.EXAMPLE
Uninstall-ChocolateyPath -PathToUninstall "$($env:SystemDrive)\tools\gittfs"
.EXAMPLE
Uninstall-ChocolateyPath "$($env:SystemDrive)\Program Files\MySQL\MySQL Server 5.5\bin" -PathType 'Machine'
.LINK
Install-ChocolateyPath
.LINK
Install-ChocolateyEnvironmentVariable
.LINK
Get-EnvironmentVariable
.LINK
Set-EnvironmentVariable
.LINK
Get-ToolsLocation
#>
param(
[parameter(Mandatory=$true, Position=0)][alias("Path")][string] $PathToUninstall,
[parameter(Mandatory=$false, Position=1)][ValidateSet('User','Machine','All')][alias("Scope")][String] $pathType = 'User',
[parameter(Mandatory=$false)][switch] $RecursiveCall,
[parameter(ValueFromRemainingArguments = $true)][Object[]] $ignoredArguments
)
Write-Debug "Running 'Uninstall-ChocolateyPath' with PathToUninstall:`'$PathToUninstall`'";
If (!$RecursiveCall -AND ($pathType -ine 'All')) {Write-Host "Only evaluating and updating path scope `"$pathType`", path will not be assessed nor removed for other scope, so path may exist in other scope as well."}
$originalPathToUninstall = $PathToUninstall
#First half on handling trailing slash properly - remove it from requested path:
$PathToUninstall = $PathToUninstall.trimend('\')
#array drops blanks (one of which is always created by final semi-colon)
$actualPathArrayUser = (Get-EnvironmentVariable -Name 'Path' -Scope 'user' -PreserveVariables).split(';',[System.StringSplitOptions]::RemoveEmptyEntries)
$actualPathArrayMachine = (Get-EnvironmentVariable -Name 'Path' -Scope 'machine' -PreserveVariables).split(';',[System.StringSplitOptions]::RemoveEmptyEntries)
$PathFoundInMachine = $PathFoundInUser = $False
If (($actualpathArrayMachine -icontains "$($PathToUninstall.ToLower())") -OR ($actualpathArrayMachine -icontains "$(($PathToUninstall + '\').ToLower())"))
{
$PathFoundInMachine = $True
}
If (($actualpathArrayUser -icontains "$($PathToUninstall.ToLower())") -OR ($actualpathArrayUser -icontains "$(($PathToUninstall + '\').ToLower())"))
{
$PathFoundInUser = $True
}
#Process machine first to minimize suppression of messaging when recursion is necessary to process machine path
If ($PathFoundInMachine)
{
If (!$RecursiveCall) {Write-Host "Target path `"$PathToUninstall`" exists in Machine scope..."}
If ($pathType -ieq 'User' -AND ($pathType -ine 'All'))
{
If (!$RecursiveCall) {Write-Host "`"$PathToUninstall`" will only be removed from Machine scope per your request. Use -PathType 'User' to remove only from Machine scope or -PathType 'All' to remove from all scopes."}
}
If (($pathType -ieq 'Machine') -OR ($pathType -ieq 'All'))
{
If (!$RecursiveCall) {Write-Host "PATH environment variable for scope `"Machine`" contains `"$PathToUninstall`". Removing..."}
$actualpathArray = $actualPathArrayMachine
[string[]]$Newpatharray = $null
foreach ($path in $actualpathArray)
{
#second half of handling trailing slash properly - compare to both options in target path
If (($path -ine "$PathToUninstall") -AND ($path -ine "$($PathToUninstall)\"))
{
[string[]]$Newpatharray += "$path"
}
}
$actualPath = ($Newpatharray -join(';')) + ';'
if (Test-ProcessAdminRights)
{
Set-EnvironmentVariable -Name 'Path' -Value $actualPath -Scope 'Machine'
}
ElseIf (!$RecursiveCall)
{
$psArgs = "Uninstall-ChocolateyPath -PathToUninstall `'$originalPathToUninstall`' -pathType `'Machine`' -RecursiveCall"
Start-ChocolateyProcessAsAdmin "$psArgs"
If ($RecursiveCall) {Return}
}
Else
{
Throw "Did not gain admin rights on the recursive call, exiting to avoid going into recursive loop."
}
}
}
If ($PathFoundInUser)
{
Write-Host "Target path `"$PathToUninstall`" exists in User scope..."
If ($pathType -ine 'Machine' -AND ($pathType -ine 'All'))
{
Write-Host "`"$PathToUninstall`" will only be removed from User scope per your request. Use -PathType 'Machine' to remove only from Machine scope or -PathType 'All' to remove from all scopes."
}
If (($pathType -ieq 'User') -OR ($pathType -ieq 'All'))
{
Write-Host "PATH environment variable for scope `"User`" contains `"$PathToUninstall`". Removing..."
$actualpathArray = $actualPathArrayUser
[string[]]$Newpatharray = $null
foreach ($path in $actualpathArray)
{
#second half of handling trailing slash properly - compare to both options in target path
If (($path -ine "$PathToUninstall") -AND ($path -ine "$($PathToUninstall)\"))
{
[string[]]$Newpatharray += "$path"
}
}
$actualPath = ($Newpatharray -join(';')) + ';'
Set-EnvironmentVariable -Name 'Path' -Value $actualPath -Scope 'User'
}
}
If ($PathFoundInUser -OR $PathFoundInMachine)
{
Write-Host "Updating environment for current process"
Update-SessionEnvironment
}
Else
{
Write-Host "`"$PathToUninstall`" was not found in requested scope `"$PathType`". Nothing to do..."
}
}
Log in or click on link to see number of positives.
- wsl2host.exe (619581883d5d) - ## / 70
- wsl2host.0.3.5.20240423.nupkg (db94c4d33898) - ## / 64
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 |
---|---|---|---|---|
wsl2host 0.3.5.20240423 | 10 | Tuesday, April 23, 2024 | Ready | |
wsl2host 0.3.5 | 68 | Wednesday, February 21, 2024 | Approved |
Copyright 2019 shayne
-
- chocolatey-core.extension (≥ 1.3.3)
Ground Rules:
- This discussion is only about wsl2host and the wsl2host 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 wsl2host, 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.
ponces (maintainer) on 23 Apr 2024 23:47:52 +00:00:
User 'ponces' (maintainer) submitted package.
chocolatey-ops (reviewer) on 24 Apr 2024 00:22:14 +00:00:
wsl2host has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
Suggestions
Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.
chocolatey-ops (reviewer) on 24 Apr 2024 01:28:30 +00:00:
wsl2host has passed automated package testing (verification). The next step in the process is package scanning.
Please visit https://gist.github.com/choco-bot/b479e92ea41b1921e106b50e5c599841 for details.
This is an FYI only. There is no action you need to take.
chocolatey-ops (reviewer) on 24 Apr 2024 05:12:27 +00:00:
wsl2host has passed automated virus scanning.