2001-02-10 02:53:10 +00:00
|
|
|
/* -*- Mode: C++; tab-width: 2; indent-tabs-mode: nil; c-basic-offset: 2 -*-
|
|
|
|
*
|
2012-05-31 09:33:35 +00:00
|
|
|
* This Source Code Form is subject to the terms of the Mozilla Public
|
|
|
|
* License, v. 2.0. If a copy of the MPL was not distributed with this
|
|
|
|
* file, You can obtain one at http://mozilla.org/MPL/2.0/. */
|
2001-02-10 02:53:10 +00:00
|
|
|
|
|
|
|
#ifndef NSS_HELPER_
|
|
|
|
#define NSS_HELPER_
|
2001-03-20 18:00:44 +00:00
|
|
|
|
|
|
|
#include "nsIInterfaceRequestor.h"
|
2001-09-05 21:27:22 +00:00
|
|
|
#include "nsIInterfaceRequestorUtils.h"
|
bug 1215690 - remove nsPSMUITracker r=Cykesiopka r=mgoodwin
nsPSMUITracker was problematic. Apparently it was originally intended to prevent
NSS shutdown while NSS-related UI operations were going on (such as choosing a
client certificate). However, when nsNSSComponent would receive the event that
told it to shutdown NSS, it would attempt to call
mShutdownObjectList->evaporateAllNSSResources(), which would call
mActivityState.restrictActivityToCurrentThread(), which failed if such a UI
operation was in progress. This actually prevented the important part of
evaporateAllNSSResources, which is the releasing of all NSS objects in use by
PSM objects. Importantly, nsNSSComponent didn't check for or handle this failure
and proceeded to call NSS_Shutdown(), leaving PSM in an inconsistent state where
it thought it was okay to keep using the NSS objects it had when in fact it
wasn't.
In any case, nsPSMUITracker isn't really necessary as long as we have the
nsNSSShutDownPreventionLock mechanism, which mostly works and is what we should
use instead (or not at all, if no such lock is needed for the operation being
performed (for example, if no NSS functions are being called)).
2015-10-16 21:31:57 +00:00
|
|
|
#include "nsNSSShutDown.h"
|
2001-03-21 00:57:46 +00:00
|
|
|
#include "pk11func.h"
|
2001-03-20 18:00:44 +00:00
|
|
|
|
|
|
|
//
|
|
|
|
// Implementation of an nsIInterfaceRequestor for use
|
|
|
|
// as context for NSS calls
|
|
|
|
//
|
|
|
|
class PipUIContext : public nsIInterfaceRequestor
|
|
|
|
{
|
|
|
|
public:
|
2013-07-19 02:24:14 +00:00
|
|
|
NS_DECL_THREADSAFE_ISUPPORTS
|
2001-03-20 18:00:44 +00:00
|
|
|
NS_DECL_NSIINTERFACEREQUESTOR
|
|
|
|
|
|
|
|
PipUIContext();
|
|
|
|
|
2014-06-23 22:40:03 +00:00
|
|
|
protected:
|
|
|
|
virtual ~PipUIContext();
|
2001-03-20 18:00:44 +00:00
|
|
|
};
|
|
|
|
|
2001-02-10 02:53:10 +00:00
|
|
|
//
|
|
|
|
// Function to get the implementor for a certain set of NSS
|
|
|
|
// specific dialogs.
|
|
|
|
//
|
|
|
|
|
|
|
|
nsresult
|
2002-09-17 18:51:22 +00:00
|
|
|
getNSSDialogs(void **_result, REFNSIID aIID, const char *contract);
|
2001-03-20 18:00:44 +00:00
|
|
|
|
|
|
|
extern "C" {
|
|
|
|
// a "fake" unicode conversion function
|
|
|
|
PRBool
|
|
|
|
pip_ucs2_ascii_conversion_fn(PRBool toUnicode,
|
|
|
|
unsigned char *inBuf,
|
|
|
|
unsigned int inBufLen,
|
|
|
|
unsigned char *outBuf,
|
|
|
|
unsigned int maxOutBufLen,
|
|
|
|
unsigned int *outBufLen,
|
|
|
|
PRBool swapBytes);
|
|
|
|
}
|
|
|
|
|
2001-03-21 00:57:46 +00:00
|
|
|
//
|
|
|
|
// A function that sets the password on an unitialized slot.
|
|
|
|
//
|
|
|
|
nsresult
|
bug 1215690 - remove nsPSMUITracker r=Cykesiopka r=mgoodwin
nsPSMUITracker was problematic. Apparently it was originally intended to prevent
NSS shutdown while NSS-related UI operations were going on (such as choosing a
client certificate). However, when nsNSSComponent would receive the event that
told it to shutdown NSS, it would attempt to call
mShutdownObjectList->evaporateAllNSSResources(), which would call
mActivityState.restrictActivityToCurrentThread(), which failed if such a UI
operation was in progress. This actually prevented the important part of
evaporateAllNSSResources, which is the releasing of all NSS objects in use by
PSM objects. Importantly, nsNSSComponent didn't check for or handle this failure
and proceeded to call NSS_Shutdown(), leaving PSM in an inconsistent state where
it thought it was okay to keep using the NSS objects it had when in fact it
wasn't.
In any case, nsPSMUITracker isn't really necessary as long as we have the
nsNSSShutDownPreventionLock mechanism, which mostly works and is what we should
use instead (or not at all, if no such lock is needed for the operation being
performed (for example, if no NSS functions are being called)).
2015-10-16 21:31:57 +00:00
|
|
|
setPassword(PK11SlotInfo* slot, nsIInterfaceRequestor* ctx,
|
|
|
|
nsNSSShutDownPreventionLock& /*proofOfLock*/);
|
2001-03-21 00:57:46 +00:00
|
|
|
|
2001-02-10 02:53:10 +00:00
|
|
|
#endif
|