search

neicnordic / sensitive-data-archive

https://neic-sda.readthedocs.io
GNU Affero General Public License v3.0
3 stars 7 forks source link

Bump the all-modules group in /sda with 6 updates #920

Closed dependabot[bot] closed 3 months ago

dependabot[bot] commented 3 months ago

Bumps the all-modules group in /sda with 6 updates:

Package From To
github.com/aws/aws-sdk-go-v2 1.28.0 1.30.0
github.com/aws/aws-sdk-go-v2/config 1.27.19 1.27.21
github.com/aws/aws-sdk-go-v2/credentials 1.17.19 1.17.21
github.com/aws/aws-sdk-go-v2/feature/s3/manager 1.16.25 1.17.1
github.com/aws/aws-sdk-go-v2/service/s3 1.55.2 1.56.1
github.com/lestrrat-go/jwx/v2 2.0.21 2.1.0

Updates github.com/aws/aws-sdk-go-v2 from 1.28.0 to 1.30.0

Commits


Updates github.com/aws/aws-sdk-go-v2/config from 1.27.19 to 1.27.21

Commits


Updates github.com/aws/aws-sdk-go-v2/credentials from 1.17.19 to 1.17.21

Commits


Updates github.com/aws/aws-sdk-go-v2/feature/s3/manager from 1.16.25 to 1.17.1

Changelog

Sourced from github.com/aws/aws-sdk-go-v2/feature/s3/manager's changelog.

Release (2022-10-24)

General Highlights

  • Dependency Update: Updated to the latest SDK module versions

Module Highlights

  • github.com/aws/aws-sdk-go-v2/feature/ec2/imds: v1.12.19
    • Bug Fix: Fixes an issue that prevented logging of the API request or responses when the respective log modes were enabled.
  • github.com/aws/aws-sdk-go-v2/service/acmpca: v1.19.0
    • Feature: AWS Private Certificate Authority (AWS Private CA) now offers usage modes which are combination of features to address specific use cases.
  • github.com/aws/aws-sdk-go-v2/service/batch: v1.19.0
    • Feature: This release adds support for AWS Batch on Amazon EKS.
  • github.com/aws/aws-sdk-go-v2/service/datasync: v1.19.0
    • Feature: Added support for self-signed certificates when using object storage locations; added BytesCompressed to the TaskExecution response.
  • github.com/aws/aws-sdk-go-v2/service/sagemaker: v1.50.0
    • Feature: SageMaker Inference Recommender now supports a new API ListInferenceRecommendationJobSteps to return the details of all the benchmark we create for an inference recommendation job.

Release (2022-10-21)

General Highlights

  • Dependency Update: Updated to the latest SDK module versions

Module Highlights

  • github.com/aws/aws-sdk-go-v2: v1.17.0
    • Feature: Adds aws.IsCredentialsProvider for inspecting CredentialProvider types when needing to determine if the underlying implementation type matches a target type. This resolves an issue where CredentialsCache could mask AnonymousCredentials providers, breaking downstream detection logic.
  • github.com/aws/aws-sdk-go-v2/service/cognitoidentityprovider: v1.21.0
    • Feature: This release adds a new "DeletionProtection" field to the UserPool in Cognito. Application admins can configure this value with either ACTIVE or INACTIVE value. Setting this field to ACTIVE will prevent a user pool from accidental deletion.
  • github.com/aws/aws-sdk-go-v2/service/eventbridge: v1.16.16
    • Bug Fix: The SDK client has been updated to utilize the aws.IsCredentialsProvider function for determining if aws.AnonymousCredentials has been configured for the CredentialProvider.
  • github.com/aws/aws-sdk-go-v2/service/s3: v1.29.0
    • Feature: S3 on Outposts launches support for automatic bucket-style alias. You can use the automatic access point alias instead of an access point ARN for any object-level operation in an Outposts bucket.
    • Bug Fix: The SDK client has been updated to utilize the aws.IsCredentialsProvider function for determining if aws.AnonymousCredentials has been configured for the CredentialProvider.
  • github.com/aws/aws-sdk-go-v2/service/sagemaker: v1.49.0
    • Feature: CreateInferenceRecommenderjob API now supports passing endpoint details directly, that will help customers to identify the max invocation and max latency they can achieve for their model and the associated endpoint along with getting recommendations on other instances.
  • github.com/aws/aws-sdk-go-v2/service/sts: v1.17.0
    • Feature: Add presign functionality for sts:AssumeRole operation

