Open Bug 512341 Opened 12 years ago Updated 7 years ago

Security Build logic does not allow instrumenting the current code.


(NSS :: Build, defect)

Not set


(Not tracked)


(Reporter: murali, Unassigned)




Check out the line # 341 in the link below.

This does not uptake the LDFLAGS passed from the .mozconfig and so this whole security code in coreconf, nss etc., is not getting instrumented.

We should change the line from 

No, absolutely do not put LDFLAGS into the line with MKSHLIB in NSS.
Blocks: 512290
May be I'm selfish and looking only at code coverage view. But I would be really I interested to know the reason for the NO in comment #1

I'm asking this question with pure technical interest and not questioning your judgement. Please indulge my curiosity. 

Murali: there are a few Mozilla developers who know Mozilla's
and NSS's build systems very well.  You can find them in
bug 511743 (:bs, :luser, and cls).  They are the best people
to consult about this bug.

The fix of this bug will require changes to some NSS
makefiles and then pass your linker flags to NSS in
mozilla/security/manager/, similar to how you
pass your compiler flags to NSS:
I went and looked for places where LDFLAGS is used in existing NSS makefiles
and found 29 matching lines in 12 files.  See

It appears to me that LDFLAGS is used to hold the linker flags for linking
executable programs, but not the linker flags for shared libraries.
I hope some one is still looking at instrumenting NSS. Should I continue finding non insecure ways to instrument the NSS still ?
You need to log in before you can comment on or make changes to this bug.