On 2012-04-18 13:06, ianG wrote:
> (lo-pri interest only requests)
Short return then :-)
>
> On 18/04/12 20:00 PM, Anders Rundgren wrote:
>> On 2012-04-18 11:04, helpcrypto helpcrypto wrote:
>
Container attestations must be performed at the APDU-level since
E2ES cannot be "abstracted"
(lo-pri interest only requests)
On 18/04/12 20:00 PM, Anders Rundgren wrote:
On 2012-04-18 11:04, helpcrypto helpcrypto wrote:
Container attestations must be performed at the APDU-level since
E2ES cannot be "abstracted".
I dont understand that.
See section 9.5 of:
http://forja.cenatic.es/
On 2012-04-18 11:04, helpcrypto helpcrypto wrote:
> On Wed, Apr 18, 2012 at 10:03 AM, Anders Rundgren
> wrote:
>> Dear "helpcrypto", now it became a little bit messy because I'm talking about
>> principles while you are talking about specific interfaces like NSS, and
>> PKCS #11.
>
> Ok. Rather
On Wed, Apr 18, 2012 at 10:03 AM, Anders Rundgren
wrote:
> Dear "helpcrypto", now it became a little bit messy because I'm talking about
> principles while you are talking about specific interfaces like NSS, and PKCS
> #11.
Ok. Rather than discussing technical or theorical point of views, i
thin
Dear "helpcrypto", now it became a little bit messy because I'm talking about
principles while you are talking about specific interfaces like NSS, and PKCS
#11.
> During enrollment, i need to know card is present and the keypair is
> generated inside. how can i achieve this without a pkcs#11 inte
> Although E2ES (End-to-End-Security with respect to the *container*) is
> actually my line of work (http://webpki.org/papers/keygen2/sks-api-arch.pdf),
> I don't understand why you would use it during signing or authentication.
> Yes, TLS-client-cert-authentication is also E2ES but it works "one l
6 matches
Mail list logo
