-
Notifications
You must be signed in to change notification settings - Fork 248
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CT Log Deployment (Manual) is COMPLETELY OUTDATED #1060
Comments
Hi @yacoubhanna, Thanks for the report. I'd be interested to hear how you get on with the tweaks I've made in #1061. I'm able to get |
Hello @AlCutter. Thank you so much for the update. However, when I get to the ctclient step to run it. It doesn't work. more specifically I was not able to run this command.
Can you please tell me the exact step that you did in order to run the ct_server and the ctclient. Thank you for your time. |
@yacoubhanna We have updated the manual deployment doc in #1061. Please try if the following command works for you.
|
Hi @yacoubhanna, just to add to Roger's reply - if you still can't get it to work with the updated command Roger copied into his comment above, it would greatly help us to help you if you could include the output of the failed commands too. Cheers, |
I ran the command that @roger2hk gave me and I got that error:
I followed all the steps that are on the Manual Deployment I started the log server and that was the output
Then started the log signer and the output was
Then createtree and I got that output
Then created the keys using these commands
However, when I get to run the next step which is
I got that error
Just to mention if you go to ctclient there is no file called ctclient. It was there in the previous versions, but it was taken out while updating. That was line 266 in the ManualDeployment.md file
It does make sense why I am getting this error since I didn't initiate anything on the 6966 port, and in the manual setup, they didn't mention anything about that 6966 port. Thank you so much for your help. |
@yacoubhanna For the export PATH="$HOME/go/bin:$PATH" |
Thank you @roger2hk. After I ran
I ran this command
and I didn't get the same error as before, but I got that
I ran this command:
and got this
|
@yacoubhanna Unfortunately the doc is outdated. Here is the correct command for go run github.com/google/certificate-transparency-go/client/ctclient@master get-roots --log_uri http://localhost:6966/aramis
Here is the correct command for go run github.com/google/certificate-transparency-go/client/ctclient@master get-sth --log_uri http://localhost:6966/aramis --pub_key pubkey.pem
|
Hello @roger2hk I ran go run github.com/google/certificate-transparency-go/client/ctclient@master get-sth --log_uri http://localhost:6966/aramis --pub_key pubkey.pem and got the same error for both
go run github.com/google/certificate-transparency-go/client/ctclient@master get-roots --log_uri http://localhost:6966/aramis
Thank you for your help |
@yacoubhanna The connection refused was caused by the missing CTFE server. The manual deployment doc doesn't mention any command to start the CTFE server but there is a link to the integration demo script. If you aim to try how Trillian and CTFE work, you can follow the Docker version deployment. The commands there are verified a few weeks ago. It will take some time rewrite the whole CT log deployment (manual) doc. |
Hi @roger2hk , log-rpc-server-pkcs11.privkey.pem I have never skipped a step, but I am not sure whether I missed something or not. On the other hand, after I started certificate transparency container in terminal 1 I got this message for the trillian log server: ctfe-trillian-log-server-1 | E0509 20:13:08.208604 1 tree_gc.go:90] DeletedTreeGC.Run: error listing trees: Error 1146 (42S02): Table 'test.Trees' doesn't exist Is that something expected? I am asking this because in the succeeding steps we are supposed to kill the first docker container running in terminal 1 and restart it by another but similar command. Regards, |
I have figured it out. It is my bad, but I was under the impression that "/trillian/testdata/fake-ca.cert" file must be in "/git/trillian" directory because the last time we changed the directory is when we get in "/git/trillian" directory. That's why the program couldn't find the certificate and freaked out. Best, |
@samettonyali It is expected to see the table doesn't exist error before importing the SQL to create tables.
|
I was trying to follow the steps at CT Log Deployment in order to run the log_server and the log_signer and they can not be found in their directories. I found them in trillian/cmd. Also, I tried to run CT Personality and the ctclient can not be found anywhere.
I even ran the Docker Containerized and had the same problem
Could you please update it?
The text was updated successfully, but these errors were encountered: