On Sat, Oct 8, 2011 at 17:58, Jean-Michel Pouré - GOOZE
wrote:
> TrueCrypt x64 is able to detect OpenSC x32 pkcs11 libraries, not OpenSC
> x64 libraries.
TrueCrypt, like many other end user applications, is a *32* bit app.
___
opensc-devel mailing list
Is there any support for trusted (OS-level) PIN input in OpenSC?
Or is this supposed to be catered for by separate PIN-pads only?
I expect this feature will be standard in mobile devices.
Google have even managed to support "trusted path" in their wallet
application. I don't know anything how thi
Hello,
On Mon, Oct 10, 2011 at 12:27, Anders Rundgren
wrote:
> Is there any support for trusted (OS-level) PIN input in OpenSC?
Trusted path for me means guaranteed by tamper-proof mechanisms, which
usually means separate hardware-guaranteed channel, which in turn
would mean something like TPC, w
On 2011-10-10 12:05, Martin Paljak wrote:
> Hello,
>
> On Mon, Oct 10, 2011 at 12:27, Anders Rundgren
> wrote:
>> Is there any support for trusted (OS-level) PIN input in OpenSC?
> Trusted path for me means guaranteed by tamper-proof mechanisms, which
> usually means separate hardware-guaranteed
On Monday, October 10 at 12:43PM, Anders Rundgren wrote:
>
> On 2011-10-10 12:05, Martin Paljak wrote:
> > Hello,
> >
> > On Mon, Oct 10, 2011 at 12:27, Anders Rundgren
> > wrote:
> >> Is there any support for trusted (OS-level) PIN input in OpenSC?
>
> > Trusted path for me means guaranteed by
Le lundi 10 octobre 2011 à 11:22 +0300, Martin Paljak a écrit :
> TrueCrypt, like many other end user applications, is a *32* bit app.
Yes, you are right, my fault.
--
Jean-Michel Pouré - Gooze - http://www.gooze.eu
smime.p7s
Description: S/MIME cryptographic signature
