Abstract: An embodiment of the invention provides an apparatus and method for passing metadata in STREAMS modules. The apparatus and method are configured to perform acts including, allocating a STREAMS message in a kernel space, storing data in the data block in the STREAMS message, allocating a buffer space for metadata associated with the data, storing the metadata of the data in the metadata block in the STREAMS message, passing the metadata among STREAMS modules as a part of the STREAMS message, and performing an operation based upon the metadata.

Abstract: An embodiment of the invention provides an apparatus and method for passing metadata in STREAMS modules. The apparatus and method are configured to perform acts including, allocating a STREAMS message in a kernel space, storing data in the data block in the STREAMS message, allocating a buffer space for metadata associated with the data, storing the metadata of the data in the metadata block in the STREAMS message, passing the metadata among STREAMS modules as a part of the STREAMS message, and performing an operation based upon the metadata.

Abstract: Disclosed are a method and apparatus for passing a data packet from a first network to a second network at a kernel level. According to one illustrative embodiment, this is accomplished by receiving a data packet from a first network, storing the data packet in a kernel-space buffer, determining if the data packet needs to be directly passed to the second network and directing the data packet from the kernel-space buffer to the second network when the data packet needs to be directly passed to the second network.

Abstract: An apparatus and method for kernel level modules or drivers identifying message processing functions and for controlling execution of the message processing functions at the stream head, so that the functions are available at the stream head for adapting stream data interpretation, stream execution behavior, and the like in accordance with various system requirements such as requirements of devices or user processes.

Abstract: A STREAMS-based protocol stack is adapted to encrypt and decrypt data flowing through the stack. In a first embodiment, a STREAMS-based module is added to a protocol stack to encrypt and decrypt data flowing through the stack. In a second embodiment, a STREAMS-based encryption multiplexor routes data to and from an encryptor. In a third embodiment, dynamic function registration is used to register cryptographic functions at a stream head. In a fourth embodiment, STREAM-based modules are modified, either by dynamic function replacement or conventional means known in the art, to redirect data flowing between protocol stack layers to an encryptor. Hardware-based and software-based encryptor configurations are disclosed for all embodiments, as well as various methods of identifying cryptographic characteristics, such as cryptographic algorithms, public and private encryption keys, bindings to applications and IP addresses, and the like.

Abstract: An extension to the STREAMS framework, referred to as dynamic function replacement, uses data structures that contain function pointers which allow STREAMS to execute various module or driver functions without requiring framework modification, or understanding what these functions actually do beyond their rudimentary classifications. This provides a simple, yet elegant, mechanism for replacing these function definitions and, hence, changing the execution behavior of STREAMS modules and drivers without requiring the modules or drivers to be rewritten or modified.