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

README: fix formatting error

This commit is contained in:
Jakob Unterwurzacher 2016-10-09 21:29:43 +02:00
parent 5ef27ee549
commit 15b6ab12b1
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@ -125,12 +125,12 @@ v1.1 (not yet released)
and later. and later.
* The default, forward mode, stays fully compatible with older versions. * The default, forward mode, stays fully compatible with older versions.
Forward mode will keep using GCM because it is much faster. Forward mode will keep using GCM because it is much faster.
* Accept "-o a,b,c"-style options that are passed at the end of * Accept `-o foo,bar,baz`-style options that are passed at the end of
the command-line, like mount(1) does. All other options must still the command-line, like mount(1) does. All other options must still
precede the passed paths. precede the passed paths.
* This allows mounting from /etc/fstab. See * This allows **mounting from /etc/fstab**. See
(#45)[https://github.com/rfjakob/gocryptfs/issues/45] for details. [#45](https://github.com/rfjakob/gocryptfs/issues/45) for details.
* Mounting on login using pam_mount works as well. It is * **Mounting on login using pam_mount** works as well. It is
[described in the wiki](https://github.com/rfjakob/gocryptfs/wiki/Mounting-on-login-using-pam_mount). [described in the wiki](https://github.com/rfjakob/gocryptfs/wiki/Mounting-on-login-using-pam_mount).
* To prevent confusion, the old `-o` option had to be renamed. It is now * To prevent confusion, the old `-o` option had to be renamed. It is now
called `-ko`. Arguments to `-ko` are passed directly to the kernel. called `-ko`. Arguments to `-ko` are passed directly to the kernel.