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.

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

What is sct files #37

Closed
giolazzareschi opened this issue May 2, 2018 · 4 comments
Closed

What is sct files #37

giolazzareschi opened this issue May 2, 2018 · 4 comments

Comments

@giolazzareschi
Copy link

Hi,

I am currently using this nginx

  • nginx version: nginx/1.10.3 (Ubuntu)

And recompiled it with the "--add-module=/path/to/nginx-ct"

Now I'm configuring my nginx.conf file. I know that can be a silly question but I am not experienced with nginx enviroment and compilation. I am trying to put this on my nginx.conf file:

ssl_ct on;
ssl_ct_static_scts /path/to/sct/dir;

questions:

  • where is the SCT directory
  • what is the SCT files.
  • I already have "ssl on" directive, should I replace it for the "ssl_ct on" ?

Sorry for the very dummy questions but any help will be appreciated.

@Knight1
Copy link

Knight1 commented May 2, 2018

Short question: Do you use Let‘s Encrypt?

Because Let‘s Encrypt is currently submitting the signed certificate to the logs and give you a certificate with the act embedded. So you might not need this module if your current certs have the sct‘s embedded. If you do not know how to do this let me know :)

More infos: https://www.certificate-transparency.org/how-ct-works

@giolazzareschi
Copy link
Author

giolazzareschi commented May 2, 2018

Hi @Knight1

Thanks for the reply and for the observation.

Yes, I do use Let's Encrypt with certbot.

I did use this website https://cryptoreport.websecurity.symantec.com/checker/ to verify my CT and it tells me

  • Certificate Transparency: Not embedded in certificate

But how can I check if my certificate already have the sct's embedded?

Should I just renew it?

@Knight1
Copy link

Knight1 commented May 2, 2018

You can verify it by the issue date. If it is after 29 March it should have it; if not you can renew it if you want it. Do you want to deploy expect-ct or what is your intention behind it?

https://community.letsencrypt.org/t/signed-certificate-timestamps-embedded-in-certificates/57187/3

@giolazzareschi
Copy link
Author

giolazzareschi commented May 2, 2018

I understand.

Well, currently my webapp product is running in a lot of customers that are instructed to use Chrome for better experience and I do not want them to face any kind of "insecure website" or something.

I just knew about this CT a few days ago and I'm trying make everything works fine. But I think on the next renewall that's should be fine.

Thanks a lot for your help and attention. Much appreciated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants