Downloads of v 0.11.1:


Last Update:

19 Mar 2021

Package Maintainer(s):

Software Author(s):

  • Siyuan Ren


securefs encryption file-encryption security filesystem


  • 1
  • 2
  • 3

0.11.1 | Updated: 19 Mar 2021



Downloads of v 0.11.1:



Software Author(s):

  • Siyuan Ren

  • 1
  • 2
  • 3
SecureFS 0.11.1

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files


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


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


To uninstall SecureFS, 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 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

4. Choose your deployment method:

choco upgrade securefs -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 securefs -y --source="'STEP 3 URL'"

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

Exit $exitCode

- name: Ensure securefs installed
    name: securefs
    state: present
    version: 0.11.1
    source: STEP 3 URL

See docs at

chocolatey_package 'securefs' do
  action    :install
  version  '0.11.1'
  source   'STEP 3 URL'

See docs at

    Name: securefs,
    Version: 0.11.1,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller securefs
   Name     = 'securefs'
   Ensure   = 'Present'
   Version  = '0.11.1'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'securefs':
  provider => 'chocolatey',
  ensure   => '0.11.1',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install securefs version="0.11.1" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved by moderator TheCakeIsNaOH on 19 Mar 2021.


securefs is a filesystem in userspace (FUSE) with transparent encryption (when writing)
and decryption (when reading).

securefs mounts a regular directory onto a mount point. The mount point appears as a
regular filesystem, where one can read/write/create files, directories and symbolic links.
The underlying directory will be automatically updated to contain the encrypted and
authenticated contents.

$ErrorActionPreference = 'Stop';
$toolsDir              = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

#Remove old versions of securefs in the tools directory
Get-ChildItem -Path $toolsDir | Where-Object { $_.PSIsContainer } | Remove-Item -Recurse -Ea 0
$ErrorActionPreference = 'Stop'; # stop on all errors
$toolsDir              = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

$url64      = '' # 64bit URL here (HTTPS preferred) or remove - if installer contains both (very rare), use $url

$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  UnzipLocation = "$toolsDir\SecureFS"
  url64bit      = $url64
  softwareName  = 'securefs*'

  checksum64      = '2A76EB9FCC0FB9807162A156357CDA7263734C711669CDF37AAD11843CCBF67D3E5BCFAB000AFF8C7C8DB6866F981736A1C94BE6C24F31FFC543CE7DBF8E2C47'
  checksumType64  = 'sha512'

Install-ChocolateyZipPackage @packageArgs

Write-Output "$packageName installed to $toolsDir"

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

  • Key file support.
  • Unicode 13 support (for filename normalization).
  • Speed on network filesystem is improved.
  • File locking can now be disabled for improved performance, at the risk of data corruption.
  • New command line options --fsname and --fssubtype.
  • New command line option --normalization replaces the old --insensitive and --nfc.
  • The default number of rounds of scrypt are increased for better security.
  • Testing are improved. Not directly related to end users.

Discussion for the SecureFS Package

Ground Rules:

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