Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Clem Taylor <clem.taylor@gmail.com>
To: linux-mips@linux-mips.org
Subject: Au1550 crypto engine and linux?
Date: Wed, 19 Jan 2005 20:05:46 -0500	[thread overview]
Message-ID: <ecb4efd10501191705570371d4@mail.gmail.com> (raw)

This may be a bit off topic, but this list seems to be a good place to
try. I was wondering if anyone here is using the Au1550 crypto engine
with linux. I'm working on a device that will have all communications
encrypted with SSL or IPSec. I am looking to use the crypto engine to
accelerate OpenSSL & IPSec and provide a source of quality random
numbers. The DBAu1550 CD came with a Linux CGX driver, but I'm not
sure what that driver actually provides or how it is intended to be
used. The OpenSSL code has for several different hardware crypto
devices, but I didn't see any reference to SafeNet or CGX. It also has
support for /dev/crypto, but that only seems to be implemented for
OpenBSD. Any ideas how this block is supposed to do be used?

                              Thank you,
                              Clem Taylor

                 reply	other threads:[~2005-01-20  1:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=ecb4efd10501191705570371d4@mail.gmail.com \
    --to=clem.taylor@gmail.com \
    --cc=linux-mips@linux-mips.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