From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-ej1-f42.google.com (mail-ej1-f42.google.com [209.85.218.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 61DC72FD1BF for ; Mon, 16 Feb 2026 11:53:59 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.218.42 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771242840; cv=none; b=b95tRIvTRC7aHmZurwoWTeyO4Z6sOxal+N6rThKVhiiQd9f3MWRGmhF2ut9j7x0koUohWq7Ss4jJVXq0wHWot/wIr6nq59i4ymMoZEIA026S/wiKzuE+xOojgt1mKPwEliWvS+cqgsXWRHxow/4su2hGZYChc6ibh9UOmWF5DR4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1771242840; c=relaxed/simple; bh=KAh4XyjTnWAcolgvdTlSSIr2XBjG7K/fvepak+cw1pc=; h=Message-ID:Date:MIME-Version:To:Cc:References:Subject:From: In-Reply-To:Content-Type; b=PeDgXASyB4qEyfGG4ApgJlmFqw9cA27MVthWuonUJgsdUIl03492ApgSml5NSzBifnxpBHrhoemXB80jpCnQuQy9E/x/MAEOg4/KGNUV1MyXMrKZQhViMQCjPXUOV5HAmuudaHCAkY24mKMxOikk3RYuQkFRtMzkSTth1uZQ12w= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com; spf=pass smtp.mailfrom=gmail.com; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b=a/GuozCP; arc=none smtp.client-ip=209.85.218.42 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="a/GuozCP" Received: by mail-ej1-f42.google.com with SMTP id a640c23a62f3a-b8842e5a2a1so376785766b.2 for ; Mon, 16 Feb 2026 03:53:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1771242838; x=1771847638; darn=vger.kernel.org; h=content-transfer-encoding:in-reply-to:from:content-language:subject :references:cc:to:user-agent:mime-version:date:message-id:from:to:cc :subject:date:message-id:reply-to; bh=Is3zhxQHenNpJMaluJOmpzUNW36eR4Zww2/Tfs8Kxqc=; b=a/GuozCPH+wjLBNmNnYB+eY7qDjDgQE+800sJSUrtA51OMhFeR/H5vzMtI+3T7oUPi 1EVanD8p4XYCIHNdgFXciw9AFQ93SkbV51eLh1uEeuCexZfyVEJIT/aPmGLpricsGOT0 t88fhrDhXhYZPPvX+xFKMHP5Lv6ZLfpkBGDL3W+WNzBbyS8mJDWeL2nlsYikIxOU73Hu 2NH8NHDn3jovs+c0wYbb1jCGmpRJPyVgxrNg9QR0U5kCzLu8fVv6ZJh4Bi3yuQrDV+f1 2MPHcB1ud8oI/fi+mkwiuVEVqZyoGMHoHHPXhzTw3+JVlQGCD0YC1IOBuR1COFt18Sta L4oA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1771242838; x=1771847638; h=content-transfer-encoding:in-reply-to:from:content-language:subject :references:cc:to:user-agent:mime-version:date:message-id:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=Is3zhxQHenNpJMaluJOmpzUNW36eR4Zww2/Tfs8Kxqc=; b=GqFGdoBFR5Ycke412vvA9FGbca6H4MOlUJk+9JcQ3ID9Vz/BzFqWLXFX300Nbn4u81 5lz+YDNJlE9boMdJTNOu0UTwT3f/5rjhf0STBtFfAJI8Z6v2zanut8QdgLARmGr5RGG/ BYtWC8ZNF2uEMe8sZMfImId/KXy/FmHv/y/EHXsYpUXpImO++QxT/LauaixRQBPrZ8IR MUE0BkWMU4kHIst0VJQzfQ7anfKpqorGHRde/pt4eyXEXnN938Ctobs4gltRwOLjyCAD EFHI6dJiC4VqJyqc9i6wtU2Hd9jMNOAVUa4/GY0vcHbZgsXESqslblmNgZd9ARkTLCFt xbNA== X-Forwarded-Encrypted: i=1; AJvYcCXBrwRY/myu6YLV2PhAMAzhI5Ckh0vIp2OTX1YTqspJzT/c0IhHbRJeigGp0FmfgO8UNH2Mdw0F8g==@vger.kernel.org X-Gm-Message-State: AOJu0YzA5ETX9mthoBkwzEwyAdm+GhpVQ70WjqRGl1ucxAfVb4ZycZ/7 ZAspMHNqeaU2Zb6SVIJyJAjZGwruDfStvE/i7fh7oX06LSOBnKwZpQbM X-Gm-Gg: AZuq6aIK8xooUDlSo+GKjS4cTbiLvX8iF7tyv5s2ZoF0xmdx0Ume7q5dc0jYKozHqGH 4fKYWhufb1Ws2fbA0UpYFvI1C8IVVWUVxAvAr4uInDN/MR6EzpAoIHZ7I/YHl/ura+26lCWOEiE HXz2NGjo5MH4A0efbmv1XDYqwjuu1fkrcCP4dAxFBrFh2z5XBfKxMKAHVBP3CBQtNpGEjYHo+14 k6rWSeNcYAfHxNvL936JpSBpg5oOESWU1MSO1ueaZsebnhMsUgleT4ud4C2EfqbMSjiH2BwM3Hw RFkbsGmKyzuzIh8L47tfUdEXAdJNe691FlJSWHFqyiG1uFDMoLUl9gW19wcJpVGaKE4Icq+Fp0o L4gTqbiduekzjG+7eC1n7MmP4celXByI7DT+ZAIUaoz8/rBz12Vq1aa/KPQ6OEXzQBFTCz9Bf9I Lzo8pVtovr7uCT2HGeT/1Yum8SIW4Rm9L5u01AeSE+z+MnrSNH7UWYQ30v5DxZe5YIlwi4vhE= X-Received: by 2002:a17:907:3f12:b0:b73:9280:2e7 with SMTP id a640c23a62f3a-b8fb449ad96mr546215266b.34.1771242837544; Mon, 16 Feb 2026 03:53:57 -0800 (PST) Received: from [192.168.0.13] (217-62-96-139.cable.dynamic.v4.ziggo.nl. [217.62.96.139]) by smtp.gmail.com with ESMTPSA id a640c23a62f3a-b8fc7691c48sm251383066b.59.2026.02.16.03.53.56 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 16 Feb 2026 03:53:57 -0800 (PST) Message-ID: Date: Mon, 16 Feb 2026 12:53:56 +0100 Precedence: bulk X-Mailing-List: ecryptfs@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: code@tyhicks.com, root@linuxmint.com Cc: arnd@arndb.de, arnd@kernel.org, damien.lemoal@opensource.wdc.com, ecryptfs@vger.kernel.org, linux-kernel@vger.kernel.org, tytso@mit.edu, willy@infradead.org References: Subject: Re: ecryptfs is unmaintained and untested Content-Language: en-US From: =?UTF-8?Q?Ren=C3=A9_Herman?= In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit > It would be good to discuss how we can get the message out to users to > migrate off of eCryptfs so that functionality can be reduced and > eventually it can be removed. > > What do folks think about the following? > > 1. Print loud warnings at mount time that eCryptfs is deprecated and > give a specific date when write support will be removed. > 2. Remove write support at that date, while retaining read-only support > to allow any lagging users to move their data to fscrypt or other > alternatives. > 3. Print loud warnings at mount that eCryptfs will be removed and give a > specific date. > 4. Remove it. > > Suggestions on lead times for #2 and #4 would be appreciated. FWIW. Ever since Ubuntu dropped eCryptfs home-directory encryption already in I believe 18.04 from now 8 years ago, Linux Mint has probably been the single biggest consumer of eCryptfs: while based on Ubuntu, they've added back eCryptfs home-directory encryption in the installer ever since Ubuntu dropped it. In the Mint project lead's latest blog he/they moreover proudly announced that their upcoming new & shiny GUI user-management tool will now support enabling home-directory also for at runtime added accounts (which up to now is done with adduser --encrypt-home from the command line only) rather than just the first, installer- created user account, and I am pretty much certain that the idea there still is *eCryptfs* home-directory-encryption. Mint is not the kind of project that routinely goes low-level. https://blog.linuxmint.com/?p=4991 In any case then this is to say that they seem to not be planning on moving off of eCryptfs -- and Linux Mint is (probably?) the most popular Linux Distribution for/among new Linux users. Have been commenting on this a bit as well on their forum, advocating for fully doing away with eCryptfs, but quite unsure that'll have any meaningful impact. Added the Mint project lead to the CC on this. If there's any progress to report on slashing eCryptfs he/they may want to be aware. Regards, Rene