Closed
Bug 131430
Opened 24 years ago
Closed 24 years ago
Issues with the version information resource of softokn3.dll
Categories
(NSS :: Build, defect, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
3.4
People
(Reporter: wtc, Assigned: wtc)
References
Details
Attachments
(1 file)
|
631 bytes,
patch
|
rrelyea
:
review+
|
Details | Diff | Splinter Review |
The good news is that softokn3.dll does have the proper
Windows version information resource, unlike its Unix
counterpart libsoftokn3.so (bug 131427).
The bad news is that I found two issues with its version
information.
1. The InternalName is "softoken3" and the OriginalFilename
is "softoken3.dll". These should be "softokn3" and
"softokn3.dll".
2. The softokn3.dll in the mozilla0.9.9 build has the
FileDescription "NSS Builtin Crypto PKCS #11 Library for
Clients". I found that this is because of the following
code in lib/softoken/softokn.rc:
#ifdef MOZ_CLIENT
#define MY_FILEDESCRIPTION "NSS Builtin Crypto PKCS #11 Library for Clients"
#else
#define MY_FILEDESCRIPTION "NSS Builtin Crypto PKCS #11 Library"
#endif
Bob, is this because we use different compile-time configuration
parameters for softoken when building for the Mozilla client (and
presumably for the other client applications)? (See bug 123753.)
I am wondering if we should go one step further and use a
different file name for the clients' version of the softoken.
This will allow the installation of both versions of the
softoken in the same (system) directory. On the other hand,
this will force us to continue to use that file name even
when we can use the same softoken for both servers and clients.
| Assignee | ||
Updated•24 years ago
|
Status: NEW → ASSIGNED
Priority: -- → P1
Target Milestone: --- → 3.4
| Assignee | ||
Comment 1•24 years ago
|
||
Comment 2•24 years ago
|
||
if -DMOZ_CLIENT is defined, softoken has defines different hash table sizes. It
seemed prudent to have a different name show up in the strings for the shared
library.
There isn't a functional difference between the two versions, only a performance
issue.
If we rename it, we would end up propogating that change into nss3 proper,
necessitating different versions of nss3, then that would necessitate changes in
ssl3 and smime3.
I prefer to handle this longer term by having a single softokn3.dll and having a
config option which tell is whether or not too configure for server usage or
client usage.
Updated•24 years ago
|
Attachment #74521 -
Flags: review+
| Assignee | ||
Comment 3•24 years ago
|
||
Patch checked into the tip of NSS.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•