Abstract: A processing device may receive a request for dependency information indicative of one or more class files included in an archive file. The processing device may fetch the archive file from an upstream source, where the archive file may be associated with the dependency information indicative of the one or more class files. The processing device may apply a transformation to the archive file to indicate provenance information for each of the one or more class files included in the archive file. The archive file may be incorporated in an application or a library, such that a scan of the application or the library may be performed for the provenance information associated with the archive file. An indication of each of the one or more class files included in the archive file may be output in view of the provenance information.

Abstract: Methods and systems for transforming bytecodes using virtual artifacts are disclosed. In one aspect, a method is provided that includes receiving a build request to convert source code into a first bytecode. A first virtual artifact may be identified within the source code and it may be determined that a local repository does not store the first virtual artifact. A real artifact that corresponds to the first virtual artifact may be retrieved from a centralized repository. A bytecode transformation may be applied to the real artifact to generate a second bytecode and the second bytecode may be added to the first bytecode.

Abstract: Methods and systems for transforming bytecodes using virtual artifacts are disclosed. In one aspect, a method is provided that includes receiving a build request to convert source code into a first bytecode. A first virtual artifact may be identified within the source code and it may be determined that a local repository does not store the first virtual artifact. A real artifact that corresponds to the first virtual artifact may be retrieved from a centralized repository. A bytecode transformation may be applied to the real artifact to generate a second bytecode and the second bytecode may be added to the first bytecode.

Abstract: Methods and systems for transforming bytecodes using virtual artifacts are disclosed. In one aspect, a method is provided that includes receiving a build request to convert source code into a first bytecode. A first virtual artifact may be identified within the source code and it may be determined that a local repository does not store the first virtual artifact. A real artifact that corresponds to the first virtual artifact may be retrieved from a centralized repository. A bytecode transformation may be applied to the real artifact to generate a second bytecode and the second bytecode may be added to the first bytecode.

Abstract: A processing device may receive a request for dependency information indicative of one or more class files included in an archive file. The processing device may fetch the archive file from an upstream source, where the archive file may be associated with the dependency information indicative of the one or more class files. The processing device may apply a transformation to the archive file to indicate provenance information for each of the one or more class files included in the archive file. The archive file may be incorporated in an application or a library, such that a scan of the application or the library may be performed for the provenance information associated with the archive file. An indication of each of the one or more class files included in the archive file may be output in view of the provenance information.

Abstract: Methods and systems for transforming bytecodes using virtual artifacts are disclosed. In one aspect, a method is provided that includes receiving a build request to convert source code into a first bytecode. A first virtual artifact may be identified within the source code and it may be determined that a local repository does not store the first virtual artifact. A real artifact that corresponds to the first virtual artifact may be retrieved from a centralized repository. A bytecode transformation may be applied to the real artifact to generate a second bytecode and the second bytecode may be added to the first bytecode.

Abstract: A secure layer extensions unit identifies a secure layer extension identifier associated with a communication protocol supported by a client device; receives, from a secure sockets layer (SSL) engine, a handshake communication in view of the communication protocol, wherein the handshake communication excludes the secure layer extension identifier; generates a modified handshake communication for the client device that includes the secure layer extension identifier in view of the communication protocol; and forwards the modified handshake communication to the client device.

Abstract: A system includes a memory, a processor in communication with the memory, and a serializer. The serializer is configured to receive an object that includes at least one field, initiate serialization of the object according to a rule set, and write a first intermediate representation of a new object based on the object. The serializer is also configured to write a second intermediate representation to set the at least one field in the new object. Additionally, the serializer is configured to output a serialization of the new object based on the first intermediate representation and the second intermediate representation.

Abstract: A system includes a memory, a processor in communication with the memory, and a serializer. The serializer is configured to receive an object that includes at least one field, initiate serialization of the object according to a rule set, and write a first intermediate representation of a new object based on the object. The serializer is also configured to write a second intermediate representation to set the at least one field in the new object. Additionally, the serializer is configured to output a serialization of the new object based on the first intermediate representation and the second intermediate representation.

Abstract: A secure layer extensions unit identifies a secure layer extension identifier associated with a communication protocol supported by a client device; receives, from a secure sockets layer (SSL) engine, a handshake communication in view of the communication protocol, wherein the handshake communication excludes the secure layer extension identifier; generates a modified handshake communication for the client device that includes the secure layer extension identifier in view of the communication protocol; and forwards the modified handshake communication to the client device.

Abstract: An implementation of the disclosure provides an apparatus comprising: a memory to store a plurality of handshake responses to authenticate client communications; and a processing device, operatively coupled to the memory, to: receive a handshake request from a client device The handshake request comprising an identifier of a communication protocol supported by the client device. A secure layer extension is extracted from the identifier of the communication protocol. Identify, in view of the communication protocol, a handshake response for the client device. The handshake response is modified to include information associated with the secure layer extension. Update a data structure with a hash value generated in view of the modified handshake response. Thereupon, forward the modified handshake response and the hash value to the client device.

Abstract: An implementation of the disclosure provides an apparatus comprising: a memory to store a plurality of handshake responses to authenticate client communications; and a processing device, operatively coupled to the memory, to: receive a handshake request from a client device The handshake request comprising an identifier of a communication protocol supported by the client device. A secure layer extension is extracted from the identifier of the communication protocol. Identify, in view of the communication protocol, a handshake response for the client device. The handshake response is modified to include information associated with the secure layer extension. Update a data structure with a hash value generated in view of the modified handshake response. Thereupon, forward the modified handshake response and the hash value to the client device.