Lines Matching +full:key +full:- +full:up

1 .. SPDX-License-Identifier: GPL-2.0
9  - Overview.
10  - Usage.
11  - Mountpoints.
12  - Dynamic root.
13  - Proc filesystem.
14  - The cell database.
15  - Security.
16  - The @sys substitution.
45 	CONFIG_AF_RXRPC		- The RxRPC protocol transport
46 	CONFIG_RXKAD		- The RxRPC Kerberos security handler
47 	CONFIG_AFS_FS		- The AFS filesystem
51 	CONFIG_AF_RXRPC_DEBUG	- Permit AF_RXRPC debugging to be enabled
52 	CONFIG_AFS_DEBUG	- Permit AFS debugging to be enabled
88 	mount -t afs "%cambridge.redhat.com:root.afs." /afs
89 	mount -t afs "#cambridge.redhat.com:root.cell." /afs/cambridge
90 	mount -t afs "#root.afs." /afs
91 	mount -t afs "#root.cell." /afs/cambridge
101 named volume will be looked up in the cell specified during modprobe.
111 presents these to the user as directories that have a follow-link capability
135 	mount -t afs none /afs -o dyn
138 to look up a name in this directory will cause a mountpoint to be created that
139 looks up a cell of the same name, for example::
190 Secure operations are initiated by acquiring a key using the klog program.  A
197 	make klog LDLIBS="-lcrypto -lcrypt -lkrb4 -lkeyutils"
203 Assuming it's successful, this adds a key of type RxRPC, named for the service
209 	       -3 --alswrv      0     0  keyring: _ses.3268
210 		2 --alswrv      0     0   \_ keyring: _uid.0
211 	111416553 --als--v      0     0   \_ rxrpc: afs@CAMBRIDGE.REDHAT.COM
216 It is not required to acquire a key before using AFS facilities, but if one is
220 If a key is acquired, then all AFS operations, including mounts and automounts,
221 made by a possessor of that key will be secured with that key.
223 If a file is opened with a particular key and then the file descriptor is
224 passed to a process that doesn't have that key (perhaps over an AF_UNIX
225 socket), then the operations on the file will be made with key that was used to
232 The list of up to 16 @sys substitutions for the current network namespace can