While this is not exactly what you are requesting, this might be worth looking at to see if it could be adapted, or the concept morphed to meet your needs.. While it uses the Windows TCP/IP stack as a place to put a re-direct to its firewall, there is no reason that it has to be programmed that way if it is a micro-kernel Linux. Rewrite and recompile.
In fact I could see the possibility that one could use use a two device system. The Linux based key to generate the encrypted file that would be ported over to a second USB key for data storage. This idea has interesting implications in that you might be able to tie a memory USB key to a specific Linux key, or, even more interesting, have multiple keys for storage that could be used for split knowledge key recovery. A USB hub with one port for the OS key and three for the key storage. and recovery. Sounds like it might be fun. Allen Ciolfi Laurence (Larry) CONT NPRI wrote: > I have not been able to find a USB stick with 100% on-board encryption yet > that works with anything other than Windows. If anyone is aware of one that > works in a Windows/Mac/Linux environment please share that info. > > Larry C. > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dennis Kezer > Sent: Friday, June 29, 2007 10:19 AM > To: [email protected] > Subject: Re: [FDE] FIPS IronKey fully encrypted USB Flash Drive. > > > And that was the fourth option I failed to mention in my message. Glad you > are going through the process. It looks like a good product, but some of us > are constrained by regulation on what can be used. I have been through most > of the site and can't seem to find if the product works with more than > Windows clients. Will it support Mac, Linux, Solaris, etc? > > > > _____ > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Jevans > Sent: Thursday, June 28, 2007 4:56 PM > To: [email protected] > Subject: Re: [FDE] FIPS IronKey fully encrypted USB Flash Drive. > > > > > > We very specifically say "Compliant" rather than "Validated" on our website. > > > > We are working with a lab to assist us through the FIPS 140-1 validation > process. > > > > We says FIPS Compliant on the website, rather than FIPS Validated, because we > have crypto components that have passed FIPS validation, but our overall > product is in process. Once the full product has been validated, we will > update the site from Compliant to Validated. > > > > - Dave > > > > ------------- > >>> from Dennis > > > > Looks interesting, but I notice they say "FIPS Compliant" rather than "FIPS > Validated." This means lack the money to go through the validation process, > lack the confidence they could pass the validation process, or the person who > designed their web page did not know the difference. Lacking a validated > implementation of AES means they can't be used to protect sensitive federal > government data. > > > > Dennis Kezer > > > > _______________________________________________ > FDE mailing list > [email protected] > http://www.xml-dev.com/mailman/listinfo/fde > _______________________________________________ FDE mailing list [email protected] http://www.xml-dev.com/mailman/listinfo/fde
