From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id EE0FF158094 for ; Tue, 26 Jul 2022 09:49:43 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 5CEAEE0C4D; Tue, 26 Jul 2022 09:49:24 +0000 (UTC) Received: from sysrq.in (sysrq.in [37.79.202.136]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id E765BE0BBB; Tue, 26 Jul 2022 09:49:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sysrq.in; s=sysrq.in; t=1658828958; h=from:from: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=Ks7dNF6JeikFA5DFABB4TxI+XoDJi6mIrWk53dmSWXM=; b=Q8o3yNK5A5blEp8lsRlJsG20X72ioBuJHoxxU92CgcHQ7IyRJRxkhmXOIducvh8O7B8wIM FKCHQSMukgkvT+sOy0aUGdG48CwVsdC99+5gXvOAirva+zJvZk0b98I3MWbX+zcptrTrGG YAMCvAmFfGU5wuQRkXY4BkNBAIJp4JLPn9o0B8aVL/l0ptW4JnFL8Ao2BRMdXer9FAhkUb 9D/yhufH1eliUo50oAiyrUe2kt83lnPSyVj6kkPJSTYaPtfhBOWAbP4KMf9sNM8igmD3zn N4wKpZb++MKED/gM722ruMAax3Yl1WM0odKvVZKfHJcnhQ1WLfDCmGgsraSUpw== Received: from sysrq.in (localhost [127.0.0.1]) by sysrq.in (OpenSMTPD) with ESMTPSA id 9dcbc703 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Tue, 26 Jul 2022 09:49:18 +0000 (UTC) Date: Tue, 26 Jul 2022 14:49:17 +0500 From: Anna To: gentoo-dev@lists.gentoo.org Cc: gentoo-user@lists.gentoo.org Subject: [gentoo-user] Re: [gentoo-dev] Rust is here to eat your Pythonz Message-ID: Mail-Followup-To: gentoo-dev@lists.gentoo.org, gentoo-user@lists.gentoo.org References: <19ec63ff438cbae29877d1b026699df797b9eefe.camel@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <19ec63ff438cbae29877d1b026699df797b9eefe.camel@gentoo.org> User-Agent: Mutt/2.2.6 (2022-06-05) X-Archives-Salt: 7ce0f128-3d93-4f7b-9fa5-890c77025fb2 X-Archives-Hash: 77891670b8376408276852cf34bbdb4c On 2022-07-26 08:42, Michał Górny wrote: > Hi, everyone. > > Just a quick FYI: since Rust is going to be marked stable on the last > architecture (sparc) that it's going to support in Gentoo, we're going > to start cleaning up old dev-python/cryptography soon. If you don't > want Rust, removing cryptography entirely will be your only option. I see three solutions here (except installing rust): 1) Stick to old cryptography/pyopenssl (if none of vulnerabilities impact revdeps) 2) Kindly ask upstream to switch to PyCryptodome 3) Write a library that implements cryptography API using PyCryptodome The last option is kinda useless but fun. If you find it interesting, contact me.