[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mozilla-security
Subject:    [Fwd: PKCS #11 & CKF_PROTECTED_AUTHENTICATION_PATH]
From:       Frank Hecker <frank () collab ! net>
Date:       2000-03-22 6:35:10
[Download RAW message or body]

Copying this to netscape.public.mozilla.crypto and setting followups to
there. Anything having to do with NSS, PKCS#11, and anything involving
crypto should be in that group. The newsgroup
netscape.public.mozilla.security is for problems involving general
Mozilla security issues not related to crypto.

Frank
-- 
Frank Hecker            work: http://www.collab.net/
frank@collab.net        home: http://www.hecker.org/

Path: secnews.netscape.com!not-for-mail
From: Petr Kostka <pkostka@rkk.cz>
Newsgroups: netscape.public.mozilla.security
Subject: PKCS #11 & CKF_PROTECTED_AUTHENTICATION_PATH
Date: Tue, 21 Mar 2000 12:53:21 +0100
Organization: Another Netscape Collabra Server User
Message-ID: <38D762B1.E3495ABE@rkk.cz>
NNTP-Posting-Host: 193.165.191.87
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-2
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 4.72 [en] (Windows NT 5.0; I)
X-Accept-Language: cs,en

Hi all,
I am writing PKCS #11 module for Communicator 4.7 (moving to Mozilla
soon) and I have discovered that NSS never checks for
CKF_PROTECTED_AUTHENTICATION_PATH flag in token flags in case he needs
user to login and always asks for pin. But I would like it not to ask,
while we have our own authentication method not neccessarily asking for
user's pin. I went through the source code of NSS released, but I have
found no solution to this problem. Do you know some work-around? Or did
I omit something?

Thanks
Petr



[prev in list] [next in list] [prev in thread] [next in thread]