Cached attributes

[Alan DeKok]

On Feb 25, 2016, at 8:28 AM, Jonathan Gazeley <Jonathan.Gazeley at bristol.ac.uk> wrote:
> I'm trying to figure out how to cache other stuff with the TLS attributes that can be pulled back later on.

  The TLS caching in v2 is (a) just a few hard-coded attributes, or (b), files on disk.  The explanations in the EAP module work.

  For v3.0, the same largely applies.  We've re-worked the on-disk TLS cache a bit, but it *should* work identically.  We've also added a cache module, which can cache just about anything.

  In 3.1, we've gotten rid of the on-disk TLS cache, and expanded the cache module to cache to just about anywhere... including disk.  So the functionality is at least equivalent, if a little different.

  So... what's going wrong?

  Alan DeKok.