1 |
On 09/14/2010 12:17 PM, Frank Peters wrote: |
2 |
> I wasn't sure if the Crypto API was purely for use within kernel space or |
3 |
> if user space applications could have access to it in the same manner as with |
4 |
> other kernel system routines. But I guess that the Crypto API is just for |
5 |
> the use of the kernel. |
6 |
|
7 |
The API will be built automatically if you enable any settings that |
8 |
require it. The only reason to explicitly build it is if you plan on |
9 |
loading kernel modules built from a different source tree that use the |
10 |
API. In that case, you'll end up with missing symbols if you don't |
11 |
explicitly build the Crypto API (or also provide that via a module). |
12 |
|
13 |
Maybe if you had some kind of proprietary disk/LAN/etc-encryption |
14 |
hardware that supplied a closed-source module you might have need of this. |
15 |
|
16 |
If you used another distro where modules tended to come pre-packaged |
17 |
that could also be a concern. |
18 |
|
19 |
Since virtually all the modules on Gentoo are provided by the users |
20 |
themselves there isn't much of a need for this. |
21 |
|
22 |
Rich |