On 1/24/06, Anders Rundgren <[EMAIL PROTECTED]> wrote:
>
> Kyle,
> The NDA situation is indeed very bad for progress.
> Then the question who is going to standardize such a thing?
>
> ITU does not really deal with browsers, this seems to be more a W3C, OASIS
> or IETF type of activity.
...but the
Julien Pierre wrote:
Vivek,
Vivek Kumar wrote:
Hi,
I am currently working with a PKCS#11 library, have modified it to
support generation of public keys on the token.
When i try to delete the certificate from Mozilla
(Options->Advanced->Manage certificates), C_DestroyObject is getting
calle
Mark Hobbs wrote:
Thanks for this Bob, unfortunately the behaviour still remains
unchanged, as
soon as I go to the login page of my Yahoo account I get a smartcard PIN
request screen, which is strange as the Yahoo login is not even SSL.
I am not convinces the behaviour was the same with FireFox
Anders Rundgren wrote re USSI and browser digital signature schemes:
The NDA situation is indeed very bad for progress.
Then the question who is going to standardize such a thing?
ITU does not really deal with browsers, this seems to be more a W3C,
OASIS or IETF type of activity.
Note that t
Vivek,
Vivek Kumar wrote:
Hi,
I am currently working with a PKCS#11 library, have modified it to
support generation of public keys on the token.
When i try to delete the certificate from Mozilla
(Options->Advanced->Manage certificates), C_DestroyObject is getting
called only for the certifi
Florian ,
I don't expect you to agree, but it may be worth reading anyway :-)
>The universal client is not secure enough for most applications.
The universal client is already a fact. The entire Internet depends on it.
What you are saying about non-repudiation may be correct, but
I don't think
> >
> > If the SSL site is not requesting client auth, then the prompts for your
> > token pin during SSL may have to do with how the token was installed. If
> > the token was installed as 'the default RSA device', then NSS assumes
> > the token is a hardware accelerator and will try to use the tok
* Anders Rundgren:
> Somewhat surprising, the people who seem to be the least aware of
> these efforts to transform the ubiquitous Internet browser from being
> a "Universal Thin Client", to become a "Universal PKI-enabled Thin Client"
> are actually the browser vendors and W3C!
>
> Comments?
The
Hi,
I am currently working with a PKCS#11 library, have modified it to support generation of public keys on the token.
When i try to delete the certificate from Mozilla (Options->Advanced->Manage certificates), C_DestroyObject is getting called only for the certificate and the private key object
Kyle,
The NDA situation is indeed very bad for
progress.
Then the question who is going to standardize such
a thing?
ITU does not really deal with browsers, this seems
to be more a W3C, OASIS or IETF type of activity.
In my opinion there are other parts of the browser
PKI support that ma
On 1/23/06, Nelson B <[EMAIL PROTECTED]> wrote:
> AFAIK, *NONE* of the groups named above has *EVER* contacted the
> developers of mozilla's crypto code (NSS and PSM) about this.
> Just last month, we learned about the South Korean government's efforts,
> not from that government, but from some Sou
> -Original Message-
> From: Bob Relyea [mailto:[EMAIL PROTECTED]
> Sent: 23 January 2006 17:31
> To: [EMAIL PROTECTED]
> Cc: dev-tech-crypto@lists.mozilla.org
> Subject: Re: PKCS#11 module and FireFox password promting
>
>
> If the SSL site is not requesting client auth, then the prompts
12 matches
Mail list logo
