Downloads:

78,355

Downloads of v 4.6:

451

Last Update:

11/23/2014

Package Maintainer(s):

Software Author(s):

  • David V. Kocher
  • Yves Langisch

Tags:

cloud storage file-browser

Cyberduck

This is not the latest version of Cyberduck available.

4.6 | Updated: 11/23/2014

Downloads:

78,355

Downloads of v 4.6:

451

Maintainer(s):

Software Author(s):

  • David V. Kocher
  • Yves Langisch

Cyberduck 4.6

This is not the latest version of Cyberduck available.

All Checks are Unknown

2 Test of Unknown Status


Validation Testing Unknown


Verification Testing Unknown

To install Cyberduck, run the following command from the command line or from PowerShell:

>

To upgrade Cyberduck, run the following command from the command line or from PowerShell:

>

To uninstall Cyberduck, run the following command from the command line or from PowerShell:

>

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

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • 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://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. Enter your internal repository url

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

4. Choose your deployment method:


choco upgrade cyberduck -y --source="'STEP 3 URL'" [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 cyberduck -y --source="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Ensure cyberduck installed
  win_chocolatey:
    name: cyberduck
    state: present
    version: 4.6
    source: STEP 3 URL

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

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'cyberduck' do
  action    :install
  version  '4.6'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: cyberduck,
    Version: 4.6,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller cyberduck
{
   Name     = 'cyberduck'
   Ensure   = 'Present'
   Version  = '4.6'
   Source   = 'STEP 3 URL'
}

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


package { 'cyberduck':
  provider => 'chocolatey',
  ensure   => '4.6',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install cyberduck version="4.6" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.

  • Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
  • Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
  • Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.

Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.

This package was approved by moderator ferventcoder on 11/27/2014.

Description

Connect to every server. With an easy to use interface, connect to FTP (File Transfer Protocol), SFTP (SSH Secure File Transfer), WebDAV (Web-based Distributed Authoring and Versioning), Amazon S3, Google Cloud Storage and Rackspace Cloud Files.


tools\chocolateyInstall.ps1
#Install-VirtualPackage 'cyberduck.install'
tools\chocolateyUninstall.ps1
# Uninstall executable = Nullsoft Install System v2.46

$silentArgs = "/S"
$processor = Get-WmiObject Win32_Processor
$is64bit = $processor.AddressWidth -eq 64

if ($is64bit) {
	$packageName = "Cyberduck"
	$uninstallString = (Get-ItemProperty HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\* | select DisplayName, UninstallString | Where-Object {$_.DisplayName -like "$packageName*"}).UninstallString
} else {
	$packageName = "Cyberduck"
	$uninstallString = (Get-ItemProperty HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\* | select DisplayName, UninstallString | Where-Object {$_.DisplayName -like "$packageName*"}).UninstallString
}

$uninstallString = "$uninstallString" -replace '[{]', '`{'
$uninstallString = "$uninstallString" -replace '[}]', '`}'

if ($uninstallString -ne "") {
     & $uninstallString $silentArgs;
}

try {
    $packageName = "cyberduck" 
    Uninstall-ChocolateyPackage $packageName
    Write-ChocolateySuccess $packageName
} catch {
    Write-ChocolateyFailure $packageName $($_.Exception.Message)
    throw
}

try {
    $packageName = "cyberduck.install"
    Uninstall-ChocolateyPackage $packageName
    Write-ChocolateySuccess $packageName
} catch {
    Write-ChocolateyFailure $packageName $($_.Exception.Message)
    throw
}

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.

Version Downloads Last Updated Status
Cyberduck 7.1.1.31577 993 Tuesday, October 8, 2019 Approved
Cyberduck 7.1.0.31395 14641 Wednesday, September 11, 2019 Approved
Cyberduck 7.0.2.30998 1756 Wednesday, July 24, 2019 Approved
Cyberduck 7.0.1.30930 1302 Tuesday, June 25, 2019 Approved
Cyberduck 7.0.0.30869 1002 Wednesday, June 5, 2019 Approved
Cyberduck 6.9.4.30164 4160 Wednesday, February 27, 2019 Approved
Cyberduck 6.9.3.30061 719 Friday, February 15, 2019 Approved
Cyberduck 6.9.0.29768 1105 Wednesday, January 16, 2019 Approved
Cyberduck 6.8.3.29107 1682 Thursday, November 1, 2018 Approved
Discussion for the Cyberduck Package

Ground Rules:

  • This discussion is only about Cyberduck and the Cyberduck 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 Cyberduck, 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