From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-fscrypt-owner@kernel.org>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
	aws-us-west-2-korg-lkml-1.web.codeaurora.org
X-Spam-Level: 
X-Spam-Status: No, score=-7.5 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH,
	DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE,
	SPF_PASS autolearn=no autolearn_force=no version=3.4.0
Received: from mail.kernel.org (mail.kernel.org [198.145.29.99])
	by smtp.lore.kernel.org (Postfix) with ESMTP id 535ECC4320A
	for <linux-fscrypt@archiver.kernel.org>; Fri, 23 Jul 2021 08:16:50 +0000 (UTC)
Received: from vger.kernel.org (vger.kernel.org [23.128.96.18])
	by mail.kernel.org (Postfix) with ESMTP id 3D45060F02
	for <linux-fscrypt@archiver.kernel.org>; Fri, 23 Jul 2021 08:16:50 +0000 (UTC)
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S234516AbhGWHgN (ORCPT
        <rfc822;linux-fscrypt@archiver.kernel.org>);
        Fri, 23 Jul 2021 03:36:13 -0400
Received: from mail.kernel.org ([198.145.29.99]:55622 "EHLO mail.kernel.org"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S234488AbhGWHgL (ORCPT <rfc822;linux-fscrypt@vger.kernel.org>);
        Fri, 23 Jul 2021 03:36:11 -0400
Received: by mail.kernel.org (Postfix) with ESMTPSA id DBB2560EBD;
        Fri, 23 Jul 2021 08:16:44 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org;
        s=k20201202; t=1627028205;
        bh=FmcsTWKVBtnIpV3kMjIYbVPEWxN8HccIeY7NweLv3fc=;
        h=Date:From:To:Cc:Subject:References:In-Reply-To:From;
        b=p83qFCUO8L5H8TZ0pJz+hXz6JmnLt1esXuHZQ1efs1LWA9Opu0oBskpMKhw8FGdEn
         nRBdyz7JfEQ9qdkIcTf1s6jWVmXGJz0B10YnsGkoqu0Z+PT8MNdItnRK5/riqJ3n3N
         dMEmHj1FJUqoWauRhi1kqPUaFo4eMLlPmU5/k2LHvRDGmayVlV1MmoN75lE4I69XcO
         wzI4Wbxrh+pZFV+3FZfLhUXTIWs12fPDDRqUdqsH3RGGbE/sYaa1SZjPi0URUsmrV4
         MyrBojV249e4n2k4um2W07m0rzgP3013tggjYWhp30V03kOWm9xowzoMT08vWHlk2I
         2Lox9cg4HZL2A==
Date:   Fri, 23 Jul 2021 01:16:43 -0700
From:   Eric Biggers <ebiggers@kernel.org>
To:     Jeff Layton <jlayton@kernel.org>
Cc:     linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org,
        Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH] fscrypt: align Base64 encoding with RFC 4648 base64url
Message-ID: <YPp667igbuyElEcD@sol.localdomain>
References: <20210718000125.59701-1-ebiggers@kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20210718000125.59701-1-ebiggers@kernel.org>
Precedence: bulk
List-ID: <linux-fscrypt.vger.kernel.org>
X-Mailing-List: linux-fscrypt@vger.kernel.org

On Sat, Jul 17, 2021 at 07:01:25PM -0500, Eric Biggers wrote:
> 
> There have been two attempts to copy the fscrypt Base64 code into lib/
> (https://lkml.kernel.org/r/20200821182813.52570-6-jlayton@kernel.org and
> https://lkml.kernel.org/r/20210716110428.9727-5-hare@suse.de), and both
> have been caught up by the fscrypt Base64 variant being nonstandard and
> not properly documented.  Also, the planned use of the fscrypt Base64
> code in the CephFS storage back-end will prevent it from being changed
> later (whereas currently it can still be changed), so we need to choose
> an encoding that we're happy with before it's too late.

Jeff, any thoughts on whether this is the variant of Base64 you want to use in
the CephFS fscrypt support?

- Eric