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.

Sign up for GitHub

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

Jump to bottom

Check JAR/POM/DB checksums to ensure integrity over time #149

Open
technomancy opened this issue May 3, 2013 · 2 comments
Open

Check JAR/POM/DB checksums to ensure integrity over time #149

technomancy opened this issue May 3, 2013 · 2 comments
Labels
security

Comments

@technomancy
Copy link
Collaborator

We should set up periodic backups of jar/pom checksums and the DB so that it's easier to confirm we haven't been affected by possible attacks in the future.
@technomancy
Copy link
Collaborator Author

Open to suggestions of where these should go. Since they need to be initiated from off the box, we can't really use S3; we need another independent host to perform an rsync and save off checksums.

@devn
Copy link
Contributor

devn commented Jul 8, 2014

Does "no S3" also mean "no AWS"?

@xeqi xeqi added the security label Oct 1, 2014
@danielcompton danielcompton changed the title Remediation of Linode compromise Check JAR/POM/DB checksums to ensure integrity over time Jan 10, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
security
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@technomancy @devn @xeqi