head 1.13; access; symbols pkgsrc-2026Q1:1.12.0.8 pkgsrc-2026Q1-base:1.12 pkgsrc-2025Q4:1.12.0.6 pkgsrc-2025Q4-base:1.12 pkgsrc-2025Q3:1.12.0.4 pkgsrc-2025Q3-base:1.12 pkgsrc-2025Q2:1.12.0.2 pkgsrc-2025Q2-base:1.12 pkgsrc-2025Q1:1.11.0.4 pkgsrc-2025Q1-base:1.11 pkgsrc-2024Q4:1.11.0.2 pkgsrc-2024Q4-base:1.11 pkgsrc-2024Q3:1.10.0.6 pkgsrc-2024Q3-base:1.10 pkgsrc-2024Q2:1.10.0.4 pkgsrc-2024Q2-base:1.10 pkgsrc-2024Q1:1.10.0.2 pkgsrc-2024Q1-base:1.10 pkgsrc-2023Q4:1.4.0.4 pkgsrc-2023Q4-base:1.4 pkgsrc-2023Q3:1.4.0.2 pkgsrc-2023Q3-base:1.4 pkgsrc-2023Q2:1.3.0.2 pkgsrc-2023Q2-base:1.3 pkgsrc-2023Q1:1.2.0.4 pkgsrc-2023Q1-base:1.2 pkgsrc-2022Q4:1.2.0.2 pkgsrc-2022Q4-base:1.2 pkgsrc-2022Q3:1.1.0.2 pkgsrc-2022Q3-base:1.1; locks; strict; comment @# @; 1.13 date 2026.04.10.07.35.42; author adam; state Exp; branches; next 1.12; commitid RNpAKm4H2oI9SnBG; 1.12 date 2025.04.14.19.31.53; author adam; state Exp; branches; next 1.11; commitid CUE7javb7zjor3RF; 1.11 date 2024.11.11.07.29.25; author wiz; state Exp; branches; next 1.10; commitid 1fBDq3LwS98NncxF; 1.10 date 2024.03.07.10.01.52; author adam; state Exp; branches; next 1.9; commitid CIVhO51XRn1Ted1F; 1.9 date 2024.02.14.21.50.29; author adam; state Exp; branches; next 1.8; commitid V2eZWUZKD4tRRrYE; 1.8 date 2024.02.08.06.06.39; author adam; state Exp; branches; next 1.7; commitid EtGnKg4insWZPAXE; 1.7 date 2024.02.07.20.11.23; author adam; state Exp; branches; next 1.6; commitid m893I5wY0BjNxxXE; 1.6 date 2024.01.20.16.19.14; author wiz; state Exp; branches; next 1.5; commitid WLZt87yvD4N5QcVE; 1.5 date 2024.01.04.22.29.23; author adam; state Exp; branches; next 1.4; commitid M3Jo2CqmHsXOobTE; 1.4 date 2023.08.26.11.56.43; author adam; state Exp; branches; next 1.3; commitid sPu9OqzItjUR6iCE; 1.3 date 2023.05.29.08.51.08; author adam; state Exp; branches; next 1.2; commitid 1CzOIXXOmSqtWPqE; 1.2 date 2022.10.19.13.56.34; author nia; state Exp; branches; next 1.1; commitid SJILZksUbr0GLkYD; 1.1 date 2022.09.01.11.51.07; author markd; state Exp; branches; next ; commitid m5b67pXieqVeC9SD; desc @@ 1.13 log @py-jwcrypto: updated to 1.5.7 1.5.7 JWE: allow general (non flattened) serialization syntax Update CI actions Allow to pass through pem loading unsafe option Add support for 'scope' claim with multiple scopes Set default kid when importing keys from pyca. Hardening: Enforce length of keys for HMAC operations Add Ed25519 and Ed448 signature algorithms Migrate jwcrypto packaging to Hatch @ text @# $NetBSD: Makefile,v 1.12 2025/04/14 19:31:53 adam Exp $ DISTNAME= jwcrypto-1.5.7 PKGNAME= ${PYPKGPREFIX}-${DISTNAME} CATEGORIES= www python MASTER_SITES= ${MASTER_SITE_PYPI:=j/jwcrypto/} MAINTAINER= pkgsrc-users@@NetBSD.org HOMEPAGE= https://github.com/latchset/jwcrypto COMMENT= Implementation of JOSE Web standards LICENSE= gnu-lgpl-v3 TOOL_DEPENDS+= ${PYPKGPREFIX}-hatchling>0:../../devel/py-hatchling DEPENDS+= ${PYPKGPREFIX}-typing-extensions>=4.5.0:../../devel/py-typing-extensions USE_LANGUAGES= # none PYTHON_VERSIONED_DEPENDENCIES= cryptography .include "../../lang/python/versioned_dependencies.mk" .include "../../lang/python/wheel.mk" .include "../../mk/bsd.pkg.mk" @ 1.12 log @Fix PLIST after py-setuptools update; bump depends and revision @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.11 2024/11/11 07:29:25 wiz Exp $ d3 1 a3 1 DISTNAME= jwcrypto-1.5.6 a4 1 PKGREVISION= 1 d13 1 a13 1 TOOL_DEPENDS+= ${PYPKGPREFIX}-setuptools>=78:../../devel/py-setuptools @ 1.11 log @py-*: remove unused tool dependency py-setuptools includes the py-wheel functionality nowadays @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.10 2024/03/07 10:01:52 adam Exp $ d5 1 d14 1 a14 1 TOOL_DEPENDS+= ${PYPKGPREFIX}-setuptools-[0-9]*:../../devel/py-setuptools a19 3 PYTHON_VERSIONS_INCOMPATIBLE= 27 @ 1.10 log @py-jwcrypto: updated to 1.5.6 1.5.6 Address potential DoS with high compression ratio 1.5.5 This version fixes a pypi distribution problem introduced in 1.0 when pushing was automated. With 1.5.5 a binary wheel is now also made available on pypi. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.9 2024/02/14 21:50:29 adam Exp $ a13 1 TOOL_DEPENDS+= ${PYPKGPREFIX}-wheel-[0-9]*:../../devel/py-wheel @ 1.9 log @py-jwcrypto: updated to 1.5.4 v1.5.4 One more release bump to address issues with typing_extensions minimum required version @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.8 2024/02/08 06:06:39 adam Exp $ d3 1 a3 1 DISTNAME= jwcrypto-1.5.4 @ 1.8 log @py-jwcrypto: updated to 1.5.3 v1.5.3 Drop python 3.6 and 3.7 and add 3.11 support @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.7 2024/02/07 20:11:23 adam Exp $ d3 1 a3 1 DISTNAME= jwcrypto-1.5.3 d15 1 a15 1 DEPENDS+= ${PYPKGPREFIX}-typing-extensions-[0-9]*:../../devel/py-typing-extensions @ 1.7 log @py-jwcrypto: updated to 1.5.2 Version 1.5.2 replace deprecated package with typing_extensions @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.6 2024/01/20 16:19:14 wiz Exp $ d3 1 a3 1 DISTNAME= jwcrypto-1.5.2 @ 1.6 log @py-jwcrypto: add missing tools @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.5 2024/01/04 22:29:23 adam Exp $ d3 1 a3 1 DISTNAME= jwcrypto-1.5.1 d15 1 a15 1 DEPENDS+= ${PYPKGPREFIX}-deprecated-[0-9]*:../../devel/py-deprecated @ 1.5 log @py-jwcrypto: updated to 1.5.1 Version 1.5.1 - Security Release This is a minor security release to fix a potential DoS for applications that allow the use of symmetric keys with pbkdf2. What's Changed Fix X22519 import/export from PEM Read the Docs now requires a config file chore: refactor for removing pdb symbols Fix potential DoS issue with p2c header @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.4 2023/08/26 11:56:43 adam Exp $ d13 2 @ 1.4 log @py-jwcrypto: updated to 1.5.0 v1.5.0 Raising the bar for minimum pyca/cryptography Fix typos with codespell Add codespell checks in CI Add Brainpool EC-curves support Fix error message Fix assorted CI issue Better support for algorithms that have different input keysize requirement @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.3 2023/05/29 08:51:08 adam Exp $ d3 1 a3 1 DISTNAME= jwcrypto-1.5.0 a20 1 .include "../../lang/python/egg.mk" d22 1 @ 1.3 log @py-jwcrypto: updated to 1.4.2 Version 1.4.2 Fix typo in new backwards JWT compat heuristics Version 1.4.1 This is a minor release focused on improving backwards compatibility with applications after the API breaking changes introduced in 1.4 This patch adds a bunch of heuristics to be able to safely autodetect a token type. It has been tested to solve the compatibility issues (ie old code works without modifications and fully securely) with at least one large application. Version 1.4 This is a security release to address CVE-2022-3102. The JWT code can auto-detect the type of token being provided, and this can lead the application to incorrect conclusions about the trustworthiness of the token. Quoting the private disclosure we received : "Under certain circumstances, it is possible to substitute a [..] signed JWS with a JWE that is encrypted with the public key that is normally used for signature validation." This substitution attack can occur only if the validating application also have access to the private key, normally used to sign the tokens, available during validation of the received JWT. The significance of this attacks depends on the use of the token, it may lead to authentication bypass or authorization bypass (respectively if claims are used to authenticate or authorize certain actions), because the attacker has full control of the data placed in the JWE and can inject any desired claim value. Several mitigating factors exist that can protect applications from this issue: If the private key corresponding to the public key used to encrypt the JWE is not available to the application an exception will be raised. If the JWK is specified with the 'use' parameter set to 'sig' (as expected for keys used only for signing/verification) an exception will be raised. If the JWK is specified with the 'key_ops' parameter set and it does not include the 'decrypt' operation an exception will be raised. Applications may check the token type before validation, in this case they would fail to detect an expected JWS Normally, signing and validation are done by different applications, so this scenario should be unlikely. However it is possible to have applications that both sign and validate tokens and do not separate JWKs in use, or do not set a JWK 'use' type. Due to the mitigating factors, and the fact that specific operational constraints and conditions need to be in place to successfully exploit this issue to generate an authentication bypass, we rate this security issue as moderate. Other avenues may decide on a different rating based on use case, always verify what conditions apply to your use of the library to assess risk. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.2 2022/10/19 13:56:34 nia Exp $ d3 1 a3 1 DISTNAME= jwcrypto-1.4.2 @ 1.2 log @fighting a losing battle against py-cryptography rustification, part 2 Switch users to versioned_dependencies.mk. @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.1 2022/09/01 11:51:07 markd Exp $ d3 1 a3 1 DISTNAME= jwcrypto-1.3.1 d5 1 a5 1 CATEGORIES= www @ 1.1 log @py-jwcrypto: add version 1.3.1 An implementation of the JOSE Working Group documents: * RFC 7515 - JSON Web Signature (JWS) * RFC 7516 - JSON Web Encryption (JWE) * RFC 7517 - JSON Web Key (JWK) * RFC 7518 - JSON Web Algorithms (JWA) * RFC 7519 - JSON Web Token (JWT) * RFC 7520 - Examples of Protecting Content Using JSON Object Signing and Encryption (JOSE) @ text @d1 1 a1 1 # $NetBSD: Makefile,v 1.1 2016/06/09 02:06:18 markd Exp $ a12 1 DEPENDS+= ${PYPKGPREFIX}-cryptography>=2.3:../../security/py-cryptography d17 2 d22 1 @