We are happy to announce an interim source release of PSM 2.0 for
developers that want to build PSM 2.0 in their trees. If you follow the
instructions in this message, you will get a browser that uses PSM 2.0
for SSL, wallet encryption technology, and setting the lock icon in your
browser's pages. Security Info is not implemented yet, so nothing will
happen when you click on the lock icon.
We have also done some work to make it possible to replace the default
UI that comes with PSM 2.0. If you are a developer that would like to
experiment with replacing our UI, you'll need to replace our
implementation of nsINSSDialogs in the component
pippki.dll/libpippki.so. You'll also want to remove pippki.jar from
your chrome directory. That is where all the resources used to create
XUL windows by PSM 2.0 are stored. We do not have extensive
documentation on the interfaces pippki implements as they are a work in
progress and will change by the time PSM 2.0 is finalized. We welcome
feedback on how to improve those interfaces.
For this release, we've also added support for switching profile
directories in PSM 2.0.
This source release consists of the PSM 2.0 code
(mozilla/security/manager) and the NSS libraries it uses for the lower
level crypto technologies (mozilla/security/manager
mozilla/security/coreconf) as well as a date tag pull of the client
tree.
We're using NSS 3.2 plus some patches to enable profile switching and
building on win32.
PSM 2.0 code is the trunk of PSM 2.0 as it existed on the afternoon of
March 15, 2001.
The client tree is from March 15, 2001 1:48 PST
Here are the instructions for building this release:
Win32:
0) Set up your machine to build the mozilla client by following the
instructions on the following web site
http://mozilla.org/build/win32.html
1) cvs co -D "2001-03-15 13:48" mozilla/client.mak
2) set BUILD_PSM2=1
3) set MOZ_DATE=2001-03-15 13:48
4) set NSS_CO_TAG=PSM20_M_1_5_TAG
5) set PSM_CO_TAG=PSM20_M_1_5_TAG
6) If building debug: set MOZ_DEBUG=1
If building optimized: set MOZ_DEBUG=
7) cd mozilla
8) nmake /f client.mak pull_and_build_all
Linux:
0) Set up your machine to build the mozilla client by following the
instructions on the following web site
http://mozilla.org/build/unix.html
1) cvs co -D "2001-03-15 13:48" mozilla/client.mk
2) cd mozilla
3) gmake -f client.mk pull_all MOZ_CO_DATE="2001-03-15 13:48"
4) In the directory where you want the binaries tree to exist:
<path to source>/configure [--disable-debug --enable-optimize]
5) gmake
6) cvs co -r PSM20_M_1_5_TAG mozilla/security/nss
mozilla/security/coreconf mozilla/security/manager
7) Issue this command in the same directory as the command issued in
step 4.
Give the same optional parameters in this step as the ones you issue
in step 4.
<path to source>/configure --enable-modules=psm2 [--disable-debug
--enable-optimize]
8) gmake BUILD_MODULES=psm2
Macintosh:
The Macintosh platform is not supported as part of this milestone
release. If you'd like to build PSM 2.0 on the Macintosh, send me
e-mail and I'll send you some diffs since the necessary changes to the
Macintosh build scripts have not been checked in.
If you would like to use PSM 2.0 against the latest trunk of mozilla,
then alter the above rules as follows:
Win32:
1) Do not pass -D "2001-03-15 13:48" to the cvs command.
5) Make sure the environment variable PSM_CO_TAG has no value
Linux:
1) Do not pass -D "2001-03-15 13:48" to the cvs command
3) Do not pass MOZ_CO_DATE="2001-03-15 13:48" as part of the gmake
command line arguments.
6) Do not check out mozilla/security/manager (ie PSM 2.0 code) with a
tag. Pull it from the trunk. This step becomes 2 parts:
6a) cvs co -r PSM20_M_1_5_TAG mozilla/security/coreconf
mozilla/security/nss
6b) cvs co mozilla/security/manager
--
Javier Delgadillo Sun / Netscape Alliance
(408) 276-3977 Software Engineer
mailto:[EMAIL PROTECTED] http://people.netscape.com/javi
