Difference between revisions of "Encfs"
no edit summary
imported>Viking60 |
imported>Viking60 |
||
Line 60: | Line 60: | ||
encfs ~/.secret ~/secret | encfs ~/.secret ~/secret | ||
and enter the password. | and enter the password. | ||
This will mount secret as a disk you can do a simple | |||
df | |||
to check if '''secret''' is mounted | |||
==Encrypting Dropbox== | |||
One of the strong points of Encfs is that it does not reserve a lot of valuable space. This makes it suitable for encrypting Dropbox content. | |||
There is no such thing as 100% security in the cloud, so remember that some things simply do not belong there. | |||
Keeping that in mind - we create a folder under ~/Dropbox that we call '''encrypted''' and we create a mount point that we call '''Dropbox_unencrypted'''. | |||
We can create the directories manually or let enfcs auto generate them: | |||
encfs ~/Dropbox/encrypted ~/Dropbox_unencrypted | |||
Just like under any first time run you accept the creation of the directories with a "y" -twice and pick "p" for paranoid mode. | |||
Then you enter the password. | |||
To access the Dropbox from another computer repeat the exact same procedure there and enter exactly the same password. | |||
That is all there is to it - your jiberish unreadable data will now be on the web (in the cloud) in the Dropbox/encrypted folder. It will only be readable to you after you have mounted ~/Dropbox_unencrypted on your local computer. | |||
[[File:encfsdb.png]] | |||
<br> | |||
==GUI helpers== | |||
To mount and un-mount there are helpers in AUR that can make the handling easier. <br> | |||
Genfcs will do the job. | |||
[[File:Gencfs.png]] | |||
Remember to always use the full path when working with the directories. | |||
Cryptkeeper is another GUI that will do the job. |