Secure module build center

A secure module building apparatus, comprising:

• a computer program product encoded in at least one non-transitory computer usable medium that, when executed, functions as:
• a secure module build center, configured generate modules corresponding to consumer computing systems, each of said consumer computing systems running one of a plurality of operating system types and versions, said secure module build center comprising:
• a coordination server, configured to receive configuration and makefile data associated with one of said consumer computing systems, and configured to place said data in a queue, and configured to provide a built module to said one of said consumer computing systems;
• and
• a build server, coupled to said coordination server and corresponding to said configuration data, configured to receive said data from said queue, and configured to generate the built module based on commands within said makefile data, said build server comprising:
• a module build compiler, disposed within a secure root, configured to access a log file, and configured to execute whitelist commands stored therein to generate named object files from proprietary source files for transfer to a public root;
• a wrapper module build compiler, disposed within said public root, configured to extract said whitelist commands from said makefile data to generate said log file, and to rename said named object files into renamed object files according to said whitelist commands;
• and
• a wrapper linker, disposed within said public root, configured to link said renamed object files according to said whitelist commands to generate said built module.

A secure module building method, comprising:

• via a secure module build center, building modules corresponding to consumer computing systems, each of the consumer computing systems running one of a plurality of operating system types and versions, said building comprising:
• via a coordination server, receiving configuration and makefile data associated with one of the consumer computing systems, and placing the data in a queue, and providing a built module to the one of the consumer computing systems;
• and
• via a build server, receiving the data from the queue, and generating a built module based on commands within the makefile data, said generating comprising:
• via a module build compiler disposed within a secure root, accessing a log file, and executing whitelist commands stored therein to generate named object files from proprietary source files for transfer to a public root;
• and
• via a wrapper module build compiler disposed within a public root, extracting said whitelist commands from the makefile data to generate the log file, and renaming the named object files into renamed object files according to the whitelist commands, wherein the renamed object files are provided to a wrapper linker disposed within the public root, and wherein the wrapper linker links the renamed objects files according to the whitelist commands to generate the built module.