Downloads:

237

Downloads of v 1.0.3938.18045:

237

Last Update:

2/12/2018

Package Maintainer(s):

Software Author(s):

  • Peonefs

Tags:

peonefs fs vfs filesystem dokan

PeoneFS

1.0.3938.18045 | Updated: 2/12/2018

Downloads:

237

Downloads of v 1.0.3938.18045:

237

Maintainer(s):

Software Author(s):

  • Peonefs

PeoneFS 1.0.3938.18045

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

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

>

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

>

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

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


Chocolatey::Ensure-Package
(
    Name: peonefs,
    Version: 1.0.3938.18045,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller peonefs
{
   Name     = 'peonefs'
   Ensure   = 'Present'
   Version  = '1.0.3938.18045'
   Source   = 'STEP 3 URL'
}

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


package { 'peonefs':
  provider => 'chocolatey',
  ensure   => '1.0.3938.18045',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install peonefs version="1.0.3938.18045" 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.

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

This package was approved by moderator gep13 on 2/27/2018.

Description

The purpose of this project is to create a “file system” that represents an encrypted view of some other folders on the same machine. The idea is that in this way applications like offsite backup tools will always work with just the encrypted version of the data, so by the time the data leaves the machine there is no risk of exposing the actual files and folders. I started this project in order to create my own backup solution based upon rsync; unluckily there are not many ways to encrypt a file in such a way that is rsync friendly. Rsyncrypto is one of such tools but it has a few drawbacks: it only supports AES, it requires some file preprocessing (i.e. the backup tool must know that it needs to encrypt the file with it before handling it) and last but not least it is terribly slow on commodity hardware like modern Atom based machines. After discovering the existence of the Dokan library, which does the heavy lifting of writing the piping code necessary for developing a filter driver on Windows, I decided to write my own file system. In addition to [pseudo]encryption the file system does file/folder name obfuscation in order to make cryptoanalisys at least a little bit more difficult.


tools\chocolateyinstall.ps1
$packageArgs = @{
  packageName            = "$env:chocolateyPackageName"
  url                    = 'https://codeplexarchive.blob.core.windows.net/archive/projects/Peonefs/Peonefs.zip'
  checksum               = '32da77e32ca00a2939045cd97727beb178f558e736379aabccabab8cad2128a2'
  checksumType           = 'sha256'
  UnzipLocation          = "$env:TMP"
}
Install-ChocolateyZipPackage @packageArgs

$packageArgs = @{
  packageName            = "$env:chocolateyPackageName"
  Destination            = "$(Split-Path -Parent $MyInvocation.MyCommand.Definition)"
  FileFullPath           = "$env:TMP\releases\0\358fb1ff-94d1-4596-8316-234b62059649"
}
Get-ChocolateyUnzip @packageArgs

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

This package has no dependencies.

Discussion for the PeoneFS Package

Ground Rules:

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