Release (2022-10-20)

Module Highlights

  • github.com/aws/aws-sdk-go-v2/service/devopsguru: v1.20.0
    • Feature: This release adds information about the resources DevOps Guru is analyzing.
  • github.com/aws/aws-sdk-go-v2/service/globalaccelerator: v1.15.0
    • Feature: Global Accelerator now supports AddEndpoints and RemoveEndpoints operations for standard endpoint groups.
  • github.com/aws/aws-sdk-go-v2/service/resiliencehub: v1.7.0
    • Feature: In this release, we are introducing support for regional optimization for AWS Resilience Hub applications. It also includes a few documentation updates to improve clarity.
  • github.com/aws/aws-sdk-go-v2/service/rum: v1.7.0
    • Feature: CloudWatch RUM now supports Extended CloudWatch Metrics with Additional Dimensions

Release (2022-10-19)

... (truncated)

Commits


Updates github.com/aws/aws-sdk-go-v2/service/s3 from 1.55.2 to 1.56.1

Commits


Updates github.com/lestrrat-go/jwx/v2 from 2.0.21 to 2.1.0

Release notes

Sourced from github.com/lestrrat-go/jwx/v2's releases.

v2.1.0

v2.1.0 18 Jun 2024
[New Features]
  * [jwt] Added `jwt.ParseCookie()` function
  * [jwt] `jwt.ParseRequest()` can now accept a new option, jwt.WithCookieKey() to
    specify a cookie name to extract the token from.
  * [jwt] `jwt.ParseRequest()` and `jwt.ParseCookie()` can accept the `jwt.WithCookie()` option,
    which will, upon successful token parsing, make the functions assign the *http.Cookie
    used to parse the token. This allows users to further inspect the cookie where the
    token came from, should the need arise.
  * [jwt] (BREAKING CHANGE) `jwt.ParseRequest()` no longer automatically looks for "Authorization" header when
    only `jwt.WithFormKey()` is used. This behavior is the same for `jwt.WithCookieKey()` and
    any similar options that may be implemented in the future.

  # previously
  jwt.ParseRequest(req) // looks under Authorization
  jwt.ParseReuqest(req, jwt.WithFormKey("foo")) // looks under foo AND Authorization
  jwt.ParseReuqest(req, jwt.WithHeaderKey("Authorization"), jwt.WithFormKey("foo")) // looks under foo AND Authorization

  # since this release
  jwt.ParseRequest(req) // same as before
  jwt.ParseRequest(req, jwt.WithFormKey("foo")) // looks under foo
  jwt.ParseReuqest(req, jwt.WithHeaderKey("Authorization"), jwt.WithFormKey("foo")) // looks under foo AND Authorization



    

  • 

    [jwt] Add jwt.WithResetValidators() option to jwt.Validate(). This option
will allow you to tell jwt.Validate() to NOT automatically check the
default validators (iat, exp, and nbf), so that you can completely customize
the validation with the validators you specify using jwt.WithValidator().
    

    This sort of behavior is useful for special cases such as
https://openid.net/specs/openid-connect-rpinitiated-1_0.html. However, you SHOULD NOT
use this option unless you know exactly what you are doing, as this will pose
significant security issues when used incorrectly.
    

    • 

  • 

    [jwk] Provide a stop-gap measure to work with PEM format ASN.1 DER encoded secp256k1 keys.
    

    • 



