From: Neil Horman <nhorman@tuxdriver.com>
To: Deep Debroy <ddebroy@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] library choices for AES CBC/GCM on dpdk app datapath
Date: Thu, 2 Apr 2015 07:30:43 -0400 [thread overview]
Message-ID: <20150402113043.GA26735@hmsreliant.think-freely.org> (raw)
In-Reply-To: <CABg=H3MR0V_-evtyAFPero=1VqCWfVQ0T9d8sc9NBgQMeY0bOw@mail.gmail.com>
On Wed, Apr 01, 2015 at 03:54:27PM -0700, Deep Debroy wrote:
> Hi, I was wondering if anyone has pointers for a crypto library
> implementing AES CBC and GCM that I can use for encrypting network packets
> in a DPDK app's datapath.
>
> The app is supposed to run in a VM in the cloud. So access to crypto
> acceleration hardware (besides Intel AES NI/pmuludq) may not be present.
>
> Does it make sense to look into OpenSSL and invoking it's APIs from a DPDK
> app?
>
> Thanks!
>
The openssl libcrypto library provides most of the above I think. You can also
just use the AF_ALG protocol to leverage the kernels crypto resources.
Neil
prev parent reply other threads:[~2015-04-02 11:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 22:54 Deep Debroy
2015-04-02 11:30 ` Neil Horman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150402113043.GA26735@hmsreliant.think-freely.org \
--to=nhorman@tuxdriver.com \
--cc=ddebroy@gmail.com \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).