A trusted branded email method and apparatus in one aspect detects branded electronic messages and performs validation before it is sent to a recipient. In another aspect, an electronic messages is branded by embedding branding assets and validation signatures. Algorithms that generate validation signatures are dynamically selected to further strengthen the security aspects. Branding assets are presented to a user using a distinct indicia that represents to the user that the branding assets are secure.

In various implementations, a network device receives a packet from a content producer. The packet includes data and further includes a signature generated by the content producer, based on the data, using a private key of the content producer. The network device modifies the packet without affecting the signature and forwards the modified packet toward a user device. The network device also sends the user device a manifest specifying how the packet was modified. The user device receives the packet and manifest, restores the packet's original data based on the manifest, and verifies the original data using the signature and a public key corresponding to the private key of the content producer. In response to verification of the original data, an application on the user device is allowed to use the data.

Digital document editing techniques as part of electronic signature collection are described. These techniques support a single unified workflow in which comments and edits may be made as part of collecting an electronic signature. In this way, user and computational efficiency may be increased over conventional techniques that require initialization of the electronic signature collection workflow any time a comment or change is to be made to a digital document. Further, the comments and edits may be incorporated as part of audit trail associated with the electronic signature, thus increasing effectiveness of the electronic signature in providing supporting evidence of signature validity by documenting changes made to the digital document by one or more of the parties that sign the document.

A digital verified identification system and method are presented for verifying and/or authenticating the identification of an entity associated with an electronic file, such as, for example the digital signatory thereof. In particular, the system and method include a module generating assembly structured to receive at least one verification data element, and at least one digital identification module structured to be associated with at least one entity. The digital identification module is capable of being disposed or embedded within at least one electronic file. Further, the digital Identification module with the entity, and one or more metadata identification module includes at least one primary components identification module includes at least one primary component structured to at least partially associate the digital.

Systems, methods, and devices enable a receiver device to determine completeness of low level signaling (LLS) tables received via broadcast transmissions. In various embodiments, broadcast service signaling may include generating a directory table identifying one or more LLS tables to be broadcast and sending the directory table in a broadcast stream of the one or more LLS tables. In various embodiments, broadcast service signaling may include calculating a cyclic redundancy check (CRC) code for, generating a hash value for, and/or applying a digital signature to one or more LLS tables in a broadcast stream.

In general, in one aspect, an installation file digitally signed with a first package signature is received. It is determined whether the received installation file includes a migration signature that covers the first package signature and that matches a second signature associated with an installed software application, to confirm that the received installation file includes a valid update related to the installed software application. The installed software application is updated from the received installation file when the migration signature is included.

Techniques are provided for using tokenization in conjunction with behind-the-wall JWT authentication. Behind-the-wall JWT authentication refers to JWT authentication techniques in which the JWT stays exclusively within the private network that is controlled by the web application provider. Because the JWT stays within the private network, the security risk posed by posting the JWT in a client cookie is avoided. However, because JWT is used behind-the-wall to authenticate a user with the services requested by the user, the authentication-related overhead is significantly reduced.

An information handling system includes a device, a controller, and a license manager subsystem. The controller is configured to determine whether the device has a license assigned and to extract a unique identification for the device in response to a request for information about the device. The license manager subsystem is configured to send the request for information about the device to the controller, to send the unique identification for the device to a license server as a request for the license for the device, to receive the license from the license server, and to assign the license to the device when the license is received.

Embodiments provide verification methods and systems for use in respect of data-oriented blockchain applications. In contrast to conventional signature verification in blockchain protocols, embodiments disclosed herein are performed in-situ within a single transaction, using only data that is provided within that transaction. Therefore, there is no reliance upon signatures provided from other transactions, and potential exploits such as replay attacks can be prevented. In an embodiment, this can be achieved by placing the signature in the output of the transaction rather than the locking script.

An e-mail system is disclosed that overcomes many deficiencies of, but is backward compatible with, existing e-mail systems. Embodiments of the system may include various features, including but not limited to: (1) secure transfer of e-mail messages, without the need for users to replace existing e-mail clients or to change e-mail addresses; (2) tracking of all actions performed in connection with an e-mail transmission; (3) the ability for a recipient to view information about an e-mail message, optionally including information about how other addressees have responded to it, before deciding whether to retrieve the e-mail message; (4) the aggregation of entire e-mail conversations into a single threaded view; (5) the ability to include both private and public messages in a single e-mail communication; (6) sender control over downstream actions performed in connection with an e-mail message; (7) flexible control over cryptographic methods used to encrypt emails messages for storage.