EP3930253A1 - High throughput post quantum aes-gcm engine for tls packet encryption and decryption - Google Patents

High throughput post quantum aes-gcm engine for tls packet encryption and decryption Download PDF

Info

Publication number
EP3930253A1
EP3930253A1 EP20205013.4A EP20205013A EP3930253A1 EP 3930253 A1 EP3930253 A1 EP 3930253A1 EP 20205013 A EP20205013 A EP 20205013A EP 3930253 A1 EP3930253 A1 EP 3930253A1
Authority
EP
European Patent Office
Prior art keywords
compute
galois field
aes
authentication key
section
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP20205013.4A
Other languages
German (de)
English (en)
French (fr)
Inventor
Manoj Sastry
Santosh Ghosh
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Intel Corp
Original Assignee
Intel Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intel Corp filed Critical Intel Corp
Publication of EP3930253A1 publication Critical patent/EP3930253A1/en
Withdrawn legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/06—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols the encryption apparatus using shift registers or memories for block-wise or stream coding, e.g. DES systems or RC4; Hash functions; Pseudorandom sequence generators
    • H04L9/0618—Block ciphers, i.e. encrypting groups of characters of a plain text message using fixed encryption transformation
    • H04L9/0631—Substitution permutation network [SPN], i.e. cipher composed of a number of stages or rounds each involving linear and nonlinear transformations, e.g. AES algorithms
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06N—COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
    • G06N10/00—Quantum computing, i.e. information processing based on quantum-mechanical phenomena
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/16—Implementing security features at a particular protocol layer
    • H04L63/166—Implementing security features at a particular protocol layer at the transport layer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/06—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols the encryption apparatus using shift registers or memories for block-wise or stream coding, e.g. DES systems or RC4; Hash functions; Pseudorandom sequence generators
    • H04L9/0618—Block ciphers, i.e. encrypting groups of characters of a plain text message using fixed encryption transformation
    • H04L9/0637—Modes of operation, e.g. cipher block chaining [CBC], electronic codebook [ECB] or Galois/counter mode [GCM]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0816—Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
    • H04L9/0852—Quantum cryptography
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0861—Generation of secret information including derivation or calculation of cryptographic keys or passwords
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
    • H04L2209/12—Details relating to cryptographic hardware or logic circuitry
    • H04L2209/125—Parallelization or pipelining, e.g. for accelerating processing of cryptographic operations

