summaryrefslogtreecommitdiff
path: root/UPDATING
diff options
context:
space:
mode:
authorTobias C. Berner <tcberner@FreeBSD.org>2023-07-22 08:00:10 +0200
committerTobias C. Berner <tcberner@FreeBSD.org>2023-07-22 09:46:37 +0200
commit173ac9651cc9ef0ab952b29e4cffa56d28e8770b (patch)
tree3b960da6306b24267847cea47cafa034cd2dfa67 /UPDATING
parentsecurity/py-cryptography: copy port to -legacy variant prior to update (diff)
framework: add PYCRYPTOGRAPHY default version
A future commit will update to security/py-cryptography will introduce a rust dependency. PR: 254853
Diffstat (limited to '')
-rw-r--r--UPDATING12
1 files changed, 12 insertions, 0 deletions
diff --git a/UPDATING b/UPDATING
index 144a7b4d1df3..569b6131db4e 100644
--- a/UPDATING
+++ b/UPDATING
@@ -5,6 +5,18 @@ they are unavoidable.
You should get into the habit of checking this file for changes each time
you update your ports collection, before attempting any port upgrades.
+20230723:
+ AFFECTS: users of security/py-cryptography
+ AUTHOR: tcberner@FreeBSD.org
+
+ Modern py-cryptography uses rust. In order to still support the Tier-2
+ architectures without rust support, a new default-version was added:
+ PYCRYPTOGRAPHY
+ it allows for the values 'rust' and 'legacy'.
+ The default is 'rust' on all platforms supporting this.
+ Note: users that are relying on the 'legacy' version will also take care
+ of using a non-base OpenSSL in the future.
+
20230620:
AFFECTS: users of lang/elixir-devel
AUTHOR: dch@FreeBSD.org