Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp4439022pxf; Tue, 30 Mar 2021 07:53:17 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwCIKpdrNnaUAVIlaFzj4Eya2/NpCqw1zLW8U0vEfWnX6mqyZFC5YHUsr1S4F7J7FL9hhLj X-Received: by 2002:a17:906:36d1:: with SMTP id b17mr22753855ejc.235.1617115997180; Tue, 30 Mar 2021 07:53:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1617115997; cv=none; d=google.com; s=arc-20160816; b=IH2H1/2C/ZanPecTtON5QFsAF/QIi19qGBs31CaFm4bYHhGsGWhyDG7At4eewKtYUO FC9rk2cWzpsSKi5lmUeWbf9KhpwKIV1Th32/eZR/QAyn977G1q5NKmwbAALStQjKPAsz eSwRv/e05OR9WFqVWP2Q+v2oKw1F9eEfuCXATaSbf8djJH04eBZRrWd/h3cPb/8GWFAU hhzh01SPPL+4vJnkmCcSe3gwulRIai8dQ3Ls8H33XUiFT+NYDW0HuNK+/Rgvj4hif4Qp GEjGNEN74/tGtVkZfIS6m0NiGKbFw5A4j3zI5ZsXEIjmJHGrFeXDlDimtGU1uVonVs1W Vl1Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-language:content-transfer-encoding :in-reply-to:mime-version:user-agent:date:message-id:organization :from:references:cc:to:subject:reply-to:dkim-signature; bh=VJVm+BmDLZgTWR3iPU4bINy5jGu0DH6bKNz0lNZl+3Q=; b=CnYHv8gyFtk68Sxny4/KumoPZ9hTK5wRABHs764OeqaMnEN3kUFQutEtT/i+eAqf4I rYZoPt8EGHSDA8YIZg6hzyzKXqAzm2E1PolPXE3lM4LzQHo5GAewvEvQvjFlNqpW5o48 947ZGnpFbNFl1po1dZ14PHcIeOUqeok+M0k85CZJFPXU6i/JeS5EsSzoVGMmSXqLkwn7 D6il7sG7ngmnUFdUMPsxCCGb2B0QLzB5IEcnQdY5qLP0A+rIWhh6vquUlC9Go+h4hsNK m4hyLrf1YuodgiEPcuiqKWf/CWSjzKVCU1Z/QwOP28hLKDId5BDST4epO0dgdGXz+PJX vPYw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Xf0sYMoL; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id bo5si14904407edb.459.2021.03.30.07.52.53; Tue, 30 Mar 2021 07:53:17 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Xf0sYMoL; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231752AbhC3OwM (ORCPT + 99 others); Tue, 30 Mar 2021 10:52:12 -0400 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:29026 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232059AbhC3Ovy (ORCPT ); Tue, 30 Mar 2021 10:51:54 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1617115914; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=VJVm+BmDLZgTWR3iPU4bINy5jGu0DH6bKNz0lNZl+3Q=; b=Xf0sYMoLVX7S77QilXAyBWokCldKRbDN2erDs4Osa0Ne0qfHIQNaRqf64vB+VkocBMxFd2 JLlEz/IO14eRMoaPYj9Kg+SwukbPSjJPyvZIA8ZARCIeJV+B85eJnpQf3y9CxIzstkkRjq 1YFLzNTN9U4cvnqCSw13Faeyg9olfk4= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-343-JaTNFoPKMVSSWsWfcIgTnw-1; Tue, 30 Mar 2021 10:51:50 -0400 X-MC-Unique: JaTNFoPKMVSSWsWfcIgTnw-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id B7F96802B40; Tue, 30 Mar 2021 14:51:48 +0000 (UTC) Received: from crecklin.bos.csb (unknown [10.22.8.39]) by smtp.corp.redhat.com (Postfix) with ESMTP id 16C8E19C44; Tue, 30 Mar 2021 14:51:48 +0000 (UTC) Reply-To: crecklin@redhat.com Subject: Re: Fix hibernation in FIPS mode? To: "Rafael J. Wysocki" , Dexuan Cui Cc: "linux-pm@vger.kernel.org" , "linux-crypto@vger.kernel.org" , "linux-kernel@vger.kernel.org" References: From: Chris von Recklinghausen Organization: Red Hat Message-ID: Date: Tue, 30 Mar 2021 10:51:47 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On 3/30/21 10:46 AM, Rafael J. Wysocki wrote: > On Tue, Mar 30, 2021 at 12:14 AM Dexuan Cui wrote: >> Hi, >> MD5 was marked incompliant with FIPS in 2009: >> a3bef3a31a19 ("crypto: testmgr - Skip algs not flagged fips_allowed in fips mode") >> a1915d51e8e7 ("crypto: testmgr - Mark algs allowed in fips mode") >> >> But hibernation_e820_save() is still using MD5, and fails in FIPS mode >> due to the 2018 patch: >> 749fa17093ff ("PM / hibernate: Check the success of generating md5 digest before hibernation") >> >> As a result, hibernation doesn't work when FIPS is on. >> >> Do you think if hibernation_e820_save() should be changed to use a >> FIPS-compliant algorithm like SHA-1? > I would say yes, it should. If we're not actually encrypting anything, shouldn't something like ghash work as well? > >> PS, currently it looks like FIPS mode is broken in the mainline: >> https://www.mail-archive.com/linux-crypto@vger.kernel.org/msg49414.html