-
Notifications
You must be signed in to change notification settings - Fork 137
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
This adds support for using encrypted Tink keysets to load a signer. There are two main benefits from this work: We can leverage this instead of KMS if we need to support a higher QPS, and Tink keysets use strong secure defaults. Keysets can be encrypted with AESGCM, do not rely on a KDF, cannot be brute-forced, and access to the key can be audited through cloud audit logs. Tink does not provide a method to extract the signing key from the keyset intentionally, so I wrote a helper library to reach into the key handle proto to construct a crypto.Signer. Signed-off-by: Hayden Blauzvern <hblauzvern@google.com>
- Loading branch information
1 parent
aa83789
commit f291e2e
Showing
12 changed files
with
738 additions
and
15 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,73 @@ | ||
// Copyright 2022 The Sigstore Authors. | ||
// | ||
// Licensed under the Apache License, Version 2.0 (the "License"); | ||
// you may not use this file except in compliance with the License. | ||
// You may obtain a copy of the License at | ||
// | ||
// http://www.apache.org/licenses/LICENSE-2.0 | ||
// | ||
// Unless required by applicable law or agreed to in writing, software | ||
// distributed under the License is distributed on an "AS IS" BASIS, | ||
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | ||
// See the License for the specific language governing permissions and | ||
// limitations under the License. | ||
|
||
package main | ||
|
||
import ( | ||
"flag" | ||
"fmt" | ||
"log" | ||
"os" | ||
|
||
"github.com/google/tink/go/keyset" | ||
"github.com/google/tink/go/signature" | ||
"github.com/sigstore/fulcio/pkg/ca/tinkca" | ||
) | ||
|
||
/* | ||
To run: | ||
go run cmd/create_tink_keyset/create_tink_keyset.go \ | ||
--kms-resource="gcp-kms://projects/<project>/locations/<region>/keyRings/<key-ring>/cryptoKeys/<key>/versions/1" \ | ||
--output="enc-keyset.cfg" | ||
You can also create a GCP KMS encrypted Tink keyset with tinkey: | ||
tinkey create-keyset --key-template ECDSA_P384 --out enc-keyset.cfg --master-key-uri gcp-kms://projects/<project>/locations/<region>/keyRings/<key-ring>/cryptoKeys/<key>/versions/1 | ||
You must have the permissions to read the KMS key, and create a certificate in the CA pool. | ||
*/ | ||
|
||
var ( | ||
kmsKey = flag.String("kms-resource", "", "Resource path to KMS key, starting with gcp-kms:// or aws-kms://") | ||
outputPath = flag.String("output", "", "Path to the output file") | ||
) | ||
|
||
func main() { | ||
flag.Parse() | ||
if *kmsKey == "" { | ||
log.Fatal("kms-resource must be set") | ||
} | ||
if *outputPath == "" { | ||
log.Fatal("output must be set") | ||
} | ||
|
||
kh, err := keyset.NewHandle(signature.ECDSAP384KeyWithoutPrefixTemplate()) | ||
if err != nil { | ||
log.Fatal(err) | ||
} | ||
|
||
primaryKey, err := tinkca.GetPrimaryKey(*kmsKey) | ||
if err != nil { | ||
log.Fatal(err) | ||
} | ||
|
||
f, err := os.Create(*outputPath) | ||
if err != nil { | ||
log.Fatal(err) | ||
} | ||
defer f.Close() | ||
jsonWriter := keyset.NewJSONWriter(f) | ||
if err := kh.Write(jsonWriter, primaryKey); err != nil { | ||
fmt.Printf("error writing primary key: %v\n", err) | ||
} | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.