[no description] https://git.osdyson.ru/mirror/pkgsrc/atom?h=trunk 2022-12-13T07:15:36Z 2022-12-13T07:15:36Z adam adam@pkgsrc.org 2022-12-13T07:15:36Z urn:sha1:bff2e5c2d501eefff4eb6556f65c4bca31573859 0.8.0 (2022-12-08) Features Add support for Python 3.11 Introduce granted scopes to credentials 2022-12-12T10:02:30Z adam adam@pkgsrc.org 2022-12-12T10:02:30Z urn:sha1:e56ec2135fc2aa81c15056fdcd6690905c81d18a Certbot 2.1.0 Fixed Interfaces which plugins register themselves as implementing without inheriting from them now show up in certbot plugins output. IPluginFactory, IPlugin, IAuthenticator and IInstaller have been re-added to certbot.interfaces. This is to fix compatibility with a number of third-party DNS plugins which may have started erroring with AttributeError in Certbot v2.0.0. Plugin authors can find more information about Certbot 2.x compatibility here. A bug causing our certbot-apache tests to crash on some systems has been resolved. 2022-12-12T09:49:33Z adam adam@pkgsrc.org 2022-12-12T09:49:33Z urn:sha1:c74692409d6503bd94cdee11124aac3681f24586 2.15.0 (2022-12-01) Features Add api_key credentials Introduce a way to provide scopes granted by user Bug Fixes Allow mtls sts endpoint for external account token urls. CI broken by removal of py.path Ensure JWT segments have the right types Updated the lower bound of interactive timeout and fix the kwarg… 2022-12-10T08:18:20Z wiz wiz@pkgsrc.org 2022-12-10T08:18:20Z urn:sha1:6536c8ed218a6b6336444e6d557fe782723d619c 2022-12-10T08:17:59Z wiz wiz@pkgsrc.org 2022-12-10T08:17:59Z urn:sha1:342ba87b5b36eecf66d92fdd84a9b305a0283a3b oauth2c is a command-line tool that simplifies the process of experimenting with different grant types and client authentication methods for OAuth 2.0. * Simple and intuitive interface for quickly experimenting with different OAuth 2.0 grant types and client authentication methods * Supports all modern OAuth 2.0 grant types: authorization code, implicit, password, client credentials, refresh token, JWT bearer * Supports all client authentication methods: client secret basic, client secret post, client secret JWT, private key JWT, TLS client auth 2022-12-09T11:20:02Z adam adam@pkgsrc.org 2022-12-09T11:20:02Z urn:sha1:35866a70b2d7cb6e1bd584fef078e3430f6f6b25 Version 1.2.0 Not passing request.body to ResourceProtector Use flask.g instead of _app_ctx_stack Add headers parameter back to ClientSecretJWT Always passing realm parameter in OAuth 1 clients Implemented RFC7592 Dynamic Client Registration Management Protocol Add default_timeout for requests OAuth2Session and AssertionSession. Deprecate jwk.loads and jwk.dumps 2022-12-08T16:14:12Z bsiegert bsiegert@pkgsrc.org 2022-12-08T16:14:12Z urn:sha1:4cdbf516beb7f96c9e722a3493c56e4c349628e5 2022-12-08T08:57:54Z adam adam@pkgsrc.org 2022-12-08T08:57:54Z urn:sha1:661f25da9d963c7f05e8bf7f5cc65c33a5da224a 2022.12.7 Unknown changes 2022-12-06T14:41:38Z vins vins@pkgsrc.org 2022-12-06T14:41:38Z urn:sha1:6470f2f273fcca5b7f638bd9a95645c6be6e6012 2022-12-05T21:57:57Z nikita nikita@pkgsrc.org 2022-12-05T21:57:57Z urn:sha1:5ea77d0a682c1e3f08a1415c102a50bdcd9b47c6 git-crypt enables transparent encryption and decryption of files in a git repository. Files which you choose to protect are encrypted when committed, and decrypted when checked out. git-crypt lets you freely share a repository containing a mix of public and private content. git-crypt gracefully degrades, so developers without the secret key can still clone and commit to a repository with encrypted files. This lets you store your secret material (such as keys or passwords) in the same repository as your code, without requiring you to lock down your entire repository.