You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: deployment/live/aws/test/README.md
+21-35Lines changed: 21 additions & 35 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -168,46 +168,35 @@ go run github.com/google/certificate-transparency-go/trillian/integration/ct_ham
168
168
169
169
### With real HTTPS certificates
170
170
171
-
We'll run a TesseraCT and copy certificates from an existing RFC6962 log to it.
172
-
It uses the [ct_hammer tool from certificate-transparency-go](https://github.com/google/certificate-transparency-go/tree/aceb1d4481907b00c087020a3930c7bd691a0110/trillian/integration/ct_hammer).
171
+
We'll run a TesseraCT instance and copy certificates from an existing RFC6962
172
+
log to it. It uses the [preloader tool from certificate-transparency-go](https://github.com/google/certificate-transparency-go/blob/master/preload/preloader/preloader.go).
Since the source and destination log [might not be configured the exact same set of roots](/internal/lax509/README.md#Chains), it is expected to see errors when submitting a certificate chaining to a missing root. This is what the error would look like:
224
+
225
+
```
226
+
W0623 11:57:05.122711 6819 handlers.go:168] test-static-ct: AddPreChain handler error: failed to verify add-chain contents: chain failed to validate: x509: certificate signed by unknown authority (possibly because of "x509: cannot verify signature: insecure algorithm SHA1-RSA" while trying to verify candidate authority certificate "Merge Delay Monitor Root")
227
+
```
228
+
229
+
## Cleanup
230
+
245
231
> [!IMPORTANT]
246
232
> Do not forget to delete all the resources to avoid incuring any further cost
247
233
> when you're done using the log. The easiest way to do this, is to [close the account](https://docs.aws.amazon.com/accounts/latest/reference/manage-acct-closing.html).
Copy file name to clipboardExpand all lines: deployment/live/gcp/test/README.md
+19-35Lines changed: 19 additions & 35 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -141,37 +141,26 @@ go run ./trillian/integration/ct_hammer \
141
141
### With real HTTPS certificates
142
142
143
143
We'll run a TesseraCT instance and copy certificates from an existing RFC6962
144
-
log to it. It uses the [ct_hammer tool from certificate-transparency-go](https://github.com/google/certificate-transparency-go/blob/master/trillian/integration/ct_hammer/main.go).
144
+
log to it. It uses the [preloader tool from certificate-transparency-go](https://github.com/google/certificate-transparency-go/blob/master/preload/preloader/preloader.go).
Clone the [certificate-transparency-go](https://github.com/google/certificate-transparency-go) repo, and from there run `ct_hammer` in a different terminal:
180
+
In a different terminal, run `preloader` to submit certificates from another log to TesseraCT.
Since the source and destination log [might not be configured the exact same set of roots](/internal/lax509/README.md#Chains), it is expected to see errors when submitting a certificate chaining to a missing root. This is what the error would look like:
192
+
211
193
```
194
+
W0623 11:57:05.122711 6819 handlers.go:168] test-static-ct: AddPreChain handler error: failed to verify add-chain contents: chain failed to validate: x509: certificate signed by unknown authority (possibly because of "x509: cannot verify signature: insecure algorithm SHA1-RSA" while trying to verify candidate authority certificate "Merge Delay Monitor Root")
0 commit comments