Abstract: An apparatus including a secure module build center, configured generate modules corresponding to consumer computing systems that each run one of a plurality of operating system types and versions. The center has a coordination server that receives configuration and makefile data associated with one of the consumer computing systems, places the data in a queue, and provides a built module to the one of the consumer computing systems; and a build server that receives the data from the queue, and generates the built module based on commands within the makefile data.

Abstract: An apparatus for securely building a module for a consumer computing system, including a coordination server and a build server. The coordination server receives configuration and makefile data associated with the consumer computing system, places the data in a queue, and provides the module to the consumer computing system. The build server corresponds to the configuration data. The build server receives the data from the queue, and builds the module based on commands within the makefile data, where the build server extracts whitelist commands from the makefile data within a public root of the build server, executes the whitelist commands within a secure root of the build server to generate named object files from proprietary source files, transfers the named object files to the public root, renames the object files into renamed object files according to the whitelist commands, and links the renamed object files to generate the module.

Abstract: An apparatus for securely building a module for a consumer computing system, including a coordination server and a build server. The coordination server transmits an agent, where the agent executes on the consumer computing system, retrieves configuration and makefile data, and transmits the data back to the coordination server. The build server corresponds to the configuration data. The build server builds the module based on commands within the makefile data, where the build server extracts whitelist commands from the makefile data within a public root of the build server, executes the whitelist commands within a secure root of the build server to generate named object files from proprietary source files, transfers the named object files to the public root, renames the object files into renamed object files according to the whitelist commands, and links the renamed object files to generate the module.

Abstract: An apparatus for securely building a module for a consumer computing system, including a coordination server and a build server. The coordination server receives configuration and makefile data associated with the consumer computing system, places the data in a queue, and provides the module to the consumer computing system. The build server corresponds to the configuration data. The build server receives the data from the queue, and builds the module based on commands within the makefile data, where the build server extracts whitelist commands from the makefile data within a public root of the build server, executes the whitelist commands within a secure root of the build server to generate named object files from proprietary source files, transfers the named object files to the public root, renames the object files into renamed object files according to the whitelist commands, and links the renamed object files to generate the module.

Abstract: An apparatus including a secure module build center, configured generate modules corresponding to consumer computing systems that each run one of a plurality of operating system types and versions. The center has a coordination server that receives configuration and makefile data associated with one of the consumer computing systems, places the data in a queue, and provides a built module to the one of the consumer computing systems; and a build server that receives the data from the queue, and generates the built module based on commands within the makefile data.

Abstract: An apparatus for securely building a module for a consumer computing system, including a coordination server and a build server. The coordination server transmits an agent, where the agent executes on the consumer computing system, retrieves configuration and makefile data, and transmits the data back to the coordination server. The build server corresponds to the configuration data. The build server builds the module based on commands within the makefile data, where the build server extracts whitelist commands from the makefile data within a public root of the build server, executes the whitelist commands within a secure root of the build server to generate named object files from proprietary source files, transfers the named object files to the public root, renames the object files into renamed object files according to the whitelist commands, and links the renamed object files to generate the module.