Automated and secure module building system

An apparatus for securely building a module for a consumer computing system, the apparatus comprising:

• a coordination server, configured to transmit a module build agent to the consumer computing system, and configured to retrieve configuration and makefile data associated with the consumer computing system, wherein said module build agent executes on the consumer computing system and retrieves said configuration and makefile data, and transmits said configuration and makefile data to said coordination server;
• and
• a build server, coupled to said coordination server and corresponding to said configuration data, configured to build the module based on commands within said makefile data, said build server comprising:
• a secure root, configured to execute whitelist commands to generate named object files from proprietary source files;
• and
• a public root, configured to extract said whitelist commands from said makefile data, to transfer said whitelist commands to said secure root, to receive said named object files, to rename said object files into renamed object files according to said whitelist commands, and to links said renamed object files to generate the module.

A method for securely building a module for a consumer computing system, the method comprising:

• via a coordination server, transmitting a module build agent to the consumer computing system, and receiving configuration and makefile data associated with the consumer computing system, wherein the module build agent executes on the consumer computing system and retrieves the configuration and makefile data, and transmits the configuration and makefile data to the coordination server;
• and
• via a build server, building the module based on commands within the makefile data, said building comprising:
• extracting whitelist commands from the makefile data within a public root of the build server;
• executing the whitelist commands within a secure root of the build server to generate named object files from proprietary source files;
• transferring the named object files to the public root;
• renaming the object files into renamed object files according to the whitelist commands;
• and
• linking the renamed object files to generate the module.