Baike.dev
All toolsOnline toolsAI codingTrendingOpen sourceNewsSubmit
Log in
< Back to tools
I

intel-ipsec-mb

> 编程语言
Open source

Intel(R) Multi-Buffer Crypto for IPSec

336 stars0 likes0 views
WebsiteGitHub

About

Intel(R) Multi-Buffer Crypto for IPSec

Intel(R) Multi-Buffer Crypto for IPsec Library

The library provides software crypto acceleration primarily targeting packet processing applications. It can be used for application such as: IPsec, TLS, Wireless (RAN), Cable or MPEG DRM.

The library is hosted on GitHub and is used as software crypto provider in DPDK, Intel(R) QAT Engine and FD.io.

Using crypto interfaces from the above frameworks gives freedom to change providers without subsequent application modifications. The library can also be used directly through its native API.

Key differentiating features:

  • operation chaining (encryption and authentication)
  • advanced cryptographic pipelining
    • job manager with scheduling and dispatching functions
    • API hides underlying implementation details from an application
  • multi-buffer and function stitching innovations
  • low level implementations using latest instruction extensions

Contents

  1. Overview
  2. Processor Extensions
  3. Recommendations
  4. Package Content
  5. Documentation
  6. Compilation
  7. Installation
  8. Security Considerations & Options for Increased Security
  9. Backwards compatibility
  10. Disclaimer (ZUC, KASUMI, SNOW3G)
  11. Legal Disclaimer
  12. FIPS Compliance
  13. DLL Injection

1. Overview

Intel Multi-Buffer Crypto for IPsec Library is highly-optimized software implementations of the core cryptographic processing for IPsec, which provides industry-leading performance on a range of Intel(R) Processors.

For information on how the library works, see the Intel White Paper: "Fast Multi-buffer IPsec Implementations on Intel Architecture Processors". Jim Guilford, Sean Gulley, et. al.

The library also provides post-quantum signature support for ML-DSA-44, ML-DSA-65 and ML-DSA-87 (FIPS 204) through the opaque IMB_ML_DSA handle and the imb_ml_dsa_* API, and post-quantum key-encapsulation support for ML-KEM-512, ML-KEM-768 and ML-KEM-1024 (FIPS 203) through the opaque IMB_ML_KEM handle and the imb_ml_kem_* API. The ML-DSA and ML-KEM implementations are derived from OpenSSL and are licensed under the Apache License 2.0 (see LICENSE.OpenSSL). The library as a whole is BSD 3-Clause licensed except where individual files state otherwise; see the Licenses section of CONTRIBUTING for the licensing model (effective SPDX expression: BSD-3-Clause AND Apache-2.0).

Table 1. List of supported cipher algorithms and their implementations.

…

IMB_ARCH arch; IMB_MGR *p_mgr = alloc_mb_mgr(0);

init_mb_mgr_auto(p_mgr, &arch); /* or init_mb_mgr_sse/avx/avx2/avx512 */

/*

  • check for self-test presence and successful
    • requires library version v1.3 or newer / if (p_mgr->features & IMB_FEATURE_SELF_TEST) { / self-test feature present */ if (p_mgr->features & IMB_FEATURE_SELF_TEST_PASS) { printf("SELF-TEST: PASS\n"); } else { printf("SELF-TEST: FAIL\n");

    } } else { printf("SELF-TEST: N/A (requires library >= v1.3)\n");

}

/* check for initialization self-test error / if (imb_get_errno(p_mgr) == IMB_ERR_SELFTEST) { / self-test error */ exit(EXIT_FAILURE); }


Example registration of self-test callback function:

int self_test_corrupt = 0;

int callback(void *arg, const IMB_SELF_TEST_CALLBACK_DATA *data) { const char *phase = ""; const char *type = ""; const char *descr = "";

    (void) arg;

    if (data != NULL) {
            if (data->phase != NULL)
                    phase = data->phase;
            if (data->type != NULL)
                    type = data->type;
            if (data->descr != NULL)
                    descr = data->descr;
    }

    if (strcmp(phase, IMB_SELF_TEST_PHASE_START) == 0)
            printf("%s : %s : ", type, descr);

    if ((strcmp(phase, IMB_SELF_TEST_PHASE_CORRUPT) == 0) && (self_test_corrupt == 1))
            return 0; /* corrupt input message */

    if (strcmp(phase, IMB_SELF_TEST_PHASE_PASS) == 0 ||
        strcmp(phase, IMB_SELF_TEST_PHASE_FAIL) == 0)
            printf("%s\n", phase);

    return 1;

}

...

IMB_ARCH arch; IMB_MGR *p_mgr = alloc_mb_mgr(0);

/*

  • Register self-test callback that will be invoked during
  • subsequent init operation */ imb_self_test_set_cb(p_mgr, callback, NULL);

init_mb_mgr_auto(p_mgr, &arch); /* or init_mb_mgr_sse/avx/avx2/avx512 */

...


## 13.DLL Injection Attack

### Problem

The Windows OS has an insecure predefined search order and set of defaults when trying to locate a resource. If the resource location is not specified by the software, an attacker need only place a malicious version in one of the locations Windows will search, and it will be loaded instead. Although this weakness can occur with any resource, it is especially common with DLL files.

### Solutions

Applications using intel-ipsec-mb DLL library may need to apply one of the solutions to prevent from DLL injection attack.

Two solutions are available:
- Using a Fully Qualified Path is the most secure way to load a DLL    
- Signature verification of the DLL    

### Resources and Solution Details

- Security remarks section of LoadLibraryEx documentation by Microsoft:    
- Microsoft Dynamic Link Library Security article:    
- Hijack Execution Flow: DLL Search Order Hijacking:     
- Hijack Execution Flow: DLL Side-Loading:

Issues· 0 open

View all issuesOpen on GitHub

No open issues yet, or sync has not completed.

> Tags

C

No comments yet. Be the first to share.

> Details

PublishedAug 1, 2026
UpdatedSep 18, 2026
Category编程语言
PricingOpen source

> Related tools

T
TypeScript
JavaScript 的超集,为前端与全栈提供静态类型
P
Python
通用编程语言,广泛用于 Web、数据与 AI
G
Go
Google 推出的简洁高效系统语言