Downloads:

4,341

Downloads of v 1.10.2:

494

Last Update:

27 Jan 2020

Package Maintainer(s):

Software Author(s):

  • jetwhiz
  • freddy77

Tags:

encfs4win driver encfs encryption foss file-system

encfs4win

1.10.2 | Updated: 27 Jan 2020

Downloads:

4,341

Downloads of v 1.10.2:

494

Software Author(s):

  • jetwhiz
  • freddy77

encfs4win 1.10.2

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

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

>

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

>

To uninstall encfs4win, 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 encfs4win -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 encfs4win -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 encfs4win installed
  win_chocolatey:
    name: encfs4win
    state: present
    version: 1.10.2
    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 'encfs4win' do
  action    :install
  version  '1.10.2'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: encfs4win,
    Version: 1.10.2,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller encfs4win
{
   Name     = 'encfs4win'
   Ensure   = 'Present'
   Version  = '1.10.2'
   Source   = 'STEP 3 URL'
}

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


package { 'encfs4win':
  provider => 'chocolatey',
  ensure   => '1.10.2',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install encfs4win version="1.10.2" 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 was approved as a trusted package on 27 Jan 2020.

Description

EncFS encrypts individual files, by translating all requests for the virtual EncFS filesystem into the equivalent encrypted operations on the raw filesystem.

A GUI for encfs4win is available through encfsw, providing a tray icon that makes mounting and unmounting encrypted partitions even easier!

EncFS provides an encrypted filesystem in user-space, using the Dokan library for the filesystem interface. EncFS is open source software, licensed under the LGPL.

Notes

  • This package will require to be reinstalled after the restart of the OS if its dependency installation is required.

legal\LICENSE.txt

The code comprising the EncFS library (libencfs) is licensed under the LGPL.
The main programs (encfs, encfsctl, etc) are licensed under the GPL.

For details of the licenses, see COPYING.LGPL and COPYING.GPL.

===========================================================================

The following 3rd party libraries are included in the EncFS source release
from github:

* easylogging++ : a logging library, which is supplied with the following license

  The MIT License (MIT)

  Copyright (c) 2015 muflihun.com

  https://github.com/easylogging/easyloggingpp
  http://easylogging.muflihun.com
  http://muflihun.com

  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.


* tinyxml2 : an XML reader / writer, which is supplied with the following license:

  TinyXML-2 is released under the zlib license:

  This software is provided 'as-is', without any express or implied
  warranty. In no event will the authors be held liable for any
  damages arising from the use of this software.

  Permission is granted to anyone to use this software for any
  purpose, including commercial applications, and to alter it and
  redistribute it freely, subject to the following restrictions:

  1. The origin of this software must not be misrepresented; you must
  not claim that you wrote the original software. If you use this
  software in a product, an acknowledgment in the product documentation
  would be appreciated but is not required.
  2. Altered source versions must be plainly marked as such, and
  must not be misrepresented as being the original software.
  3. This notice may not be removed or altered from any source
  distribution.
legal\VERIFICATION.txt
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

The embedded software have been downloaded from the listed download
location on <https://github.com/jetwhiz/encfs4win/releases>
and can be verified by doing the following:

1. Download the following <https://github.com/jetwhiz/encfs4win/releases/download/v1.10.2/encfs-installer.exe>
2. Get the checksum using one of the following methods:
  - Using powershell function 'Get-FileHash'
  - Use chocolatey utility 'checksum.exe'
3. The checksums should match the following:

  checksum type: sha256
  checksum: 43AF6E27C36FD8E9E3DF913D157D72A148349D723726961C55F9A81055913A37

The file 'LICENSE.txt' has been obtained from <https://github.com/jetwhiz/encfs4win/blob/21bd66bddf75fb7bda018a52d51a42ff8b24348a/COPYING>
tools\chocolateyInstall.ps1
$ErrorActionPreference = 'Stop'

$toolsPath = Split-Path -parent $MyInvocation.MyCommand.Definition

$packageArgs = @{
  packageName    = $env:ChocolateyPackageName
  fileType       = 'exe'
  file           = "$toolsPath\encfs-installer.exe"
  softwareName   = 'encfs4win*'
  silentArgs     = '/S'
  validExitCodes = @(0)
}

Install-ChocolateyInstallPackage @packageArgs

Get-ChildItem $toolsPath\*.exe | ForEach-Object { Remove-Item $_ -ea 0; if (Test-Path $_) { Set-Content "$_.ignore" '' } }

$packageName = $packageArgs.packageName
$installLocation = Get-AppInstallLocation $packageName
if ($installLocation) {
  Write-Host "$packageName installed to '$installLocation'"
  Register-Application "$installLocation\encfsw.exe"
  Write-Host "$packageName tray application registered as encfsw"
  Install-BinFile encfs "$installLocation\encfs.exe"

  Write-Host 'OS restart might be required'
}
else { Write-Warning "Can't find $PackageName install location" }
tools\chocolateyUninstall.ps1
$ErrorActionPreference = 'Stop'

$packageArgs = @{
  packageName    = $env:ChocolateyPackageName
  softwareName   = 'encfs4win*'
  fileType       = 'exe'
  silentArgs     = '/S'
  validExitCodes = @(@(0))
}

$uninstalled = $false

[array]$key = Get-UninstallRegistryKey @packageArgs

if ($key.Count -eq 1) {
  $key | ForEach-Object {
    $packageArgs['file'] = "$($_.UninstallString)"

    Uninstall-ChocolateyPackage @packageArgs
  }
}
elseif ($key.Count -eq 0) {
  Write-Warning "$packageName has already been uninstalled by other means."
}
elseif ($key.Count -gt 1) {
  Write-Warning "$($key.Count) matches found!"
  Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
  Write-Warning "Please alert the package maintainer that the following keys were matched:"
  $key | ForEach-Object { Write-Warning "- $($_.DisplayName)" }
}
tools\encfs-installer.exe
md5: 4B162A6E9E82B3FD7DDBCF67C1C7D030 | sha1: CCE6BD0C604CA94D9C5441E9A1108125787D66F4 | sha256: 43AF6E27C36FD8E9E3DF913D157D72A148349D723726961C55F9A81055913A37 | sha512: 3C6901ED8E2CD2A88BAF581AD4E825C89C2832421C5EF1376D87651307EF3D5C844C9D1AAC743EDE580EBC242EA006F0BD74173FF9D39DB4E8570AF8509C6F29

Log in or click on link to see number of positives.

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
encfs4win 1.11.0-beta2 196 Monday, January 27, 2020 Approved
encfs4win 1.11.0-beta1 200 Sunday, May 5, 2019 Approved
encfs4win 1.10.1 266 Sunday, May 5, 2019 Approved
encfs4win 1.10.1-RC15 142 Monday, April 8, 2019 Approved
encfs4win 1.10.1-RC14 210 Monday, January 21, 2019 Approved
encfs4win 1.10.1-RC13 357 Monday, March 12, 2018 Approved
encfs4win 1.10.1-RC12-20180213 248 Tuesday, February 13, 2018 Approved
encfs4win 1.10.1-RC12 327 Sunday, August 27, 2017 Approved
encfs4win 1.10.1-RC11 361 Wednesday, March 15, 2017 Approved

Discussion for the encfs4win Package

Ground Rules:

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