Skip to content
This repository has been archived by the owner on May 1, 2018. It is now read-only.

Security Considerations #11

Open
andyleejordan opened this issue May 9, 2014 · 3 comments
Open

Security Considerations #11

andyleejordan opened this issue May 9, 2014 · 3 comments
Assignees

Comments

@andyleejordan
Copy link
Owner

I'm going to play it very safe and test extensively on a Vagrant box with Trusty Tahr. Once that's working, we'll upgrade DigitalOcean.

@andyleejordan
Copy link
Owner Author

With 058b318, my manifests seamlessly support different versions of Ubuntu.

@andyleejordan
Copy link
Owner Author

You know, it's also tempting to switch to Fedora.

@andyleejordan andyleejordan changed the title Update to 14.04 Security Considerations May 12, 2014
@andyleejordan
Copy link
Owner Author

Also should look into CentOS and FreeBSD. The latter would be the most difficult due to the change in OS, and therefore major change to Puppet manifests. I do want to move away from Canonical though.

Dr. Conte de Leon recommended setting up a whitelisted outbound firewall, ensuring latest repositories for my services are being used, using Bastille (I think Tiger had an interface for it as well), and carefully scanning with nmap and OpenVAS.

I am also considering separating suchcodemuchlove.com onto its own server; however, Gitlab really highly recommends at least 1 GB of RAM. It could work on 512 MB, but eh.

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

No branches or pull requests

1 participant