Bump github.com/privacybydesign/irmago from 0.12.6 to 0.15.0

[dependabot]

Bumps github.com/privacybydesign/irmago from 0.12.6 to 0.15.0.

Release notes

Sourced from github.com/privacybydesign/irmago's releases.

v0.15.0

Added

• Support for Redis in Sentinel mode
• Redis support for irma keyshare server and irma keyshare myirmaserver
• /health endpoint for irma server, irma keyshare server and irma keyshare myirmaserver
• RemoveRequestorScheme function in irmaclient to remove a requestor scheme from the irma_configuration directory

Changed

• Using optimistic locking in the irma server instead of pessimistic locking
• storage-fallback-key-file option of irma keyshare server being replaced by storage-fallback-keys-dir option

Fixed

• HTTP cookies not stored in irmaclient when received from a Set-Cookie header
• Invalid hostname specified in MX record bypasses e-mail address revalidation
• Background revocation tasks not stopped when closing an irmaclient
• RemoveScheme function in irmaclient not deleting issuer schemes without a keyshare server (#260)

Internal

• Fixed issue with expired irma-demo.MijnOverheid key in testdata
• Always use testdata of current branch for integration-test jobs in GitHub Actions workflow

v0.14.2

Fixed

• IRMA session gets stuck in communicating status when user is requested to confirm PIN in irmaclient

v0.14.1

Fixed

• Improve stability of database drivers by bumping their versions

Security

• Use Go toolchain version 1.21.3 for building irma CLI tool

Internal

• Fixed failing tests due to expired test.test2 idemix key

v0.14.0

Note for users of the irmaclient package (e.g. maintainers of the Yivi app): the KeyshareVerifyPin function requires the renewal endpoint for the keyshare attribute to be present. Therefore, this version should first be deployed on keyshare servers before the client side can be upgraded.

Added

• Option skipExpiryCheck in disclosure requests to allow disclosure of expired credentials (e.g. "skipExpiryCheck": ["irma-demo.sidn-pbdf.email"])
• Option host in session request to overrule host name in IRMA QR if permission has been granted (see below)

  {
    "@context": "https://irma.app/ld/request/disclosure/v2",
    "host": "irma.example.com",
    "disclose": ...
  }
  

  This leads to the following session package:

  {
  

... (truncated)

Changelog

Sourced from github.com/privacybydesign/irmago's changelog.

[0.15.0] - 2023-12-11

Added

• Support for Redis in Sentinel mode
• Redis support for irma keyshare server and irma keyshare myirmaserver
• /health endpoint for irma server, irma keyshare server and irma keyshare myirmaserver
• RemoveRequestorScheme function in irmaclient to remove a requestor scheme from the irma_configuration directory

Changed

• Using optimistic locking in the irma server instead of pessimistic locking
• storage-fallback-key-file option of irma keyshare server being replaced by storage-fallback-keys-dir option

Fixed

• HTTP cookies not stored in irmaclient when received from a Set-Cookie header
• Invalid hostname specified in MX record bypasses e-mail address revalidation
• Background revocation tasks not stopped when closing an irmaclient
• RemoveScheme function in irmaclient not deleting issuer schemes without a keyshare server (#260)

Internal

• Fixed issue with expired irma-demo.MijnOverheid key in testdata
• Always use testdata of current branch for integration-test jobs in GitHub Actions workflow

[0.14.2] - 2023-10-25

Fixed

• IRMA session gets stuck in communicating status when user is requested to confirm PIN in irmaclient

[0.14.1] - 2023-10-18

Fixed

• Improve stability of database drivers by bumping their versions

Security

• Use Go toolchain version 1.21.3 for building irma CLI tool

Internal

• Fixed failing tests due to expired test.test2 idemix key

[0.14.0] - 2023-10-02

Note for users of the irmaclient package (e.g. maintainers of the Yivi app): the KeyshareVerifyPin function requires the renewal endpoint for the keyshare attribute to be present. Therefore, this version should first be deployed on keyshare servers before the client side can be upgraded.

Added

• Option skipExpiryCheck in disclosure requests to allow disclosure of expired credentials (e.g. "skipExpiryCheck": ["irma-demo.sidn-pbdf.email"])
• Option host in session request to overrule host name in IRMA QR if permission has been granted (see below)

  {
    "@context": "https://irma.app/ld/request/disclosure/v2",
    "host": "irma.example.com",
    "disclose": ...
  }
  

  This leads to the following session package:

  {
  

... (truncated)

Commits

• ca6c60c Merge pull request #364 from privacybydesign/version-bump-v0.15.0
• 4077a8d Version bump to v0.15.0
• 804df2d Merge pull request #354 from privacybydesign/redis-failover
• f1ac276 Merge branch 'master' into redis-failover
• 5024f30 Merge pull request #362 from privacybydesign/remove-scheme-fix
• 43d11cd Merge branch 'master' into remove-scheme-fix
• bc07cec Merge pull request #359 from privacybydesign/sticky-session-cookies
• 35815f6 Merge branch 'master' into sticky-session-cookies
• c4e46fc Check MX record hostname validity (#358)
• 95076b2 Test: remove nonexistent requestor scheme
• Additional commits viewable in compare view

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 <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #2695.