Notices: This section not yet converted to new layout. Download stats are rolling back out.

Tor Browser Bundle

Package test results have failed.

This package was rejected on 6/11/2019. The reviewer chocolatey-ops has listed the following reason(s):

chocolatey (maintainer) on 07 May 2019 00:09:57 +00:00:

User 'chocolatey' (maintainer) submitted package.

chocolatey-ops (reviewer) on 07 May 2019 00:44:35 +00:00:

tor-browser 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.

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.

  • The nuspec has been enhanced to allow more information related to the software. More... Please consider adding one or more of the following to the nuspec, if available:

    • docsUrl - points to the location of the wiki or docs of the software

    • mailingListUrl - points to the forum or email list group for the software

    • bugTrackerUrl - points to the location where issues and tickets can be accessed

    • projectSourceUrl - points to the location of the underlying software source

chocolatey-ops (reviewer) on 07 May 2019 06:22:55 +00:00:

tor-browser has failed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/7350003049d0bf45f84b1162c9a1f71a for details.
The package status will be changed and will be waiting on your next actions.

  • NEW! We have a test environment for you to replicate the testing we do. This can be used at any time to test packages! See https://github.com/chocolatey/chocolatey-test-environment
  • Please log in and leave a review comment if you have questions and/or comments.
  • If you see the verifier needs to rerun testing against the package without resubmitting (a issue in the test results), you can do that on the package page in the review section.
  • If the verifier is incompatible with the package, please log in and leave a review comment if the package needs to bypass testing (e.g. package installs specific drivers).
  • Automated testing can also fail when a package is not completely silent or has pop ups (AutoHotKey can assist - a great example is the VeraCrypt package).
  • A package that cannot be made completely unattended should have the notSilent tag. Note that this must be approved by moderators.

chocolatey-ops (reviewer) on 27 May 2019 06:23:44 +00:00:

We've found tor-browser v8.0.9 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.

Take action:
* Log in to the site and respond to the review comments.
* Resubmit fixes for this version.
* If the package version is failing automated checks, you can self-reject the package.

If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.

Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.

chocolatey-ops (reviewer) on 11 Jun 2019 06:28:24 +00:00:

Unfortunately there has not been progress to move tor-browser v8.0.9 towards an approved status within 15 days after the last review message, so we need to close (reject) the package version at this time. If you want to pick this version up and move it towards approval in the future, use the contact site admins link on the package page and we can move it back into a submitted status so you can submit updates.

Status Change - Changed status of package from 'submitted' to 'rejected'.


The Tor software protects you by bouncing your communications around a distributed network of relays run by volunteers all around the world: it prevents somebody watching your Internet connection from learning what sites you visit, it prevents the sites you visit from learning your physical location, and it lets you access sites which are blocked.

The Tor Browser Bundle lets you use Tor on Windows without needing to install any software. It comes with a pre-configured web browser to protect your anonymity, and is self-contained.

This package puts the Tor Browser Bundle into $env:ChocolateyBinRoot\tor-browser.

Files

