August 13 - 19

upgraded test environment to Confluence 3.3.1
- tested for issues, seems to be cool de-la
  - they have addressed the cross-site request forgery vulnerability in the 3.3.x line
  - fortunately for us, Atlassian accelerated their minor revision timeline due to a security vulnerability that was introduced in 3.3.0
major issues (aside from aforementioned XSRF) from ISO vulnerability assessment:
- https://issues.its.utexas.edu/jira/browse/CONF-107
- https://issues.its.utexas.edu/jira/browse/CONF-108
- discussion with Tom regarding these issues
  - all security related patches released by the vendors are backported to the versions we currently run – Apache 2.2.3 and OpenSSH 4.3 – and should address the issues outlined in the referenced issues
- communications with ISO regarding all of the above
enabled trusted connection between JIRA and Confluence
- the system clocks are off by between 30 and 90 seconds and, as a result, the connection does not get properly established
user support, correspondence

assisted SIS with retrieving Tomcat logs from their (issues.reg.utexas.edu --> jira02.austin.utexas.edu) instance
assisted ECS with loading their new license key
other user support, correspondence

troubleshooting for capps.its virtual server
- runaway OpenSSL process was using 99.9% of the CPU – process was promptly killed

meeting with Mic regarding PHP-WURFL inefficiencies
- we will have a test run next Wednesday, August 25 to determine whether we need to use a caching library and if it should be in the x86 environment

meeting with Jason and Dr. Stahl regarding a contract opportunity with the Economics department supporting Dr. Stahl's research

made sure that all of the hosting team's services were running following the network maintenance window on Sunday, August 15

need to schedule maintenance to upgrade production environment to 3.3.1
waiting to hear back from the ISO regarding second application scan on the upgraded test environment