• fixes:

  • eauth scries were broken for migrated peers
  • there was a space leak in %gall in which we were not removing outstanding %keens when hearing a %near or a %sage
  • %shut (multi-party remote scry) payloads, encrypted with keys created using 64 bytes of entropy would crash on the receiver if it had been migrated to |mesa, because we were asserting that the key was of length 32 (see %gulp task in %ames; currently not used by %gall)

• this opens the question of how to unify the three types of gifts that you might get using remote scry:

  • %tune, for public data via %fine
  • %near, for two (%chum) and multi-party (%shut) encrypted remote scry, via %fine
  • %sage, for any type of namespace +peek, via %mesa

%sage and %near are identical, a spar and maybe a page of data. %tune adds (using the $roar type) signature information at a specific life, but this information is not used by any of the client vanes (%clay, %gall, %eyre).

• options:
  • unifying all these gifts as one thing (e.g. a %near so we don't introduce new types)
    • %gall stills injects a %near with an empty response into an agent if there's been an error, or the plea asking for the encryption keys got nacked, so that suggest that %near might be a good candidate for unification
  • support %near/%tune for backwards compatibility, but favoring %sage for 409k?
  • %ames (both |ames and |mesa cores) give only a %sage as the response for a +peek