hardcoresushi/libcryfs
1
0
Fork 0
Code Issues Pull Requests Releases Activity

Remove obsolete dependency

Browse Source
This commit is contained in:
Sebastian Meßmer 2020-07-02 03:03:00 -07:00 committed by GitHub
parent 7d02e20f89
commit e7fa2817d2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -140,9 +140,7 @@ Creating .deb and .rpm packages
It is recommended to install CryFS using packages, because that allows for an easy way to uninstall it again once you don't need it anymore. It is recommended to install CryFS using packages, because that allows for an easy way to uninstall it again once you don't need it anymore.
There are additional requirements if you want to create packages. They are: If you want to create a .rpm package, you need to install rpmbuild.
- CMake version >= 3.3
- rpmbuild if you're creating a .rpm package
1. Clone repository 1. Clone repository
@ -159,4 +157,4 @@ There are additional requirements if you want to create packages. They are:
Disclaimer Disclaimer
---------------------- ----------------------
On the event of a password leak, you are strongly advised to create a new filesystem and copy all the data over from the previous one. Done this, all copies of the compromised filesystem and config file must be removed (e.g, from the "previous versions" feature of your cloud system) to prevent access to the key (and, as a result, your data) using the leaked password. In the event of a password leak, you are strongly advised to create a new filesystem and copy all the data over from the previous one. Done this, all copies of the compromised filesystem and config file must be removed (e.g, from the "previous versions" feature of your cloud system) to prevent access to the key (and, as a result, your data) using the leaked password.