Closed Bug 37073 Opened 24 years ago Closed 22 years ago

Personal Security Manager (PSM) not present in new builds

Categories

(Core Graveyard :: Security: UI, defect, P3)

Product:
Core Graveyard
Component:
Security: UI
Version:
1.0 Branch
Platform:
x86
Windows NT
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: morse, Assigned: thayes0993)

References

Details

(Whiteboard: [nsbeta2-]) 

Yesterday I followed the instructions that Terry Hayes gave me for obtaining 
psm.exe on my machine.  With that, I was able to complete the integration of 
single-signon with PSM and had it working.  I checked my changes into the tree.

This morning I pulled a fresh tree into a new \mozilla directory, built it, and 
ran it.  The first time I attempted to use a single-signon function (which in 
turn needs psm) I got a pop-up window asking me where my psm.exe was located.  
Of course I didnt' have any in my new \mozilla directory.

I checked and found psm.exe in the backup directory of the previous 
\mozilla directory that I used so I copied it over.  I resumed execution and 
then, one by one, was informed that I was missing the following dll's, each of 
which I then copied over.  After doing all the manual copying, single signon 
worked.

   nsuni3231.dll
   nscnv3231.dll
   nsres3231.dll
   nsfmt3231.dll
   plc3.dll
   nspr3.dll
   plds3.dll
*** Bug 37072 has been marked as a duplicate of this bug. ***
PSM CANNOT BE PART OF MOZILLA. The code is patented, not open, etc. etc. etc.

Steve, back your change out, please. If i don't here from you in short order,
i'm backing it out myself.
Assignee: thayes → morse
20 minutes have passed, backing this out.
This is blocking me from even looking at many bugs relating to form submission. 
I can't submit forms because wallet requires psm - I can't install psm because 
of another bug.  Updating now in hopes the back out fixes this...
Steve, is there a way to turn wallet off?  It's probably there in the UI 
somewhere, I'm just not seeing it...  :)
Wallet should not be bothering you.  It is mostly passive -- you have to do 
something in order to cause it prefill a form or capture data from a 
form.  In one minor case does it take the initiative on its own and that is 
controlled by a pref (see the wallet preference panel)
You're right, largely, wallet and single sign-on have not been a bother at all.  
It was in this case because I happened to pull at a bad time.  (BTW, I no longer 
have the PSM problem after my update, thanks.)

However (hypothetical) suppose I as a user did not want single sign-on active.  
Where is the UI to turn this feature off and on?  When I get asked whether to 
store login/password, I am given the choices "yes", "no", and "never for this 
site".  I looked for a pref panel but could not find one.  Am I not looking in 
the right place?

BTW, I think this bug is FIXED, right?
The UI for turning single singlon off is in the pref panel.  But finding it is 
tricky due to recent pref regressions (I'm sure there's a bug report on this 
but I don't know the number off hand).

Open the pref panel and go to "forms and passwords" under "advanced".  What, you 
say you don't see "forms and passwords".  Yep, that's the regression -- the pref 
tree has become flattened and you don't see the subtrees.  Work-around -- 
double-click on advanced.  Suddenly the subtree opens and you see "forms and 
passwords" (don't ask me how to get to "cookies", I don't know any work-around 
for that).  On the pref pane now displayed you'll see a checkbox to turn off 
single signon.

No, this bug is not yet fixed.  Although I have all my code in place to link to 
PSM, PSM itself is still not part of the daily builds and that is the bug.  
However I don't know why the bug is assigned to me.  I opened it and assigned it 
to thayes who is on the crypto side of things.  Then leaf for some unknown 
reason reassigned it to me.  I'm going to reassing to thayes.
Blocks: 26085
This bug was filed because not having PSM was causing the wallet functionality
to not happen... i reassigned it to you, steve, because PSM cannot legally work
open source until after some patents expire in september. So this bug is either
invalid, because it's not legally possible right now, or it's a wallet bug
(which is fixed by not relying on the PSM functionality).
.
Assignee: morse → thayes
Keywords: nsbeta2
Just to clarify the above remark.  This bug is neither invalid nor is it a 
wallet bug.  It is a crypto bug that needs to be addressed by the crypto team.  
It is currently assigned to thayes waiting for him to make some decision on how 
to implement this.
I'll chime in here.  PSM probably will not be part of the build any time soon. 
There is a chance that we will be able to build it IF the developer gets the 
BSAFE package ($$) or gets a copy of RSAREF to use for the build.  Neither of 
these is in place yet.

Core functionality should not rely on PSM being present, unless we are willing 
to require people to download the PSM builds (on limited platforms) from the 
iPlanet site.  Core functionality should implement correct error handling, or 
fallback to some other mechanism to perform functions.

Currently, there is a problem with the PSM component that causes multiple 
prompts for location of a missing PSM server.  This needs to be fixed so that 
the information is requested once, cached, and used for future request for the 
service.  This is as much as I can promise in the short term.
Target Milestone: --- → M16
nsbeta2-
Whiteboard: [nsbeta2-]
This bug is totally invalid.  If PSM is not present, any interface that depends 
on this functionality should deal with it.  Requiring PSM installed is a bug.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
How can a feature request be invalid?  Are you saying that you never plan on 
having this implemented in either the mozilla or the commercial cobase?

Validity or invalidity of a feature has nothing to do with whether or not the 
rest of the codebase depends on it or not.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Steve, the functionality *is* provided in commercial builds already, because psm
is present. 

If this bug is about PSM not being present, then this bug will have to be
latered until sometime after the patents that restrict redistribution expire.

The point is that nothing core to mozilla can *require* the use of PSM (right
now).
Changing status to later.
Status: REOPENED → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → LATER
Verifying later.
Status: RESOLVED → VERIFIED
Hasn't this already been done?  So shouldn't we change the "later" to "fixed"?
PSM is now part of the Mozilla builds.
Status: VERIFIED → CLOSED
Mass changing Security:Crypto to PSM
Component: Security: Crypto → Client Library
Product: Browser → PSM
Target Milestone: M16 → ---
Version: other → 2.1
Mass changing Security:Crypto to PSM
LATER is deprecated per bug 35839.
Status: CLOSED → REOPENED
Resolution: LATER → ---
FIXED per comments.
Status: REOPENED → RESOLVED
Closed: 24 years ago → 22 years ago
Resolution: --- → FIXED
Verified.
Status: RESOLVED → VERIFIED
Version: 2.1 → 2.3
Product: PSM → Core
Version: psm2.3 → 1.0 Branch
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.