Hide
  • tools\chocolateyInstall.ps1 Show
    $ErrorActionPreference = 'Stop'
    
    $toolsDir = Split-Path -Parent $MyInvocation.MyCommand.Definition
    . "$toolsDir\helpers.ps1"
    
    $data = GetDownloadInformation -toolsPath $toolsDir
    $destinationFolder = GetInstallDirectory -toolsPath $toolsDir
    
    $packageArgs = @{
      PackageName = 'tor-browser'
      FileFullPath = Join-Path $env:TEMP "tor-browserInstall.exe"
      Url = $data.URL
      Checksum = $data.Checksum
      ChecksumType = 'sha256'
    }
    
    Get-ChocolateyWebFile @packageArgs
    
    Write-Output "Installing $($packageArgs.PackageName) with language code: '$($data.Locale)'..."
    
    Start-Process -Wait $packageArgs.FileFullPath -ArgumentList '/S', "/D=$destinationFolder"
    
    Remove-Item  $packageArgs.FileFullPath -Force -ea 0
    
    # Create .ignore files for exe’s
    Get-ChildItem -Path $destinationFolder -Recurse | Where-Object {
      $_.Extension -eq '.exe'} | ForEach-Object {
      New-Item $($_.FullName + '.ignore') -Force -ItemType file
    # Suppress output of New-Item
    } | Out-Null
    
    $desktop = [System.Environment]::GetFolderPath('Desktop')
    
    Install-ChocolateyShortcut `
      -ShortcutFilePath "$desktop\Tor Browser.lnk" `
      -TargetPath "$toolsDir\tor-browser\Browser\firefox.exe" `
      -WorkingDirectory "$toolsDir\tor-browser\Browser"
    
    # set NTFS modify file permissions to $toolsDir\tor-browser\ for user account that installed the package
    $WhoAmI=whoami
    $Acl = Get-Acl "$toolsDir\tor-browser"
    $Ar = New-Object  system.security.accesscontrol.filesystemaccessrule($WhoAmI,"Modify",'ContainerInherit,ObjectInherit', 'None', "Allow")
    $Acl.SetAccessRule($Ar)
    Set-Acl "$toolsDir\tor-browser" $Acl
    
  • tools\chocolateyUninstall.ps1 Show
    $ErrorActionPreference = 'Stop'
    
    $desktop = [System.Environment]::GetFolderPath('Desktop')
    
    if (Test-Path "$desktop\Tor Browser.lnk") {
      Write-Host "Removing Desktop shortcut..."
      Remove-Item -Force -ea 0 "$desktop\Tor Browser.lnk"
    }
    
  • tools\helpers.ps1 Show
    function GetDownloadsData() {
      param($filePath)
    
      $data = Get-Content $filePath | ConvertFrom-Csv -Delimiter '|'
      return $data
    }
    
    function GetLocaleData() {
      param($downloadData)
    
      $availableLocales = $downloadData | Select-Object -expand Locale
    
      $pp = Get-PackageParameters
      $preferredLocale = if ($pp.Locale) { $pp.Locale } else { (Get-Culture).Name }
      $twoLetterLocale = (Get-Culture).TwoLetterISOLanguageName
      $fallbackLocale = 'en-US'
    
      $locales = $preferredLocale,$twoLetterLocale,$fallbackLocale
    
      foreach ($locale in $locales) {
        $localeMatch = $availableLocales | Where-Object { $_ -eq $locale } | Select-Object -first 1
        if (!$localeMatch -and $locale -ne $null -and $locale.Count -eq 2) {
          $localeMatch = $availableLocales | Where-Object { ($_ -split '-' | Select-Object -first 1) -eq $locale } | Select-Object -first 1
        }
        if ($localeMatch -and $locale -ne $null) { break }
      }
    
      return $downloadData | Where-Object { $_.Locale -eq $locale } | Select-Object -first 1
    }
    
    function GetDownloadInformation() {
      param($toolsPath)
      $dlData = GetDownloadsData "$toolsPath\LanguageChecksums.csv"
      if (!$dlData) { throw "No URLs is available to download from!" }
      $locale = GetLocaleData $dlData
      return $locale
    }
    
    function GetInstallDirectory() {
      param($toolsPath)
    
      $pp = Get-PackageParameters
      if ($pp.InstallDir) { return $pp.InstallDir }
    
      $binRoot = Get-ToolsLocation
      $destinationFolder = Join-Path $binRoot "tor-browser"
    
      if (!(Test-Path $destinationFolder)) {
        $destinationFolder = Join-Path $toolsPath "tor-browser"
      } else {
        Write-Warning @(
          'Deprecated installation folder detected (binRoot). ' +
          'This package will continue to install tor-browser there ' +
          'unless you manually remove it from "' + $destinationFolder + '".'
        )
      }
    
      $desktopPath = [System.Environment]::GetFolderPath('Desktop')
      $oldDestinationFolder = Join-Path $desktopPath 'Tor-Browser'
      if ((Test-Path $oldDestinationFolder) -and
          ($oldDestinationFolder -ne $destinationFolder)) {
        $destinationFolder = $oldDestinationFolder
    
        Write-Warning @(
          'Deprecated installation fodler detected: Desktop/Tor-Browser. ' +
          'This package will continue to install tor-browser there unless you ' +
          'remove the deprecated installation folder. After your did that, reinstall ' +
          'this package again with the "--force" parameter. Then it will be installed ' +
          'to the package tools directory.'
        )
      }
    
      return $destinationFolder
    }
    
  • tools\LanguageChecksums.csv

Virus Scan Results

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.

Dependencies

Package Maintainer(s)

Software Author(s)

  • Tor Project

Tags

Release Notes

https://blog.torproject.org/category/tags/tor-browser

Version History

Version Downloads Last updated Status
Tor Browser Bundle 8.5.2 766 Thursday, June 20, 2019 approved
Tor Browser Bundle 8.5.1 2894 Tuesday, June 4, 2019 approved
Tor Browser Bundle 8.5 2536 Thursday, May 23, 2019 approved
Tor Browser Bundle 8.0.8 5688 Saturday, March 23, 2019 approved
Tor Browser Bundle 8.0.7 932 Tuesday, March 19, 2019 approved
Tor Browser Bundle 8.0.6 3453 Wednesday, February 13, 2019 approved
Tor Browser Bundle 8.0.5 2008 Wednesday, January 30, 2019 approved
Tor Browser Bundle 8.0.4 4108 Tuesday, December 11, 2018 approved
Show More

Discussion for the Tor Browser Bundle Package

Ground rules:

  • This discussion is only about Tor Browser Bundle and the Tor Browser Bundle 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 Tor Browser Bundle, 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
Chocolatey.org uses cookies to enhance the user experience of the site.
Ok