Implementing the TLS Protocol on a Bare PC

Abstract

A bare PC is an ordinary computer that runs applications without an operating system (OS). It thus provides immunity from attacks that target specific OS vulnerabilities while eliminating the OS overhead in a conventional system. We describe a novel implementation of TLS that runs on a bare PC. The TLS implementation differs from a conventional TLS implementation in that it is included within a bare PC application that manages its own CPU tasks, directly interfaces to the hardware, and communicates with network protocols without using a standard socket interface. Furthermore, the unique software architecture of a bare PC enables the TLS, TCP, and application protocols to be intertwined, thereby reducing the communication overhead compared to that of a conventional system. As an example, we give details of the internal architecture of a bare PC TLS Web server. We then illustrate intertwining of the TLS, TCP, and HTTP protocols. In particular, we show how a state transition model that represents events and actions in the TLS Web server is used to develop the intertwined protocol code. We also discuss the testing methodology, note some challenges with respect to implementing TLS on a bare PC, and outline the measures taken to address them.

A Framework for the Implementation of Secure Bare-Based Web-Email System

“…An AO may constitute a single application such as Webmail server or it may consist of composite applications including: Webmail server, Web Browser and a Text-editor. Applications like the Web server [8], Email Server [9][10] VoIP [11] [12] and TLS on web server [13] have been built on Bare PC and these applications demonstrated significant improvements in performance compared to other commercial systems. These applications uncovered the unique features of the Bare PC architecture and served as the bases for the design and implementation of the Bare PC Webmail Server.…”

“…Control is then passed to the Main Task (3). The basic Bare PC data structures used by the Main Task include a Delayed List (16), Resume List (15) and a Multiplexor mechanism (4) that switches between Received Tasks (20) and Resume List Tasks (HTTP, SMTP, POP3, TLS) and selects a running task (13). This running task can be suspended and returned to the Delayed List (16) when it is not being run.…”