Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Bump github.com/ProtonMail/go-crypto from 1.1.0-alpha.2 to 1.1.0-alpha.4-proton#973

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Conversation

@dependabot
Copy link
Contributor

@dependabotdependabotbot commented on behalf ofgithubJul 17, 2024

Bumpsgithub.com/ProtonMail/go-crypto from 1.1.0-alpha.2 to 1.1.0-alpha.4-proton.

Release notes

Sourced fromgithub.com/ProtonMail/go-crypto's releases.

v1.1.0-alpha.4-proton

This pre-release is v1.1.0-alpha.4 with support for symmetric keys and automatic forwarding, both of which are not standardized yet.

v1.1.0-alpha.3-proton

This pre-release is v1.1.0-alpha.3 with support for symmetric keys and automatic forwarding, both of which are not standardized yet.

v1.1.0-alpha.1-proton

This pre-release is v1.1.0-alpha.1 with support for symmetric keys and automatic forwarding, both of which are not standardized yet.

v1.1.0-alpha.0-proton

This pre-release is v1.1.0-alpha.0 with support for symmetric keys and automatic forwarding, both of which are not standardized yet.

v1.1.0-alpha.4

What's Changed

Full Changelog:ProtonMail/go-crypto@v1.1.0-alpha.3...v1.1.0-alpha.4

v1.1.0-alpha.3

What's Changed

  • New functions to verify signature hash tags
  • Allow parsing certifications explicitly marked as exportable
  • Sorting signature sub-packets by their ID when serializing
  • Markcreation time,issuer key ID, andkey flag signature sub-packets as critical
  • When AEAD is in use, the session key length is now determined by the cipher specified in the AEAD preference.

Full Changelog:v1.1.0-alpha.2...v1.1.0-alpha.3

Commits
  • 0b33f7b Fix HMAC generation (#204)
  • 9c1877a Replace ioutil.ReadAll with io.ReadAll
  • 91a0def fix(v2): Adapt NewForwardingEntity to refactored NewEntity
  • da66ff5 fix(v2): Do not allow encrpytion with a forwarding key
  • f27ab7d feat: Add symmetric keys to v2
  • 4017cb3 fix: Address warnings
  • fcee26d feat: Add forwarding to v2 api
  • 20a257b fix: Address rebase on version 2 issues
  • a5524a5 Use fingerprints instead of KeyIDs
  • 9be33fe Create a copy of the encrypted key when forwarding
  • Additional commits viewable incompare view

Dependabot compatibility score

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)

Bumps [github.com/ProtonMail/go-crypto](https://github.com/ProtonMail/go-crypto) from 1.1.0-alpha.2 to 1.1.0-alpha.4-proton.- [Release notes](https://github.com/ProtonMail/go-crypto/releases)- [Commits](ProtonMail/go-crypto@v1.1.0-alpha.2...v1.1.0-alpha.4-proton)---updated-dependencies:- dependency-name: github.com/ProtonMail/go-crypto  dependency-type: direct:production  update-type: version-update:semver-patch...Signed-off-by: dependabot[bot] <support@github.com>
@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 20.04%. Comparing base(da1fa2e) to head(fc077e7).

Additional details and impacted files
@@           Coverage Diff           @@##             main     #973   +/-   ##=======================================  Coverage   20.04%   20.04%           =======================================  Files          42       42             Lines        2569     2569           =======================================  Hits          515      515             Misses       1968     1968             Partials       86       86
FlagCoverage Δ
unit20.04% <ø> (ø)

Flags with carried forward coverage won't be shown.Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report?Share it here.

@dependabot@github
Copy link
ContributorAuthor

dependabotbot commented on behalf ofgithubJul 19, 2024

Superseded by#974.

@dependabotdependabotbot closed thisJul 19, 2024
@dependabotdependabotbot deleted the dependabot/go_modules/github.com/ProtonMail/go-crypto-1.1.0-alpha.4-proton branchJuly 19, 2024 00:29
@per1234per1234 added the conclusion: duplicateHas already been submitted labelJul 19, 2024
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

conclusion: duplicateHas already been submittedtopic: infrastructureRelated to project infrastructure

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@codecov-commenter@per1234

[8]ページ先頭

©2009-2025 Movatter.jp