Github user jacksontj commented on the pull request:
https://github.com/apache/trafficserver/pull/189#issuecomment-96038933
With that behavior it means that you have yo atomically add the new key to
all hosts within a Colo, which is difficult to say the least. Since we
can't really guarantee that it is atomic we want some wiggle room, which
renewing out of the middle gives us.
On Apr 24, 2015 12:04 PM, "Bin" <notificati...@github.com> wrote:
> ATS does not review tickets using the middle key. Here is how it works.
> When you rotate the key, you push a new key to the head of the key file
and
> remove one from the tail of the file. The new key will be used to encrypt
> session tickets and the rest are only used to decrypt session tickets. The
> middle keys are not used to encrypt any more because they are retired and
> only used to resume sessions.
>
> â
> Reply to this email directly or view it on GitHub
> <https://github.com/apache/trafficserver/pull/189#issuecomment-96037112>.
>
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
