Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Use --passphrase-fd to supply passphrase to gpg2

  1. … 1 more file in changeset.
Add support for key fingerprints

In order to provide maximum security, it's now possible to use full key

fingerprints, in addition to long (64-bit) key ids, in trusted or ignored

keys.

It doesn't matter what format is used: if a trusted key uses a long id,

then it's possible that if there's a key collision, an artifact would be

trusted even if it shouldn't. If a fingerprint is used instead, then we

would use the full fingerprint for verification.

It's worth nothing that PGP doesn't provide the full fingerprint in signatures

for the key issuer. This means that when we're going to download keys, we

will still use the long ids.

Fixes #11770

    • -0
    • +100
    ./Fingerprint.java
    • -15
    • +39
    ./KeyringFilePublicKeyService.java
    • -0
    • +24
    ./PublicKeyResultBuilder.java
  1. … 13 more files in changeset.
Add support for key fingerprints

In order to provide maximum security, it's now possible to use full key

fingerprints, in addition to long (64-bit) key ids, in trusted or ignored

keys.

It doesn't matter what format is used: if a trusted key uses a long id,

then it's possible that if there's a key collision, an artifact would be

trusted even if it shouldn't. If a fingerprint is used instead, then we

would use the full fingerprint for verification.

It's worth nothing that PGP doesn't provide the full fingerprint in signatures

for the key issuer. This means that when we're going to download keys, we

will still use the long ids.

Fixes #11770

    • -0
    • +100
    ./Fingerprint.java
    • -15
    • +39
    ./KeyringFilePublicKeyService.java
    • -0
    • +24
    ./PublicKeyResultBuilder.java
  1. … 13 more files in changeset.
Rework how the keyring file is written

For some reason the previous version is not always

fully re-readable...

  1. … 1 more file in changeset.
Rework how the keyring file is written

For some reason the previous version is not always

fully re-readable...

  1. … 1 more file in changeset.
Add safety around reading of keyring file

Add safety around reading of keyring file

Add safety around reading of keyring file

Avoid verifying the same artifact multiple times

and make sure that signature files are downloaded concurrently. This

commit adds several improvements, in particular by avoiding making

the same network requests multiple times just because we use the same

PGP key but in a different context.

  1. … 7 more files in changeset.
Avoid verifying the same artifact multiple times

and make sure that signature files are downloaded concurrently. This

commit adds several improvements, in particular by avoiding making

the same network requests multiple times just because we use the same

PGP key but in a different context.

  1. … 6 more files in changeset.
Avoid verifying the same artifact multiple times

and make sure that signature files are downloaded concurrently. This

commit adds several improvements, in particular by avoiding making

the same network requests multiple times just because we use the same

PGP key but in a different context.

  1. … 7 more files in changeset.
Avoid verifying the same artifact multiple times

and make sure that signature files are downloaded concurrently. This

commit adds several improvements, in particular by avoiding making

the same network requests multiple times just because we use the same

PGP key but in a different context.

  1. … 7 more files in changeset.
Avoid verifying the same artifact multiple times

and make sure that signature files are downloaded concurrently. This

commit adds several improvements, in particular by avoiding making

the same network requests multiple times just because we use the same

PGP key but in a different context.

  1. … 6 more files in changeset.
Avoid verifying the same artifact multiple times

  1. … 5 more files in changeset.
Avoid verifying the same artifact multiple times

and make sure that signature files are downloaded concurrently. This

commit adds several improvements, in particular by avoiding making

the same network requests multiple times just because we use the same

PGP key but in a different context.

  1. … 7 more files in changeset.
Avoid verifying the same artifact multiple times

and make sure that signature files are downloaded concurrently. This

commit adds several improvements, in particular by avoiding making

the same network requests multiple times just because we use the same

PGP key but in a different context.

  1. … 6 more files in changeset.
Add local keyring file

Fetching remote keys can be quite expensive. In order to avoid lookups,

this commits introduces the ability to use a local keyrings file, found

alongside the verification metadata.

This file can either be generated using regular tools like GPG, or via

command-line by adding the `--export-keys` flag when generating the

verification metadata.

    • -0
    • +75
    ./KeyringFilePublicKeyService.java
    • -0
    • +72
    ./PublicKeyServiceChain.java
  1. … 15 more files in changeset.
Add local keyring file

Fetching remote keys can be quite expensive. In order to avoid lookups,

this commits introduces the ability to use a local keyrings file, found

alongside the verification metadata.

This file can either be generated using regular tools like GPG, or via

command-line by adding the `--export-keys` flag when generating the

verification metadata.

  1. … 15 more files in changeset.
Add local keyring file

Fetching remote keys can be quite expensive. In order to avoid lookups,

this commits introduces the ability to use a local keyrings file, found

alongside the verification metadata.

This file can either be generated using regular tools like GPG, or via

command-line by adding the `--export-keys` flag when generating the

verification metadata.

    • -0
    • +75
    ./KeyringFilePublicKeyService.java
    • -0
    • +63
    ./PublicKeyServiceChain.java
  1. … 15 more files in changeset.
Add local keyring file

Fetching remote keys can be quite expensive. In order to avoid lookups,

this commits introduces the ability to use a local keyrings file, found

alongside the verification metadata.

This file can either be generated using regular tools like GPG, or via

