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

[xenial] ensure OSSEC alert is sent pointing to xenial upgrade docs #4147

Closed
redshiftzero opened this issue Feb 15, 2019 · 1 comment
Closed
Assignees
Milestone

Comments

@redshiftzero
Copy link
Contributor

Followup from the stretch goal in #4104, this ticket is to ensure that on Trusty on 0.12.0~rc2 an OSSEC alert is indeed sent containing a pointer to the Xenial upgrade guide at https://securedrop.org/xenial-upgrade.

See the test plan in #3546 for how to test this - note that the notification is sent on a weekly basis.

If the alert is not being sent for some reason, then the implementer of this ticket should investigate why and resolve. See #4116 for various ideas on how to do this.

@redshiftzero redshiftzero added this to the 0.12.0 milestone Feb 15, 2019
@redshiftzero redshiftzero self-assigned this Feb 15, 2019
@redshiftzero
Copy link
Contributor Author

Following steps in #3546, I verified in Trusty staging VMs (with OSSEC enabled) that an OSSEC alert will be sent with the expected message:

gpg: encrypted with 4096-bit RSA key, ID 0xEECE0DDC6DCB11EF, created 2015-03-16
      "Freedom of the Press Foundation <[email protected]>"

/etc/cron.weekly/update-notifier-common:
New release '16.04.5 LTS' available.
Visit https://securedrop.org/xenial-upgrade for more information

This is working as expected, so no further action is needed. Closing!

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