From: "Dr. David Alan Gilbert" <dave@treblig.org>
To: linux-scsi@vger.kernel.org
Subject: LTO 4 encryption support?
Date: Wed, 2 May 2007 09:56:32 +0100 [thread overview]
Message-ID: <20070502085632.GA11062@gallifrey> (raw)
Hi,
It is said that LTO 4 drives are starting to be available and
that they have encryption support built in.
Does anyone know anything about the encryption stuff on it?
In particular:
1) How can I tell if it is using encryption?
2) How can I set the encryption key on the drive?
I guess my biggest worry would be running a drive which I believed
wasn't encrypting and then only find out when I replace the drive
that it was encrypted; with some default key I didn't know.
However it would be nice to run with encryption if I could then
store that key in a few nice secure places.
Suggestions welcome.
Dave
--
-----Open up your eyes, open up your mind, open up your code -------
/ Dr. David Alan Gilbert | Running GNU/Linux on Alpha,68K| Happy \
\ gro.gilbert @ treblig.org | MIPS,x86,ARM,SPARC,PPC & HPPA | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
reply other threads:[~2007-05-02 9:38 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=20070502085632.GA11062@gallifrey \
--to=dave@treblig.org \
--cc=linux-scsi@vger.kernel.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