command-line by adding the `--export-keys` flag when generating the

verification metadata.

    • -0
    • +75
    ./KeyringFilePublicKeyService.java
    • -0
    • +63
    ./PublicKeyServiceChain.java
  1. … 15 more files in changeset.
Add local keyring file

Fetching remote keys can be quite expensive. In order to avoid lookups,

this commits introduces the ability to use a local keyrings file, found

alongside the verification metadata.

This file can either be generated using regular tools like GPG, or via

command-line by adding the `--export-keys` flag when generating the

verification metadata.

  1. … 15 more files in changeset.
Add local keyring file

Fetching remote keys can be quite expensive. In order to avoid lookups,

this commits introduces the ability to use a local keyrings file, found

alongside the verification metadata.

This file can either be generated using regular tools like GPG, or via

command-line by adding the `--export-keys` flag when generating the

verification metadata.

    • -0
    • +75
    ./KeyringFilePublicKeyService.java
    • -0
    • +72
    ./PublicKeyServiceChain.java
  1. … 15 more files in changeset.
Fix unclosed resources

The Armored(Input|Output)Stream classes do _not_ close the underlying

stream.

  1. … 3 more files in changeset.
Fix unclosed resources

The Armored(Input|Output)Stream classes do _not_ close the underlying

stream.

  1. … 3 more files in changeset.
Fix unclosed resources

The Armored(Input|Output)Stream classes do _not_ close the underlying

stream.

  1. … 2 more files in changeset.
Fix unclosed resources

The Armored(Input|Output)Stream classes do _not_ close the underlying

stream.

  1. … 3 more files in changeset.
Initial implementation of verification of signatures

This commit introduces _signature_ verification. Signature verification

is stronger than checksum verification and must be enabled explicitly,

by adding `<signature-verification>true</signature-verification>` to the

dependency verification configuration file.

Once such verification is enabled, Gradle will do its best to verify

the signature of artifacts. This means:

- it will try to download the .asc file associated with an artifact

- if it's present, it will automatically download the public keys

of the signature and verify that the file matches the signatures

- if _any_ of the signature verification fails, fails the build

- if a public key is not trusted explicitly, fails the build

- if signature verification succeeds, no checksum verification is

performed

Currently it's not possible to perform checksum verification for some

modules and signature verification for others. All modules must declare

all trusted keys.

If a key cannot be downloaded, verification will fail. It's not possible

to ignore a key for now. It's not possible to fallback to checksum

verification.

  1. … 61 more files in changeset.
Initial implementation of verification of signatures

This commit introduces _signature_ verification. Signature verification

is stronger than checksum verification and must be enabled explicitly,

by adding `<signature-verification>true</signature-verification>` to the

dependency verification configuration file.

Once such verification is enabled, Gradle will do its best to verify

the signature of artifacts. This means:

- it will try to download the .asc file associated with an artifact

- if it's present, it will automatically download the public keys

of the signature and verify that the file matches the signatures

- if _any_ of the signature verification fails, fails the build

- if a public key is not trusted explicitly, fails the build

- if signature verification succeeds, no checksum verification is

performed

Currently it's not possible to perform checksum verification for some

modules and signature verification for others. All modules must declare

all trusted keys.

If a key cannot be downloaded, verification will fail. It's not possible

to ignore a key for now. It's not possible to fallback to checksum

verification.

  1. … 60 more files in changeset.
Initial implementation of verification of signatures

This commit introduces _signature_ verification. Signature verification

is stronger than checksum verification and must be enabled explicitly,

by adding `<signature-verification>true</signature-verification>` to the

dependency verification configuration file.

Once such verification is enabled, Gradle will do its best to verify

the signature of artifacts. This means:

- it will try to download the .asc file associated with an artifact

- if it's present, it will automatically download the public keys

of the signature and verify that the file matches the signatures

- if _any_ of the signature verification fails, fails the build

- if a public key is not trusted explicitly, fails the build

- if signature verification succeeds, no checksum verification is

performed

Currently it's not possible to perform checksum verification for some

modules and signature verification for others. All modules must declare

all trusted keys.

If a key cannot be downloaded, verification will fail. It's not possible

to ignore a key for now. It's not possible to fallback to checksum

verification.

  1. … 61 more files in changeset.
Initial implementation of verification of signatures

This commit introduces _signature_ verification. Signature verification

is stronger than checksum verification and must be enabled explicitly,

by adding `<signature-verification>true</signature-verification>` to the

dependency verification configuration file.

Once such verification is enabled, Gradle will do its best to verify

the signature of artifacts. This means:

- it will try to download the .asc file associated with an artifact

- if it's present, it will automatically download the public keys

of the signature and verify that the file matches the signatures

- if _any_ of the signature verification fails, fails the build

- if a public key is not trusted explicitly, fails the build

- if signature verification succeeds, no checksum verification is

performed

Currently it's not possible to perform checksum verification for some

modules and signature verification for others. All modules must declare

all trusted keys.

If a key cannot be downloaded, verification will fail. It's not possible

to ignore a key for now. It's not possible to fallback to checksum

verification.

    • -0
    • +142
    ./PublicKeyDownloadService.java
    • -0
    • +26
    ./PublicKeyService.java
    • -0
    • +89
    ./SecuritySupport.java
  1. … 61 more files in changeset.