In order to enable this feature, you must compile jwx with TWO build tags:
`jwx_es256k` to enable ES256K/secp256k1, and `jwx_secp256k1_pem` to enable PEM handling.
Not one, but BOTH tags need to be present.

With this change, by suppliying the `WithPEM(true)` option, `jwk.Parse()` is now
able to read sep256k1 keys. Also, `jwk.Pem()` should be able to handle `jwk.Key` objects
that represent a secp256k1 key.

Please do note that the implementation of this feature is dodgy at best. Currently
Go's crypto/x509 does not allow handling additional EC curves, and thus in order to
accomodate secp256k1 keys in PEM/ASN.1 DER format we need to "patch" the stdlib.
We do this by copy-and-pasting relevant parts of go 1.22.2's crypto/x509 code and
adding the minimum required code to make secp256k1 keys work.



</tr></table>

... (truncated)

Changelog

Sourced from github.com/lestrrat-go/jwx/v2's changelog.

v2.1.0 18 Jun 2024 [New Features]

  • [jwt] Added jwt.ParseCookie() function

  • [jwt] jwt.ParseRequest() can now accept a new option, jwt.WithCookieKey() to specify a cookie name to extract the token from.

  • [jwt] jwt.ParseRequest() and jwt.ParseCookie() can accept the jwt.WithCookie() option, which will, upon successful token parsing, make the functions assign the *http.Cookie used to parse the token. This allows users to further inspect the cookie where the token came from, should the need arise.

  • [jwt] (BREAKING CHANGE) jwt.ParseRequest() no longer automatically looks for "Authorization" header when only jwt.WithFormKey() is used. This behavior is the same for jwt.WithCookieKey() and any similar options that may be implemented in the future.

    previously

    jwt.ParseRequest(req) // looks under Authorization jwt.ParseReuqest(req, jwt.WithFormKey("foo")) // looks under foo AND Authorization jwt.ParseReuqest(req, jwt.WithHeaderKey("Authorization"), jwt.WithFormKey("foo")) // looks under foo AND Authorization

    since this release

    jwt.ParseRequest(req) // same as before jwt.ParseRequest(req, jwt.WithFormKey("foo")) // looks under foo jwt.ParseReuqest(req, jwt.WithHeaderKey("Authorization"), jwt.WithFormKey("foo")) // looks under foo AND Authorization

  • [jwt] Add jwt.WithResetValidators() option to jwt.Validate(). This option will allow you to tell jwt.Validate() to NOT automatically check the default validators (iat, exp, and nbf), so that you can completely customize the validation with the validators you specify using jwt.WithValidator().

    This sort of behavior is useful for special cases such as https://openid.net/specs/openid-connect-rpinitiated-1_0.html. However, you SHOULD NOT use this option unless you know exactly what you are doing, as this will pose significant security issues when used incorrectly.

  • [jwk] Provide a stop-gap measure to work with PEM format ASN.1 DER encoded secp256k1 keys.

    In order to enable this feature, you must compile jwx with TWO build tags: jwx_es256k to enable ES256K/secp256k1, and jwx_secp256k1_pem to enable PEM handling. Not one, but BOTH tags need to be present.

    With this change, by suppliying the WithPEM(true) option, jwk.Parse() is now able to read sep256k1 keys. Also, jwk.Pem() should be able to handle jwk.Key objects that represent a secp256k1 key.

    Please do note that the implementation of this feature is dodgy at best. Currently Go's crypto/x509 does not allow handling additional EC curves, and thus in order to accomodate secp256k1 keys in PEM/ASN.1 DER format we need to "patch" the stdlib. We do this by copy-and-pasting relevant parts of go 1.22.2's crypto/x509 code and adding the minimum required code to make secp256k1 keys work.

    Because of the above, there are several important caveats for this feature:

... (truncated)

Commits


Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions
aaperis commented 3 months ago

The breaking change in github.com/lestrrat-go/jwx/v2 does not seem to affect us since we are not using jwt.ParseRequest() as far as I can see.