GCM-AEAD支持运行linux kernel-3.10的ubuntu系统

时间:2016-06-29 08:53:33

标签: encryption linux-kernel cryptography aes-gcm

我正在尝试使用GCM加密实现加密的AEAD示例代码。但是在设置密钥时我总是得到无效的参数错误

static int init_aead(void)
    {
        printk("Starting encryption\n");
        struct crypto_aead *tfm = NULL;
        struct aead_request *req;
        struct tcrypt_result tresult;

        struct scatterlist plaintext[1] ;
        struct scatterlist ciphertext[1];
        struct scatterlist gmactext[1];
        unsigned char *plaindata = NULL;
        unsigned char *cipherdata = NULL;
        unsigned char *gmacdata = NULL;

        const u8 *key =  kmalloc(16, GFP_KERNEL);

        char *algo = "rfc4106(gcm(aes))";
        unsigned char *ivp = NULL;
        int ret, i, d;
        unsigned int iv_len;
        unsigned int keylen = 16;

        /* Allocating a cipher handle for AEAD */
        tfm = crypto_alloc_aead(algo, 0, 0);
        init_completion(&tresult.completion);
        if(IS_ERR(tfm)) {
                     pr_err("alg: aead: Failed to load transform for %s: %ld\n", algo,
                            PTR_ERR(tfm));
                return PTR_ERR(tfm);
        }

        /* Allocating request data structure to be used with AEAD data structure */
        req = aead_request_alloc(tfm, GFP_KERNEL);
        if(IS_ERR(req)) {
            pr_err("Couldn't allocate request handle for %s:\n", algo);
            return PTR_ERR(req);
        }

        /* Allocting a callback function to be used , when the request completes */
        aead_request_set_callback(req, CRYPTO_TFM_REQ_MAY_BACKLOG, aead_work_done,&tresult);

        crypto_aead_clear_flags(tfm, ~0);

        /* Set key */
        get_random_bytes((void*)key, keylen);

     if((ret = crypto_aead_setkey(tfm, key, 16) != 0)) {
            pr_err("Return value for setkey is %d\n", ret);
            pr_info("key could not be set\n");
                ret = -EAGAIN;
            return ret;
        }

        /* Set authentication tag length */
            if(crypto_aead_setauthsize(tfm, 16)) {
            pr_info("Tag size could not be authenticated\n");
                ret = -EAGAIN;
            return ret;
        }

        /* Set IV size */
        iv_len = crypto_aead_ivsize(tfm);
        if (!(iv_len)){
            pr_info("IV size could not be authenticated\n");
                     ret = -EAGAIN;
                     return ret;
             }


        plaindata  = kmalloc(16, GFP_KERNEL);
        cipherdata = kmalloc(16, GFP_KERNEL);
        gmacdata   = kmalloc(16, GFP_KERNEL);
        ivp        = kmalloc(iv_len, GFP_KERNEL);

        if(!plaindata || !cipherdata || !gmacdata || !ivp) {
            printk("Memory not availaible\n");
            ret = -ENOMEM;
            return ret;
        }
        for (i = 0, d = 0; i < 16; i++, d++)
            plaindata[i] = d;

        memset(cipherdata, 0, 16);
        memset(gmacdata, 0, 16);

        for (i = 0,d=0xa8; i < 16; i++, d++)
            ivp[i] = d;

        sg_init_one(&plaintext[0], plaindata, 16);
        sg_init_one(&ciphertext[0], cipherdata, 16);
        sg_init_one(&gmactext[0], gmacdata, 128);
        aead_request_set_crypt(req, plaintext, ciphertext, 16, ivp);
        aead_request_set_assoc(req, gmactext, 16);

        ret = crypto_aead_encrypt(req);

        if (ret)
            printk("cipher call returns %d \n", ret);
        else
            printk("Failure \n");
        return 0;
     }

     module_init(init_aead);
     module_exit(exit_aead);
     MODULE_LICENSE("GPL");
     MODULE_DESCRIPTION("My code for aead encryption test");
     }

在插入模块时,我得到以下输出

  

开始加密
  setkey的返回值为-22
  无法设置密钥

根据AEAD规范,aead使用aes-128进行加密,因此块大小应为128位。

但是我的系统只显示了AEAD的1字节块大小支持

name         : rfc4106(gcm(aes))
driver       : rfc4106-gcm-aesni
module       : aesni_intel
priority     : 400
refcnt       : 1
selftest     : passed
type         : nivaead
async        : yes
blocksize    : 1
ivsize       : 8
maxauthsize  : 16
geniv        : seqiv

由于块大小,是否抛出了无效参数错误。如果是这样,我该怎么做才能使它发挥作用?

2 个答案:

答案 0 :(得分:0)

AES的块大小确实总是128位。然而,GCM的块大小是另一回事。 GCM(伽罗瓦计数器模式) - 顾名思义 - 建立在CTR(计数器)操作模式之上,有时也称为SIC(分段整数计数器)操作模式。这将AES转换为流密码。根据定义,流密码的块大小为一个字节(或者更确切地说,一个位,但API通常不支持位级操作)。

然而,块大小与调用中显示的密钥大小没什么关系,并且参数确实需要字节而不是位(通常定义密钥长度)。

IV的大小应为12个字节(默认值)。否则,GCM实施可能需要额外的计算(如果存在的话)。

答案 1 :(得分:0)

对于Aes GCM RFC 4106,密钥必须为20个字节。我还不知道为什么。我研究了ipsec源代码,以了解如何进行加密。