OpenSolaris

1. Community: OS/Net (ON)
   1. Blogs
   2. Development Process
   3. Developer's Reference
      1. Introduction
      2. Prerequisites
      3. The Source Tree, part 1
      4. The Source Tree, part 2
      5. Building OpenSolaris
      6. Installing and Testing OpenSolaris
      7. Integration Procedure
      8. Best Practices and Requirements
      9. Glossary
   4. Discussions
   5. Installation (from source) Quickstart
      1. Annotated nightly(1) Mail Example
   6. Currently Known Issues
   7. CRT
      1. Advocates & Sponsors
      2. Becoming a CRT Advocate
      3. Charter
      4. RTI nits to avoid
      5. Sponsor Tasks
      6. Becoming a Sponsor
   8. Schedule
   9. ONNV Flag Days, Heads Ups, and Project Integration History
      1. All
      2. Builds 91-95
      3. Builds 86-90
      4. Builds 81-85
      5. Builds 76-80
      6. Builds 71-75
      7. Builds 66-70
      8. Builds 61-65
      9. Builds 56-60
      10. Builds 51-55
      11. Builds 46-50
      12. Builds 41-45
      13. Builds 36-40
      14. Builds 31-35
      15. Builds 26-30
      16. Builds 21-25
   10. Leaders
   11. Observers
   12. Putback Logs
   13. Developing Solaris
       1. Quality Death Spiral
   14. wx
   15. findunref and unreferenced files
   16. Bourne/Korn Shell Coding Conventions

Flag Day: build machine update required following elfsign support of Verisign Trust Network

Date: Wed, 21 Feb 2007 09:21:24 -0800 (PST)
From: John Zolnowsky x69422/408-404-5064 <John.Zolnowsky at sun dot com>
To: onnv-gate at onnv dot eng dot sun dot com, on-all at eng dot sun dot com
Subject: Flag Day: build machine update required following elfsign support of Verisign Trust Network

It has been discovered that my recent putback into Nevada for

	CR 6391249: elfsign needs to support Verisign certificate chain

introduced a flag day for building of cryptographic modules.  Builds
performed using older versions of elfsign will have improperly-formed
signatures on cryptographic modules and libraries.  Symptoms will be
failure to register cryptographic kernel modules or verify pkcs11
plugin libraries.

Use of the nightly -t option will use the updated version of elfsign to
sign, avoiding the problem.  Build servers can be updated to have new
versions of /usr/bin/elfsign and /usr/lib/libelfsign.so.1.  The script
/net/onnv.sfbay/public/bin/update_elfsign, invoked by root, will update
these files with current versions.

I apologize for any inconvenience that this may have caused.

						-JZ