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

Only for internal communication; Put in place our own Certificate Authority and sign our self-signed certificates with it #125

Open
renoirb opened this issue Mar 12, 2015 · 1 comment

Comments

@renoirb
Copy link
Member

renoirb commented Mar 12, 2015

This will allow us to have under TLS everything that isn’t yet AND to make sure where its in use that we can also check if we should trust the client connecting to a given service.

Connecting through TLS isn’t a statement that the connection should be trusted. But sniffing the certificate, check if we accept the origin of the certificate it provided is a step toward that goal.

Estimated steps

  • Create self-signed certificate
  • Document how to do
  • Make sure the new self-proclaimed CA certificate we created is archived and accessible exclusively to W3C team members
  • ... ?

Notes

  • apt-get install gnutls-bin
  • Look for certtool
  • Self signed certificate and becoming our own authority for internal comm

See GnuTLS documentation.

@renoirb
Copy link
Member Author

renoirb commented Mar 12, 2015

Related to #70?

@renoirb renoirb removed their assignment Sep 21, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant