Skip to content
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.

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Jump to bottom

Explicitly specify hash in client applications #1255

Merged
merged 1 commit into from
Oct 7, 2024
Merged

Explicitly specify hash in client applications #1255

merged 1 commit into from
Oct 7, 2024

Commits on Oct 7, 2024

  1. Explicitly specify hash in client applications 

    For some signing implementations, such as ed25519, a non-default hash
implementation must be specified when creating the Gateway connection in
client applications. Rather than relying on the default hash algorithm,
it is probably good practice in general to specify an algorithm that is
compatible with your signing implementation.

This change explicitly specifies the hash algorithm to raise visibility
of the option to select the hash algorithm.

Signed-off-by: Mark S. Lewis <[email protected]>
    @bestbeforetoday
    bestbeforetoday committed Oct 7, 2024
    Configuration menu
    Copy the full SHA
    489b422 View commit details
    Browse the repository at this point in the history