Re: Certificate Management Protocol with RFC4210

SecureToken is optional.
initial PIN is set by vendor and users have control.

service providers has no control for it.




On Tue, Mar 26, 2013 at 10:20 PM, Anders Rundgren <anders.rundgren@telia.com
> wrote:

> On 2013-03-26 14:07, Mountie Lee wrote:
> > PIN is used to access secure token storing the certificate and private
> key
> > secure token is accessed via PKCS#11 interface.
> >
> > the other parts (servers and services) are based on RFC4210 (previously
> RFC2510)
>
> Mountie,
>
> But how do you set the initial PIN?
>
> Regards
> Anders
>
>
> >
> > regards
> > mountie.
> >
> >
> > On Tue, Mar 26, 2013 at 6:13 PM, Anders Rundgren <
> anders.rundgren@telia.com <mailto:anders.rundgren@telia.com>> wrote:
> >
> >
> http://lists.w3.org/Archives/Public/public-webcrypto/2013Mar/0122.html
> >
> >     Doesn't the Korean NPKI use PIN-codes (two-factor authentication)?
> >
> >     If so I don't understand how the deal with those using CMP since no
> PKIX-protocols support this basic functionality.
> >     If they on the other hand don't use PIN-codes they are running a
> very unusual NPKI.
> >
> >     Anders
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > --
> > Mountie Lee
> >
> > PayGate
> > CTO, CISSP
> > Tel : +82 2 2140 2700
> > E-Mail : mountie@paygate.net <mailto:mountie@paygate.net>
> >
> > =======================================
> > PayGate Inc.
> > THE STANDARD FOR ONLINE PAYMENT
> > for Korea, Japan, China, and the World
> >
> >
> >
> >
>
>
>
>
>
>
>
>


-- 
Mountie Lee

PayGate
CTO, CISSP
Tel : +82 2 2140 2700
E-Mail : mountie@paygate.net

=======================================
PayGate Inc.
THE STANDARD FOR ONLINE PAYMENT
for Korea, Japan, China, and the World