As a security precaution, we have turned on the setting "Require API key authentication for API requests" for everyone. If this has broken something, please contact
Last Comment Bug 623498 - Back port LDAP ASLR onto the current Thunderbird/SeaMonkey releases
: Back port LDAP ASLR onto the current Thunderbird/SeaMonkey releases
: fixed-seamonkey2.0.12
Product: MailNews Core
Classification: Components
Component: Build Config (show other bugs)
: 1.9.2 Branch
: All All
: -- normal (vote)
: ---
Assigned To: Mark Banner (:standard8)
Depends on: 602920 623497
  Show dependency treegraph
Reported: 2011-01-06 04:25 PST by Mark Banner (:standard8)
Modified: 2011-01-18 13:12 PST (History)
3 users (show)
bugspam.Callek: blocking‑seamonkey2.0.12+
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---

Update to LDAPCSDK_6_0_6E_MOZILLA_RTM (314 bytes, patch)
2011-01-17 04:16 PST, Mark Banner (:standard8)
bugspam.Callek: review+
standard8: approval‑thunderbird3.1.8+
bugspam.Callek: approval‑seamonkey2.0.12+
Details | Diff | Splinter Review

Description User image Mark Banner (:standard8) 2011-01-06 04:25:48 PST
Bug 602920 has implemented ASLR for the LDAP c-sdk. Bug 623497 is pulling this in on trunk, but we need to back-port it for the branches.

I don't think we need to back-port the other fixes on the branches, so we'll just land this in cvs and create a new cvs tag.
Comment 1 User image Justin Wood (:Callek) 2011-01-06 07:43:05 PST
technically I don't think this needs to block the SeaMonkey release; but I'm happy to take it.
Comment 2 User image Mark Banner (:standard8) 2011-01-17 04:16:31 PST
Created attachment 504413 [details] [diff] [review]

I've back-ported the changes in bug 602920, this should pick them up on the branches.
Comment 3 User image Justin Wood (:Callek) 2011-01-17 19:55:14 PST
Comment on attachment 504413 [details] [diff] [review]

I also consider my a+ on the 1.9.2 branch, given build-system land thoughts. I just can't set any official flag here.
Comment 4 User image Mark Banner (:standard8) 2011-01-18 13:12:25 PST
Now landed in both 1.9.1 and 1.9.2:

Note You need to log in before you can comment on or make changes to this bug.