Messages in this thread |  | | Date | Tue, 27 Dec 2016 15:16:14 +0100 | From | Daniel Borkmann <> | Subject | Re: [RFC PATCH 4.10 1/6] crypto/sha256: Refactor the API so it can be used without shash |
| |
On 12/27/2016 10:58 AM, Herbert Xu wrote: > On Mon, Dec 26, 2016 at 10:08:48AM -0800, Andy Lutomirski wrote: >> >> According to Daniel, the networking folks want to let embedded systems >> include BPF without requiring the crypto core. > > Last I checked the IPv4 stack depended on the crypto API so this > sounds bogus.
I think there's a bit of a mixup here with what I said. To clarify, requirement back then from tracing folks was that bpf engine and therefore bpf syscall can be build w/o networking enabled for small devices, so dependencies preferably need to be kept on a absolute minimum, same counts for either making it suddenly a depend on CRYPTO or a select CRYPTO for just those few lines that can be pulled in from lib/ code instead.
|  |