Linux/gocryptfs: Difference between revisions

From Wiki
No edit summary
No edit summary
 
(5 intermediate revisions by the same user not shown)
Line 2: Line 2:
* files are always encrypted, become decrypted when mounting
* files are always encrypted, become decrypted when mounting


 
<blockquote>
 
<pre>
mkdir encrypteddir
mkdir plaindir
gocryptfs --init encrypteddir
gocryptfs encrypteddir plaindir       
fusermount -u plaindir   
</pre>
</blockquote>




Line 9: Line 16:
* files are always decrypted, become encrypted when mounting
* files are always decrypted, become encrypted when mounting
* good for cloud backup syncing
* good for cloud backup syncing
 
<blockquote>
<pre>
mkdir /home/joe.crypt
gocryptfs -init -reverse /home/joe
gocryptfs -reverse /home/joe /home/joe.crypt
fusermount -u plain 
-> then rsync/rclone /home/joe.crypt to insecure cloud storage
</pre>
</blockquote>


[[Category:Linux/System]]
[[Category:Linux/System]]
[[Category:Linux]]
[[Category:Linux]]

Latest revision as of 12:22, 22 December 2017

Forward mode

  • files are always encrypted, become decrypted when mounting
mkdir encrypteddir
mkdir plaindir
gocryptfs --init encrypteddir
gocryptfs encrypteddir plaindir        
fusermount -u plaindir     


reverse mode

  • files are always decrypted, become encrypted when mounting
  • good for cloud backup syncing
mkdir /home/joe.crypt
gocryptfs -init -reverse /home/joe
gocryptfs -reverse /home/joe /home/joe.crypt
fusermount -u plain   
-> then rsync/rclone /home/joe.crypt to insecure cloud storage