Issue 81230 - macro security level configuration depends on mozilla build
Summary: macro security level configuration depends on mozilla build
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: 680m225
Hardware: All All
: P4 Trivial (vote)
Target Milestone: AOO Later
Assignee: joachim.lingner
QA Contact: issues@framework
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-03 14:51 UTC by philipp.lohmann
Modified: 2010-07-01 14:05 UTC (History)
6 users (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description philipp.lohmann 2007-09-03 14:51:43 UTC
I discovered during investigation of issue 79885 that not building mozilla
implicitly disables build (and packaging) of the service providing the macro
security dialog (tools->options->security->macro security ...). Since the
default level is "high" now meaning that macros are silently disabled this
leaves the user with no opportunity to run macros if so desired.

Perhaps it is possible to have this dialog available without requiring a mozilla
build.
Comment 1 joachim.lingner 2007-09-03 15:25:06 UTC
As I understood issue 79885 the dialog is in xmlsecurity which has a dependency
to the mozilla module. The idea is to separate the dialog from this dependency.
However, the macro security dialog has a text area where it shows certificates,
which is probably the cause for the dependency. If this is the case then the
dependency is justified. 
Comment 2 ht990332 2007-09-26 01:09:10 UTC
There's another problem here. At least 2.3.0, internal xmlsec uses mozilla-nss
and won't build against a seperate nss.
Unless I am mistaken #69368 needs to be fixed first before doing a
--disable-mozilla build.
Comment 3 joachim.lingner 2008-01-15 12:02:03 UTC
The code of the macro security dialog needs the mozilla libraries and is
therefore linked accordingly. Therefore this dependency is justified.
Comment 4 ht990332 2008-01-15 12:18:35 UTC
If mozilla is only used for nss, then people with nss built apart from mozilla
(as in ArchLinux) should be able to build with system nss instead of the whole
mozilla suite. I think the first step is issue 69368.

There is also the mozilla plugin.
Comment 5 ht990332 2008-01-15 12:21:55 UTC
As a clarification, we should require only nss whenever possible (for the macro
security / digital certificates) and the whole mozilla/xulrunner only for
building the mozilla plugin.
Comment 6 alan 2009-10-11 06:58:46 UTC
I had this problem when I built 3.1.1 with mozilla disabled. I reconfigured, and
rebuilt, but the problem remained until I did a clean build. It seems that
something should be changed in the makefiles, so that a clean build won't be
necessary.
Comment 7 philipp.lohmann 2010-07-01 13:39:35 UTC
@jl: I guess this would be more your area of expertise. If there aren't any
plans for this, please close.
Comment 8 joachim.lingner 2010-07-01 14:04:55 UTC
Yes, no plans to change this. Anyway showing the certificates requires NSS. Closing.
Comment 9 joachim.lingner 2010-07-01 14:05:21 UTC
.