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

Core Infrastructure Initiative (CII) Best Practices #291

Open
ypid opened this issue Jul 12, 2016 · 2 comments
Open

Core Infrastructure Initiative (CII) Best Practices #291

ypid opened this issue Jul 12, 2016 · 2 comments

Comments

@ypid
Copy link
Contributor

ypid commented Jul 12, 2016

Hey @timthelion

I found https://bestpractices.coreinfrastructure.org and thought it might also be a good fit for this project. Do you want to add subuser there and go thought the criteria?

References

@timthelion
Copy link
Contributor

This looks interesting.

Currently, I'm missing https.

subuser.org is hosted on a VPS running within a huge OpenVZP/ZFS server farm. I'm definitely not the only one with root access to my VPS (my service providers also have access).

If I use Let's Encrypt then I'm also putting my trust in them that they won't sign any fake certificates. And indeed, this is always the case. https://en.wikipedia.org/wiki/Certificate_authority#CA_compromise

Https provides MITM attack prevention at the consumer end point level, but the level of trust that we've come to put in https is horribly misplaced. I wish that organizations like Mozilla and coreinfrastructure.org would stop promoting the standard as a security and privacy mechanism.

@ypid
Copy link
Contributor Author

ypid commented Jul 12, 2016

Sure https is not ideal. But I think things like HPKP (HTTP Public Key Pinning) can help with that (to some extend). Also TLS is just transport security. We still have other means like GPG.

To your other question, that is something I have been thinking about 😉 debops/debops-playbooks#274

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

2 participants