Hi,

Percival Blakeney wrote:

One "nice-to-have" feature for the project would be to
allow users to use the tokens in Linux systems as well
as Windows.  Initially I had hoped that OpenSC would
offer this, but I gather that it only supports
pkcs#15, and that the eToken's key & certificate
storage structures (and possibly other low-level
interface details) are proprietary.
You could use OpenSC also on Windows or use the library of Aladdin on Linux (if you don't have them, please tell me, as I'm an official Aladdin Solution Provider).

So I have some questions:
  1) Has this problem already been solved, or is there
some other workaround?
Not that I'm aware of...
  3) How irritated are Aladdin likely to get at having
their stuff reverse engineered (would this be a DMCA
brick-wall if I were in the USA)?
I can't speak for them really (so I could ask), but I guess, whatever gets more products out of the door, would be good for them as well. Alternatively, one person could describe the reverse engineered stuff in a document and yet another different person implement the description. This is some known way of "safe" reverse engineering...(So no guaranties :-))

--
Regards

Signer:      Eddy Nigg, StartCom Ltd.
Phone:       +1.213.341.0390

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Reply via email to