increase s3_url_ttl from 15m to 8h

tired of endless CHEF-3045 complaints on the mailing list.

403s on long chef runs are not delightful.

any attacker than can issue a replay attack inside of an 8 hour window
can also issue a replay attack within a 15 minute window, so having this
timeout be shorter does not prevent any attacks (15 minutes is already
an eternity to any kind of automated attack tool).
Merge pull request #63 from opscode/lcg/increase-s3-ttl

increase s3_url_ttl from 15m to 8h
Set correct maintainer and homepage.

This data is important when publishing to Artifactory as it’s used in
the underlying package path in the repo (e.g. `com/getchef`).
Merge pull request #76 from opscode/schisamo/fix-homepage

Set correct maintainer and homepage.
Update CHANGELOG with latest commits

This notes the commits to update the maintainer and homepage
and to increase the s3_url_ttl. Both of these are minor, but should be
noted
initctl stop chef-server-runsvdir leaves orphaned processes

The right thing to do would be to have 'kill signal HUP' in
the Upstart config so everything gets taken care of cleanly
when you use upstart to stop the runsvdir process. But that
stanza isn't available in Ubuntu 10.04. Without that stanza
Upstart sends a TERM which kills runsvdir and orphans all the
rest of its process tree.

This fix does the same thing Enterprise Chef server does. It
stops Chef services in a pre-stop script.
Update CHANGELOG with note about fix for PR 73
Merge branch 'mm/fix_chef-server-runsvdir.conf'
Add support for TLS 1.1 / 1.2 to Nginx config
Remove SSLv3 and update ciphers

Using the Mozilla recommended cipher suite from
https://wiki.mozilla.org/Security/Server_Side_TLS#Recommended_Ciphersuit
e
Update comments per delano