Re: [RFC PATCH v11 02/51] fscrypt: export fscrypt_base64url_encode and fscrypt_base64url_decode

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Luís Henriques <lhenriques@xxxxxxx>, "Eric Biggers" <ebiggers@xxxxxxxxxx>
Subject: Re: [RFC PATCH v11 02/51] fscrypt: export fscrypt_base64url_encode and fscrypt_base64url_decode
From: "Colin Walters" <walters@xxxxxxxxxx>
Date: Thu, 24 Mar 2022 14:20:24 -0400
Cc: "Jeff Layton" <jlayton@xxxxxxxxxx>, idryomov@xxxxxxxxx, xiubli@xxxxxxxxxx, ceph-devel@xxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, linux-fscrypt@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
In-reply-to: <87zglgoi1e.fsf@brahms.olymp>
User-agent: Cyrus-JMAP/3.5.0-alpha0-4911-g925b585eab-fm-20220323.003-g925b585e


On Wed, Mar 23, 2022, at 10:33 AM, Luís Henriques wrote:

> So, my current proposal is to use a different encoding table. 

Another alternative is https://en.wikipedia.org/wiki/Base62

References:
- [RFC PATCH v11 00/51] ceph+fscrypt : full support
  - From: Jeff Layton
- [RFC PATCH v11 02/51] fscrypt: export fscrypt_base64url_encode and fscrypt_base64url_decode
  - From: Jeff Layton
- Re: [RFC PATCH v11 02/51] fscrypt: export fscrypt_base64url_encode and fscrypt_base64url_decode
  - From: Luís Henriques

Prev by Date: Re: [RFC PATCH v11 02/51] fscrypt: export fscrypt_base64url_encode and fscrypt_base64url_decode
Next by Date: Re: [PATCH RFC] nfsd: avoid recursive locking through fsnotify
Previous by thread: Re: [RFC PATCH v11 02/51] fscrypt: export fscrypt_base64url_encode and fscrypt_base64url_decode
Next by thread: [RFC PATCH v11 01/51] vfs: export new_inode_pseudo
Index(es):
- Date
- Thread

[Index of Archives] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [NTFS 3] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [NTFS 3] [Samba] [Device Mapper] [CEPH Development]