Definitions

  • Subject matter described herein relates generally to the field of computer security and more particularly to a high throughput post quantum advanced encrypt standard Galois/Counter mode (AES-GCM) engine for transport layer security (TLS) packet encryption and/or decryption.
  • AES-GCM high throughput post quantum advanced encrypt standard Galois/Counter mode
  • TLS transport layer security
  • Transport Layer Security is a known protocol used for protecting network traffic. Recently, TLS has been equipped with post-quantum security to make this protocol robust against attacks by quantum computers.
  • BIKE Bit Flipping Key Encapsulation
  • SIKE Supersingular Isogeny Key Encapsulation
  • AES-GCM Galois/Counter mode
  • TLS transport layer security
  • AES-GCM Galois/Counter mode
  • TLS transport layer security
  • Fig. 1 is a schematic illustration of a processing environment in which systems and methods for a high throughput post quantum advanced encrypt standard Galois/Counter mode (AES-GCM) engine for transport layer security (TLS) packet encryption and/or decryption may be implemented, according to embodiments.
  • a system 100 may comprise a compute platform 120.
  • compute platform 120 includes one or more host computer servers for providing cloud computing services.
  • Compute platform 120 may include (without limitation) server computers (e.g., cloud server computers, etc.), desktop computers, cluster-based computers, set-top boxes (e.g., Internet-based cable television set-top boxes, etc.), etc.
  • Compute platform 120 includes an operating system ("OS") 106 serving as an interface between one or more hardware/physical resources of compute platform 120 and one or more client devices 130A-130N, etc.
  • Compute platform 120 further includes processor(s) 102, memory 104, input/output (“I/O") sources 108, such as touchscreens, touch panels, touch pads, virtual or regular keyboards, virtual or regular mice, etc.
  • OS operating system
  • I/O input/output
  • host organization 101 may further employ a production environment that is communicably interfaced with client devices 130A-N through host organization 101.
  • Client devices 130A-N may include (without limitation) customer organization-based server computers, desktop computers, laptop computers, mobile compute platforms, such as smartphones, tablet computers, personal digital assistants, e-readers, media Internet devices, smart televisions, television platforms, wearable devices (e.g., glasses, watches, bracelets, smartcards, jewelry, clothing items, etc.), media players, global positioning system -based navigation systems, cable setup boxes, etc.
  • the illustrated database system 150 includes database(s) 140 to store (without limitation) information, relational tables, datasets, and underlying database records having tenant and user data therein on behalf of customer organizations 121A-N (e.g., tenants of database system 150 or their affiliated users).
  • a client-server computing architecture may be utilized in place of database system 150, or alternatively, a computing grid, or a pool of work servers, or some combination of hosted computing architectures may be utilized to carry out the computational workload and processing that is expected of host organization 101.
  • the illustrated database system 150 is shown to include one or more of underlying hardware, software, and logic elements 145 that implement, for example, database functionality and a code execution environment within host organization 101.
  • database system 150 further implements databases 140 to service database queries and other data interactions with the databases 140.
  • hardware, software, and logic elements 145 of database system 150 and its other elements, such as a distributed file store, a query interface, etc. may be separate and distinct from customer organizations (121A-121N) which utilize the services provided by host organization 101 by communicably interfacing with host organization 101 via network(s) 135 (e.g., cloud network, the Internet, etc.).
  • network(s) 135 e.g., cloud network, the Internet, etc.
  • host organization 101 may implement on-demand services, on-demand database services, cloud computing services, etc., to subscribing customer organizations 121A-121N.
  • host organization 101 receives input and other requests from a plurality of customer organizations 121A-N over one or more networks 135; for example, incoming search queries, database queries, application programming interface ("API") requests, interactions with displayed graphical user interfaces and displays at client devices 130A-N, or other inputs may be received from customer organizations 121A-N to be processed against database system 150 as queries via a query interface and stored at a distributed file store, pursuant to which results are then returned to an originator or requestor, such as a user of client devices 130A-N at any of customer organizations 121A-N.
  • API application programming interface
  • each customer organization 121A-N may include an entity selected from a group consisting of a separate and distinct remote organization, an organizational group within host organization 101, a business partner of host organization 101, a customer organization 121A-N that subscribes to cloud computing services provided by host organization 101, etc.
  • requests are received at, or submitted to, a server within host organization 101.
  • Host organization 101 may receive a variety of requests for processing by host organization 101 and its database system 150.
  • incoming requests received at the server may specify which services from host organization 101 are to be provided, such as query requests, search request, status requests, database transactions, graphical user interface requests and interactions, processing requests to retrieve, update, or store data on behalf of one of customer organizations 121A-N, code execution requests, and so forth.
  • the server at host organization 101 may be responsible for receiving requests from various customer organizations 121A-N via network(s) 135 on behalf of the query interface and for providing a web-based interface or other graphical displays to one or more end-user client devices 130A-N or machines originating such data requests.
  • host organization 101 may implement a request interface via the server or as a stand-alone interface to receive requests packets or other requests from the client devices 130A-N.
  • the request interface may further support the return of response packets or other replies and responses in an outgoing direction from host organization 101 to one or more client devices 130A-N.
  • Fig. 2 is a simplified block diagram of an example system including an example host system compute platform 120 supporting trusted execution aware hardware debug and manageability in accordance with an embodiment.
  • a compute platform 120 can include one or more processor devices 205, one or more memory elements 210, and other components implemented in hardware and/or software, including an operating system 215 and a set of applications (e.g., 220, 225, 230.
  • applications e.g., 220, 225, 230.
  • One or more of the applications may be implemented in a trusted execution environment secured using, for example, a secure enclave 235, or application enclave.
  • Secure enclaves can be implemented using secure memory 240 (as opposed to general memory 245) and utilizing secured processing functionality of at least one of the processors (e.g., 205) of the compute platform 120 to implement private regions of code and data to provide secured or protected execution of the application.
  • Logic implemented in firmware and/or software of the compute platform (such as code of the CPU of the host), can be provided on the compute platform 120 that can be utilized by applications or other code local to the compute platform to set aside private regions of code and data, which are subject to guarantees of heightened security, to implement one or more secure enclaves on the system.
  • a secure enclave can be used to protect sensitive data from unauthorized access or modification by rogue software running at higher privilege levels and preserve the confidentiality and integrity of sensitive code and data without disrupting the ability of legitimate system software to schedule and manage the use of platform resources.
  • Secure enclaves can enable applications to define secure regions of code and data that maintain confidentiality even when an attacker has physical control of the platform and can conduct direct attacks on memory.
  • Secure enclaves can further allow consumers of the host devices (e.g., compute platform 120) to retain control of their platforms including the freedom to install and uninstall applications and services as they choose.
  • Secure enclaves can also enable compute platform 200 to take measurements of an application's trusted code and produce a signed attestation, rooted in the processor, that includes this measurement and other certification that the code has been correctly initialized in a trustable execution environment (and is capable of providing the security features of a secure enclave, such as outlined in the examples above).
  • an application enclave (e.g., 235) can protect all or a portion of a given application 230 and allow for attestation of the application 230 and its security features.
  • a service provider in backend system 280 such as a backend service or web service, may prefer or require that clients with which it interfaces, possess certain security features or guarantees, such that the backend system 280 can verify that it is transacting with who it the client says it is.
  • malware e.g., 305
  • malware can sometimes be constructed to spoof the identity of a user or an application in an attempt to extract sensitive data from, infect, or otherwise behave maliciously in a transaction with the backend system 280.
  • Signed attestation can allow an application (e.g., 230) to verify that it is a legitimate instance of the application (i.e., and not malware).
  • Other applications e.g., 220
  • compute platform platforms e.g., 200
  • emulator 310 can be emulated (e.g., by emulator 310) to attempt to transact falsely with the backend system 280. Attestation through a secure enclave can guard against such insecure, malicious, and faulty transactions.
  • attestation can be provided on the basis of a signed piece of data, or "quote,” that is signed using an attestation key securely provisioned on the platform.
  • Additional secured enclaves can be provided (i.e., separate from the secure application enclave 235) to measure or assess the application and its enclave 235, sign the measurement (included in the quote), and assist in the provisioning of one or more of the enclaves with keys for use in signing the quote and established secured communication channels between enclaves or between an enclave and an outside service (e.g., backend system 280, attestation system 105, provisioning system 130, backend system 140).
  • backend system 280 e.g., attestation system 105, provisioning system 130, backend system 140.
  • one or more provisioning enclaves 255 can be provided to interface with a corresponding provisioning system to obtain attestation keys for use by a quoting enclave 255 and/or application enclave.
  • One or more quoting enclaves 255 can be provided to reliably measure or assess an application 230 and/or the corresponding application enclave 235 and sign the measurement with the attestation key obtained through the corresponding provisioning enclave 250.
  • a provisioning certification enclave 260 may also be provided to authenticate a provisioning enclave (e.g., 250) to its corresponding provisioning system (e.g., 120).
  • the provisioning certification enclave 260 can maintain a provisioning attestation key that is based on a persistently maintained, secure secret on the host platform 200, such as a secret set in fuses 265 of the platform during manufacturing, to support attestation of the trustworthiness of the provisioning enclave 250 to the provisioning system 290, such that the provisioning enclave 250 is authenticated prior to the provisioning system 290 entrusting the provisioning enclave 250 with an attestation key.
  • the provisioning certification enclave 260 can attest to authenticity and security of any one of potentially multiple provisioning enclaves 250 provided on the platform 200.
  • multiple different provisioning enclaves 250 can be provided, each interfacing with its own respective provisioning system, providing its own respective attestation keys to one of potentially multiple quoting enclaves (e.g., 255) provided on the platform.
  • quoting enclaves e.g. 255
  • different application enclaves can utilize different quoting enclaves during attestation of the corresponding application, and each quoting enclave can utilize a different attestation key to support the attestation, e,g., via an attestation system 105.
  • provisioning enclaves 250 and provisioning services provided, e.g., by one or more provisioning systems 130, different key types and encryption technologies can be used in connection with the attestation of different applications and services (e.g., hosted by backend systems 280).
  • one or more applications and quoting enclaves can utilize keys generated by a key generation enclave 270 provided on the platform.
  • the provisioning certification enclave can sign the key (e.g., the public key of a key pair generated randomly by the key generation enclave) such that quotes signed by the key can be identified as legitimately signed quotes.
  • key generation enclaves e.g., 270
  • provisioning enclaves e.g., 250
  • key generation enclaves e.g., 270
  • provisioning enclaves e.g., 250
  • key generation enclaves and provisioning enclaves can be provided as alternatives for the other (e.g., with only a key generation enclave or provisioning enclaves be provided on a given platform), among other examples and implementations.
  • Transport Layer Security is a known protocol used for protecting network traffic. Recently, TLS has been equipped with post-quantum security to make this protocol robust against attacks by quantum computers.
  • BIKE Bit Flipping Key Encapsulation
  • SIKE Supersingular Isogeny Key Encapsulation
  • an AES-GCM pipeline engine may be constructed pursuant to the following principles to address key challenges.
  • an authentication key (h) for tag computation in the GCM is derived from the encryption key (k).
  • Some existing systems compute h prior to encryption and tag generation through a handshake protocol between the host and the crypto engine, which adds a significant latency overhead for context switching.
  • Systems described herein are capable to compute h on the fly for every input data-block that hides this latency with data encryption latency and provides ability of context switch in every clock.
  • the TCP packets within a connection may carry variable-sized TLS payload (e.g., 60-byte).
  • variable-sized TLS payload e.g. 60-byte.
  • Some existing solutions operate on static intermediate input block size (multiple of 16-byte AES block) incurring additional computation/latency overhead.
  • Systems described herein are capable to, based on input block size (ranging from 1-byte to 64-byte), reconfigure the pipeline with automatic padding to perform encryption and partial tag computation.
  • Fig. 4 is a schematic illustration of an architecture to implement a high throughput post quantum advanced encrypt standard Galois/Counter mode (AES-GCM) engine for transport layer security (TLS) packet encryption and/or decryption, in accordance with some examples.
  • AES-GCM Galois/Counter mode
  • TLS transport layer security
  • one example of an engine 400 comprises a pipelined architecture with eighteen (18) internal stages. More particularly, engine 400 comprises an input register 410 to receive a series of inputs. A key to the inputs is provided in Table 1.
  • Engine 400 further comprises intermediate pipeline stages 2-13 425 and final last-round stage 435.
  • Each stage is communicatively coupled to a register to store output data.
  • stage 1 415 is communicatively coupled to stage 1 register 420
  • stage 13 is communicatively coupled to stage 13 register 430
  • stage 14 435 is communicatively couple to stage 14 register 440
  • stage 15 445 is communicatively coupled to stage 15 register 450
  • stage 16 455 is communicatively coupled to stage 16 register 460
  • stage 17 465 is communicatively coupled to stage 17 register 470
  • stage 18 475 is communicatively coupled to output register 480.
  • Pipeline stages 1 to 14 implement AES256 encryption and/or decryiption in round-1 to round-14 respectively.
  • the pipeline architecture has six (6) parallel AES256 round-1 to round-14 data paths, four (4) of which are used for up to 64-byte data encryption/decryption, one of which is used to compute authentication key (h) and another one is used for computing the authentication tag mask E k (c 1 ).
  • the engine 400 receives up to 64-byte input data, a 16-byte Additional Authentication Data (AAD), a 32-byte encryption key, a 16-byte counter value and related control signals as inputs in every cycle and passes the inputs through pipeline with changing clock cycles.
  • AAD Additional Authentication Data
  • Pipeline stage 15 comprises one combinatorial GF(2128) multiplier that computes h 2 and places the outputs in register 450.
  • Pipeline stage 16 comprises two combinatorial GF(2 128 ) multipliers that compute h 3 and h 4 .
  • Pipeline stage 17 comprises four combinatorial GF(2 128 ) multipliers to compute (pat x h 4 , d1 x h 3 , d2 x h 2 , d3 x h), where pat represents a partial authentication tag which is initialized to zero for a new TLS record and it holds the intermediate tag value up to the last data block processed by the AES-GCM engine, d 1 , d 2 , d 3 represent corresponding 16-byte data blocks from left to write within 64-byte data input.
  • This new pat value is further multiplied with h 2 to compute the final tag if the current block in 401 is indicated as the final/last data block of a TLS record.
  • the new pat value and the key id associated with it are feedback to all prior pipeline stages where it replaces the respective existing pat value if the feedback key_id matches with the respective key_id of each stage.
  • the encrypt signal indicates the Encryption or Decryption mode of operations. The last in input signal indicates that no more data to process so generate the final tag for this TLS record identified by the respective input kid.
  • the engine 400 supports a 16-byte AAD, which is applied to the engine only once per connection with first valid data block. To accommodate large numbers of simultaneous connections/TLS-records the engine supports zero-delay context switch among connections. Each connection is associated with different key and key id. Sometimes it is required to resume a connection which was idle for a while. To support that, the engine 400 generates the partially computed tag (or pat) which is stored by the driver/HW-wrapper along with the respective key_id. At resume, the driver provides the stored pat to the engine with new valid blocks.
  • Fig. 5 is a flow diagram illustrating operations in a method to implement a high throughput post quantum advanced encrypt standard Galois/Counter mode (AES-GCM) engine for transport layer security (TLS) packet encryption and/or decryption, in accordance with some examples.
  • AES-GCM high throughput post quantum advanced encrypt standard Galois/Counter mode
  • TLS transport layer security
  • the engine 400 receives TLS packet(s) and signaling in input register 410.
  • the engine 400 performs encryption/decryption operations on data received in the packets, computes the authentication key (h), and computes the authentication tag mask (E k (c 1 )). As described above, these operations may be implemented by the AES256 engines in stages 1-14 of the pipeline.
  • the engine computes a first multiple of the authentication key (h 2 ), a second multiple of authentication key (h 3 ), and a third multiple of authentication key (h 4 ). As described above, these operations may be implemented by the AES256 engines in stages 15-16 of the pipeline. At operation 525 the engine computes a first partial authentication tag. As described above, these operations may be implemented by stage 17 of the pipeline.
  • the pipeline computes a second partial authentication tag (pat), which is provided as feedback to previous stages of the pipeline, along with the key_id.
  • the pipeline multiplies the record length by the authentication key (h) and computes the final authentication tag ("pat” also called as "pad”).
  • the encrypted/decrypted data and output signals are pushed to the output register 480 of the pipeline. As described above, these operations may be implemented by stage 18 of the pipeline.
  • the pipeline as described herein may implement a 64-byte/clock AES-GCM Encrypt and Decrypt which consumes four 16-byte blocks as input and forms the 64-byte block as: ⁇ di_in, d 2_ in, d 3_ in, d 4_ in ⁇ where d 1_ in is positioned in the most significant position.
  • the pipeline exhibits substantially zero setup latency. It can be fed data, IV, counter, key, AAD, pat, encrypt, etc. in every clock for the same or different flows identified by key id (kid_in).
  • the pipeline supports variable number of running flows.
  • the pipeline supports an individual block valid mode to process data in 16-byte granularity. The pipeline receives a 4-bit valid_in, each bit is associated with respective 16-byte data; i.e.., valid_in[3:0] for ⁇ di_in, d 2_ in, d 3_ in, d 4_ in ⁇ .
  • Fig. 6 is a schematic illustration of partial block support in in a method to implement a high throughput post quantum advanced encrypt standard Galois/Counter mode (AES-GCM) engine for transport layer security (TLS) packet encryption and/or decryption, in accordance with some examples.
  • AES-GCM Galois/Counter mode
  • TLS transport layer security
  • the pipeline can encrypt packets with any size and without delaying to form a full 16-byte aligned block.
  • cycle M 600 includes four data blocks 612, 614, 616, 618 and cycle N includes four data blocks 622, 624, 626, 628.
  • unused parts of the partial block 614 will set to zero and it is not required to set this block as partial_block.
  • the same block counter value e.g., block 3
  • the cycle-n partial_in input is to set to 1.
  • the partial block is the block located as the least significant valid block, whereas in cycle-n the rest of the part of the partial block will be placed in the most significant position.
  • Fig. 7 illustrates an embodiment of an exemplary computing architecture that may be suitable for implementing various embodiments as previously described.
  • the computing architecture 700 may comprise or be implemented as part of an electronic device.
  • the computing architecture 700 may be representative, for example of a computer system that implements one or more components of the operating environments described above.
  • computing architecture 700 may be representative of one or more portions or components of a DNN training system that implement one or more techniques described herein. The embodiments are not limited in this context.
  • a component can be, but is not limited to being, a process running on a processor, a processor, a hard disk drive, multiple storage drives (of optical and/or magnetic storage medium), an object, an executable, a thread of execution, a program, and/or a computer.
  • a component can be, but is not limited to being, a process running on a processor, a processor, a hard disk drive, multiple storage drives (of optical and/or magnetic storage medium), an object, an executable, a thread of execution, a program, and/or a computer.
  • an application running on a server and the server can be a component.
  • One or more components can reside within a process and/or thread of execution, and a component can be localized on one computer and/or distributed between two or more computers. Further, components may be communicatively coupled to each other by various types of communications media to coordinate operations. The coordination may involve the uni-directional or bi-directional exchange of information. For instance, the components may communicate information in the form of signals communicated over the communications media. The information can be implemented as signals allocated to various signal lines. In such allocations, each message is a signal. Further embodiments, however, may alternatively employ data messages. Such data messages may be sent across various connections. Exemplary connections include parallel interfaces, serial interfaces, and bus interfaces.
  • the computing architecture 700 includes various common computing elements, such as one or more processors, multi-core processors, co-processors, memory units, chipsets, controllers, peripherals, interfaces, oscillators, timing devices, video cards, audio cards, multimedia input/output (I/O) components, power supplies, and so forth.
  • processors multi-core processors
  • co-processors memory units
  • chipsets controllers
  • peripherals peripherals
  • oscillators oscillators
  • timing devices video cards, audio cards, multimedia input/output (I/O) components, power supplies, and so forth.
  • the embodiments are not limited to implementation by the computing architecture 700.
  • the computing architecture 700 includes one or more processors 702 and one or more graphics processors 708, and may be a single processor desktop system, a multiprocessor workstation system, or a server system having a large number of processors 702 or processor cores 707.
  • the system 700 is a processing platform incorporated within a system-on-a-chip (SoC or SOC) integrated circuit for use in mobile, handheld, or embedded devices.
  • SoC system-on-a-chip
  • An embodiment of system 700 can include, or be incorporated within a server-based gaming platform, a game console, including a game and media console, a mobile gaming console, a handheld game console, or an online game console.
  • system 700 is a mobile phone, smart phone, tablet computing device or mobile Internet device.
  • Data processing system 700 can also include, couple with, or be integrated within a wearable device, such as a smart watch wearable device, smart eyewear device, augmented reality device, or virtual reality device.
  • data processing system 700 is a television or set top box device having one or more processors 702 and a graphical interface generated by one or more graphics processors 708.
  • the one or more processors 702 each include one or more processor cores 707 to process instructions which, when executed, perform operations for system and user software.
  • each of the one or more processor cores 707 is configured to process a specific instruction set 709.
  • instruction set 709 may facilitate Complex Instruction Set Computing (CISC), Reduced Instruction Set Computing (RISC), or computing via a Very Long Instruction Word (VLIW).
  • Multiple processor cores 707 may each process a different instruction set 709, which may include instructions to facilitate the emulation of other instruction sets.
  • Processor core 707 may also include other processing devices, such a Digital Signal Processor (DSP).
  • DSP Digital Signal Processor
  • the processor 702 includes cache memory 704. Depending on the architecture, the processor 702 can have a single internal cache or multiple levels of internal cache. In some embodiments, the cache memory is shared among various components of the processor 702. In some embodiments, the processor 702 also uses an external cache (e.g., a Level-3 (L3) cache or Last Level Cache (LLC)) (not shown), which may be shared among processor cores 707 using known cache coherency techniques.
  • L3 cache Level-3
  • LLC Last Level Cache
  • a register file 706 is additionally included in processor 702 which may include different types of registers for storing different types of data (e.g., integer registers, floating point registers, status registers, and an instruction pointer register). Some registers may be general-purpose registers, while other registers may be specific to the design of the processor 702.
  • one or more processor(s) 702 are coupled with one or more interface bus(es) 710 to transmit communication signals such as address, data, or control signals between processor 702 and other components in the system.
  • the interface bus 710 can be a processor bus, such as a version of the Direct Media Interface (DMI) bus.
  • processor busses are not limited to the DMI bus, and may include one or more Peripheral Component Interconnect buses (e.g., PCI, PCI Express), memory busses, or other types of interface busses.
  • the processor(s) 702 include an integrated memory controller 716 and a platform controller hub 730.
  • the memory controller 716 facilitates communication between a memory device and other components of the system 700, while the platform controller hub (PCH) 730 provides connections to I/O devices via a local I/O bus.
  • PCH platform controller hub
  • Memory device 720 can be a dynamic random-access memory (DRAM) device, a static random-access memory (SRAM) device, flash memory device, phase-change memory device, or some other memory device having suitable performance to serve as process memory.
  • the memory device 720 can operate as system memory for the system 700, to store data 722 and instructions 721 for use when the one or more processors 702 executes an application or process.
  • Memory controller hub 716 also couples with an optional external graphics processor 712, which may communicate with the one or more graphics processors 708 in processors 702 to perform graphics and media operations.
  • a display device 711 can connect to the processor(s) 702.
  • the display device 711 can be one or more of an internal display device, as in a mobile electronic device or a laptop device or an external display device attached via a display interface (e.g., DisplayPort, etc.).
  • the display device 711 can be a head mounted display (HMD) such as a stereoscopic display device for use in virtual reality (VR) applications or augmented reality (AR) applications.
  • HMD head mounted display
  • the platform controller hub 730 enables peripherals to connect to memory device 720 and processor 702 via a high-speed I/O bus.
  • the I/O peripherals include, but are not limited to, an audio controller 746, a network controller 734, a firmware interface 728, a wireless transceiver 726, touch sensors 725, a data storage device 724 (e.g., hard disk drive, flash memory, etc.).
  • the data storage device 724 can connect via a storage interface (e.g., SATA) or via a peripheral bus, such as a Peripheral Component Interconnect bus (e.g., PCI, PCI Express).
  • the touch sensors 725 can include touch screen sensors, pressure sensors, or fingerprint sensors.
  • the wireless transceiver 726 can be a Wi-Fi transceiver, a Bluetooth transceiver, or a mobile network transceiver such as a 3G, 4G, or Long Term Evolution (LTE) transceiver.
  • the firmware interface 728 enables communication with system firmware, and can be, for example, a unified extensible firmware interface (UEFI).
  • the network controller 734 can enable a network connection to a wired network.
  • a high-performance network controller (not shown) couples with the interface bus 710.
  • the audio controller 746 in one embodiment, is a multi-channel high definition audio controller.
  • the system 700 includes an optional legacy I/O controller 740 for coupling legacy (e.g., Personal System 2 (PS/2)) devices to the system.
  • legacy e.g., Personal System 2 (PS/2)
  • the platform controller hub 730 can also connect to one or more Universal Serial Bus (USB) controllers 742 connect input devices, such as keyboard and mouse 743 combinations, a camera 744, or other USB input devices.
  • USB Universal Serial Bus
  • logic instructions as referred to herein relates to expressions which may be understood by one or more machines for performing one or more logical operations.
  • logic instructions may comprise instructions which are interpretable by a processor compiler for executing one or more operations on one or more data objects.
  • this is merely an example of machine-readable instructions and examples are not limited in this respect.
  • a computer readable medium may comprise one or more storage devices for storing computer readable instructions or data.
  • Such storage devices may comprise storage media such as, for example, optical, magnetic or semiconductor storage media.
  • this is merely an example of a computer readable medium and examples are not limited in this respect.
  • logic as referred to herein relates to structure for performing one or more logical operations.
  • logic may comprise circuitry which provides one or more output signals based upon one or more input signals.
  • Such circuitry may comprise a finite state machine which receives a digital input and provides a digital output, or circuitry which provides one or more analog output signals in response to one or more analog input signals.
  • Such circuitry may be provided in an application specific integrated circuit (ASIC) or field programmable gate array (FPGA).
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • logic may comprise machine-readable instructions stored in a memory in combination with processing circuitry to execute such machine-readable instructions.
  • Some of the methods described herein may be embodied as logic instructions on a computer-readable medium. When executed on a processor, the logic instructions cause a processor to be programmed as a special-purpose machine that implements the described methods.
  • the processor when configured by the logic instructions to execute the methods described herein, constitutes structure for performing the described methods.
  • the methods described herein may be reduced to logic on, e.g., a field programmable gate array (FPGA), an application specific integrated circuit (ASIC) or the like.
  • FPGA field programmable gate array
  • ASIC application specific integrated circuit
  • Coupled may mean that two or more elements are in direct physical or electrical contact.
  • coupled may also mean that two or more elements may not be in direct contact with each other, but yet may still cooperate or interact with each other.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Hardware Design (AREA)
  • Electromagnetism (AREA)
  • Computational Mathematics (AREA)
  • Condensed Matter Physics & Semiconductors (AREA)
  • Data Mining & Analysis (AREA)
  • Evolutionary Computation (AREA)
  • Artificial Intelligence (AREA)
  • Mathematical Analysis (AREA)
  • Mathematical Optimization (AREA)
  • Pure & Applied Mathematics (AREA)
  • Mathematical Physics (AREA)
  • Software Systems (AREA)
  • Storage Device Security (AREA)
EP20205013.4A 2020-06-23 2020-10-30 High throughput post quantum aes-gcm engine for tls packet encryption and decryption Withdrawn EP3930253A1 (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US16/909,648 US11489661B2 (en) 2020-06-23 2020-06-23 High throughput post quantum AES-GCM engine for TLS packet encryption and decryption

Publications (1)

Publication Number Publication Date
EP3930253A1 true EP3930253A1 (en) 2021-12-29

Family

ID=73043108

Family Applications (1)

Application Number Title Priority Date Filing Date
EP20205013.4A Withdrawn EP3930253A1 (en) 2020-06-23 2020-10-30 High throughput post quantum aes-gcm engine for tls packet encryption and decryption

Country Status (3)

Country Link
US (1) US11489661B2 (zh)
EP (1) EP3930253A1 (zh)
CN (1) CN113839770A (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11489661B2 (en) 2020-06-23 2022-11-01 Intel Corporation High throughput post quantum AES-GCM engine for TLS packet encryption and decryption

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11836514B2 (en) * 2021-01-19 2023-12-05 Dell Products L.P. System and method of utilizing memory medium fault resiliency with secure memory medium portions
CN116488795B (zh) * 2023-06-19 2023-09-22 北京大禹智芯科技有限公司 一种gcm-aes处理方法和装置

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120011351A1 (en) * 2010-07-08 2012-01-12 Texas Instruments Incorporated Security Processing Engines, Circuits and Systems and Adaptive Processes and Other Processes

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8577026B2 (en) * 2010-12-29 2013-11-05 Ternarylogic Llc Methods and apparatus in alternate finite field based coders and decoders
KR100715679B1 (ko) * 2005-12-05 2007-05-09 한국전자통신연구원 인증 암호화를 통해 보안 전송을 가능하게 하는 ｇｐｏｎ시스템 및 그 인증 암호화 방법
US10103873B2 (en) * 2016-04-01 2018-10-16 Intel Corporation Power side-channel attack resistant advanced encryption standard accelerator processor
US11386017B2 (en) * 2018-06-20 2022-07-12 Intel Corporation Technologies for secure authentication and programming of accelerator devices
US11469902B2 (en) * 2019-03-29 2022-10-11 Intel Corporation Systems and methods of using cryptographic primitives for error location, correction, and device recovery
US11489661B2 (en) 2020-06-23 2022-11-01 Intel Corporation High throughput post quantum AES-GCM engine for TLS packet encryption and decryption

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120011351A1 (en) * 2010-07-08 2012-01-12 Texas Instruments Incorporated Security Processing Engines, Circuits and Systems and Adaptive Processes and Other Processes

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"Progress in cryptology - INDOCRYPT 2004 : 5th International Conference on Cryptology in India, Chennai, India, December 20 - 22, 2004 ; proceedings", vol. 3348, 1 January 2005, BERLIN [U.A.] : SPRINGER, DE, ISBN: 978-3-540-24130-0, article DAVID A MCGREW ET AL: "The Galois/Counter Mode of Operation (GCM", pages: 343 - 355, XP055537225 *
KEVIN BRSTINGHAUS-STEINBACH ET AL: "Post-Quantum TLS on Embedded Systems", vol. 20200312:151206, 11 March 2020 (2020-03-11), pages 1 - 12, XP061035433, Retrieved from the Internet <URL:http://eprint.iacr.org/2020/308.pdf> [retrieved on 20200311] *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11489661B2 (en) 2020-06-23 2022-11-01 Intel Corporation High throughput post quantum AES-GCM engine for TLS packet encryption and decryption

Also Published As

Publication number Publication date
US11489661B2 (en) 2022-11-01
US20210399876A1 (en) 2021-12-23
CN113839770A (zh) 2021-12-24

Similar Documents

Publication Publication Date Title
US11088846B2 (en) Key rotating trees with split counters for efficient hardware replay protection
US11651092B2 (en) Techniques to provide client-side security for storage of data in a network environment
US20220027288A1 (en) Technologies for low-latency cryptography for processor-accelerator communication
US11917053B2 (en) Combined SHA2 and SHA3 based XMSS hardware accelerator
TWI715619B (zh) 用於硬體強制單向密碼學的處理器、方法及系統
EP3930253A1 (en) High throughput post quantum aes-gcm engine for tls packet encryption and decryption
US11405213B2 (en) Low latency post-quantum signature verification for fast secure-boot
US20170063532A1 (en) Efficient sharing of hardware encryption pipeline for multiple security solutions
US20200153629A1 (en) Trusted execution aware hardware debug and manageability
WO2017045484A1 (zh) 一种基于xts-sm4的存储加解密方法及装置
EP3757857B1 (en) Device id for memory protection
US20200127850A1 (en) Certifying a trusted platform module without privacy certification authority infrastructure
Arasu et al. A secure coprocessor for database applications
US20220083347A1 (en) Adding cycle noise to enclaved execution environment
EP3886360A1 (en) Robust state synchronization for stateful hash-based signatures
US11722313B2 (en) State synchronization for post-quantum signing facilities
EP4198780A1 (en) Distributed attestation in heterogenous computing clusters
EP4152681A1 (en) Low overhead side channel protection for number theoretic transform
CN113704041A (zh) Fpga设计的安全调试
WO2023107776A1 (en) Efficient hybridization of classical and post-quantum signatures
US20230117518A1 (en) Permutation cipher encryption for processor-accelerator memory mapped input/output communication
US11522678B2 (en) Block cipher encryption for processor-accelerator memory mapped input/output communication
WO2023159458A1 (en) Device runtime update pre-authentication
US20240089083A1 (en) Secure multiparty compute using homomorphic encryption
US20240031164A1 (en) Hybridization of dilithium and falcon for digital signatures

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN PUBLISHED

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

B565 Issuance of search results under rule 164(2) epc

Effective date: 20210412

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20220615

RBV Designated contracting states (corrected)

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

RIC1 Information provided on ipc code assigned before grant

Ipc: H04L 9/32 20060101ALI20220905BHEP

Ipc: H04L 9/06 20060101AFI20220905BHEP

INTG Intention to grant announced

Effective date: 20221004

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20230215