Ben Bucksch wrote:
> UI:
> - The email address is not listed for my own certs. Email address is
> essential - multiple addresses per person are normal. I won't be able to
> distinguish my certs, if I can't see the address.
There's not much room there unless I make the Cert Manager much wider.
How about if I replace "Issued On" with "Mail Address"?
> - Move the Secure Mail pane to Mailnews section (out of Security). This
> is more logical and where I would search for them.
Interesting suggestion. I'll give it a whirl.
> - Move the SSL pane to Navigator section, assuming it applies to the
> browser only and not e.g. snews.
It applies to all the SSL/TLS protocols like SSL/NNTP, SSL/SMTP,
SSL/IMAP, and SSL/LDAP in addition to SSL/HTTP (HTTPS).
> - Merge Certificate Manager and Device Manager. I don't see a need to
> separate them. Merging keeps the menu smaller.
I'll have to ponder this one some more. The CM manages your certs, and
the DM manages (among other things) your smart cards. I suppose we
could have a "Certificate and Device Manager" by adding a new tab to the
current CM called "Devices". Is that what you had in mind?
>
> Tasklist:
> - What is "UTF-8 to UNICODE conversion - 1 day"? I'd bet, we have such a
> function already.
Terry and Javi will have to answer this one.
>
> Roadmap:
> - I'd call the libraries psm* (e.g. psmpki). PIP only makes sense as
> name for a temporary project. Compare iip (IMAP in process), bip
> (bookmarks in process), ....
Same here.
>
>
> Some questions about PSM 1.x, trying to understand why you created
> (out-of-process) PSM 1.x in the first place:
> <http://www.mozilla.org/projects/security/pki/psm/history.html>
>
>> * In the past, crypto-savvy customers often asked Netscape to fix
>> bugs or add security features outside the normal Commnicator
>> release sechdule. The PSM model gave the development team more
>> freedom to act quickly without waiting for the next Communicator
>> release.
>>
>
> Did you actually deliver PSM to these customers?
Yes. We had PSM for Communiator 4.5 and higher long before Netscape-6
shipped.
>
>> * Networking code for Mozilla was not available until the end of
>> 1999. If we hadn't started work on Personal Security Manager
>> until then, it would not have been finished in time to ship with
>> Netscape 6.
>>
>
> Well, Mailnews is working just fine :).
--
Bob Lord
Director, Security Engineering
Netscape Communications Corp.
http://www.mozilla.org/projects/security/pki/
http://people.netscape.com/lord/open-reqs.html
