Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Security Apps
Other security for Windows, Mac, Linux
Data encryption software: CPPcryptfs
Message
<blockquote data-quote="chetuyet.hp" data-source="post: 1061993" data-attributes="member: 97954"><p>cppcryptfs is based on the design of <a href="https://github.com/rfjakob/gocryptfs" target="_blank">gocryptfs</a>, an encrypted overlay filesystem written in Go.</p><p></p><p>cppcryptfs is an implementation of the gocryptfs filesystem in C++ for Windows. cppcryptfs is compatible with gocryptfs. Filesystems created with one can generally be mounted (and synced) with the other. Please see the statement on compatibility near the end of this document.</p><p></p><p>cppcrypts provides on-the-fly, at-rest and in-the-cloud encryption of files and file names in a virtual filesystem. It uses the <a href="https://github.com/dokan-dev/dokany" target="_blank">Dokany</a> driver and library to provide a virtual filesystem in user mode under Windows.</p><p></p><p><strong>IMPORTANT</strong>: As per <a href="https://github.com/rfjakob/gocryptfs/issues/50" target="_blank">this</a> discussion, you should only store the created gocryptfs.conf in the cloud if your password is strong. If an attacker obtains your gocryptfs.conf, then they will be able to throw whatever resources they have at a brute force attack on your encrypted password. Increasing scryptn will slow them down (see below) The developer keeps his gocryptfs.conf in the cloud and uses a very strong password.</p><p></p><p>You can use cppcryptfs to create an encrypted filesystem in a folder. The encrypted filesystem is protected with a password that you choose.</p><p></p><p>When you use cppcryptfs to mount the encrypted filesystem by providing the password, then you have a new drive letter in Windows. This virtual drive letter gives you an unencrypted view of your files. The encryption and decryption are done on the fly and are transparent to applications that use the files on that virtual drive.</p><p></p><p>After you tell cppcryptfs to dismount the virtual drive letter, then there is no way to get at your unencrypted data unless the filesystem is re-mounted again using your password.</p><p></p><p>Shutting down your computer automatically dismounts all cppcryptfs drive letters.</p><p></p><p>If the folder where the encrypted files are kept is being synced with a cloud service, then only the encrypted files with encrypted file names will be uploaded to the cloud service.</p><p></p><p>This way, neither the employees of the cloud service nor anybody who hacks into the cloud service can use your files.</p><p></p><p>Also, if someone steals your computer and the encrypted filesystem is not mounted, then the thief cannot use your files.</p><p>[ATTACH=full]279297[/ATTACH]</p><p></p><p>Because the encryption is done on a per-file basis instead of using a container file to store the data, you do not have to decide ahead of time how much encrypted storage you will need. cppcryptfs has very minimal storage overhead, and your encrypted filesystem can grow dynamically limited only by the amount of free space on the physical drive on which the encrypted filesystem is located.</p><p></p><p>Another advantage of per-file encryption over container-based encryption is that per-file encryption syncs very quickly and efficiently with cloud-based services.</p><p>Link. <a href="https://github.com/bailey27/cppcryptfs" target="_blank">GitHub - bailey27/cppcryptfs: cppcryptfs is an implementation of the gocryptfs encrypted overlay filesystem in C++ for Windows.</a></p></blockquote><p></p>
[QUOTE="chetuyet.hp, post: 1061993, member: 97954"] cppcryptfs is based on the design of [URL='https://github.com/rfjakob/gocryptfs']gocryptfs[/URL], an encrypted overlay filesystem written in Go. cppcryptfs is an implementation of the gocryptfs filesystem in C++ for Windows. cppcryptfs is compatible with gocryptfs. Filesystems created with one can generally be mounted (and synced) with the other. Please see the statement on compatibility near the end of this document. cppcrypts provides on-the-fly, at-rest and in-the-cloud encryption of files and file names in a virtual filesystem. It uses the [URL='https://github.com/dokan-dev/dokany']Dokany[/URL] driver and library to provide a virtual filesystem in user mode under Windows. [B]IMPORTANT[/B]: As per [URL='https://github.com/rfjakob/gocryptfs/issues/50']this[/URL] discussion, you should only store the created gocryptfs.conf in the cloud if your password is strong. If an attacker obtains your gocryptfs.conf, then they will be able to throw whatever resources they have at a brute force attack on your encrypted password. Increasing scryptn will slow them down (see below) The developer keeps his gocryptfs.conf in the cloud and uses a very strong password. You can use cppcryptfs to create an encrypted filesystem in a folder. The encrypted filesystem is protected with a password that you choose. When you use cppcryptfs to mount the encrypted filesystem by providing the password, then you have a new drive letter in Windows. This virtual drive letter gives you an unencrypted view of your files. The encryption and decryption are done on the fly and are transparent to applications that use the files on that virtual drive. After you tell cppcryptfs to dismount the virtual drive letter, then there is no way to get at your unencrypted data unless the filesystem is re-mounted again using your password. Shutting down your computer automatically dismounts all cppcryptfs drive letters. If the folder where the encrypted files are kept is being synced with a cloud service, then only the encrypted files with encrypted file names will be uploaded to the cloud service. This way, neither the employees of the cloud service nor anybody who hacks into the cloud service can use your files. Also, if someone steals your computer and the encrypted filesystem is not mounted, then the thief cannot use your files. [ATTACH type="full" alt="screenshot_create.png"]279297[/ATTACH] Because the encryption is done on a per-file basis instead of using a container file to store the data, you do not have to decide ahead of time how much encrypted storage you will need. cppcryptfs has very minimal storage overhead, and your encrypted filesystem can grow dynamically limited only by the amount of free space on the physical drive on which the encrypted filesystem is located. Another advantage of per-file encryption over container-based encryption is that per-file encryption syncs very quickly and efficiently with cloud-based services. Link. [URL="https://github.com/bailey27/cppcryptfs"]GitHub - bailey27/cppcryptfs: cppcryptfs is an implementation of the gocryptfs encrypted overlay filesystem in C++ for Windows.[/URL] [/QUOTE]
Insert quotes…
Verification
Post reply
Top