Conversation

Notices

1. :abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: (kaniini@pleroma.site)'s status on Wednesday, 17-Jul-2019 15:50:57 EDT :abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy:
   parts 1 and 2 of our "secure mode" implementation are now merged.
   
   now to do part 3: signing outbound object fetches with the instance fetch actor.
   1. :abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy: (kaniini@pleroma.site)'s status on Wednesday, 17-Jul-2019 15:52:34 EDT :abunhdhappyhop: :abunhdhappy: :abunhdhop: :abunhd: :abunhdhappyhop: :abunhdhappy:

      in reply to
      part 4 is the easy part, mapping signed fetches as proof of possession of the "fetch" capability.
      
      note that i keep talking about mapping signatures from specific actors to capabilities. this is so that *internally* it's all translated OCAP. that means once OCAP is ready, we can just flip a switch and have it.