Gary Casey
Gary Casey
@kalluriramkumar what are your thoughts so far re a fix? We can discuss in tomorrows early sync
Also - we should be able to do better than just "pad block" - can we improve the exception handling here in terms of intent and chaining and explanation? I'd...
> @cconstab : But it needs a minor change in sync_conflict_resolution code. Hence wanted to check with @gkc before pushing the changes. @kalluriramkumar What do I need to review?
We (@gkc @VJag @murali-shris and @kalluriramkumar) discussed this on Thursday Oct 13, @Vjag will review where we are and how we will fix this properly. @VJag when you are ready,...
@gkc and @VJag had follow-up discussion today. In summary, we need to break down this important lifecycle (delivery of shared encryption key to recipient) into several parts 1. Sender generates...
Burned 3SP in PR47. Moving to PR48. Estimate 8SP for implementation including extensive testing to ensure we have a rock-solid solution.
@VJag if you think this is 13SP please update the label
Continuing to send key in payload fixes one problem but does not address the issue regarding collision when more than one sender client is in play, and both of them...
True. But we need to agree that either (1) we will have a single shared encryption key per atsign pair (current intended behaviour) or (2) we can have multiple shared...
@cconstab once we've solved this for one AES key, the same pattern will work for many. We can start by making this work for what we have now - one....