Init should also be encrypted to self

[Powersource]

for ssbc/ssb-tribes2#40

implemented in ssbc/ssb-tribes2#56

[staltz]

LGTM, but I'm not an expert in this repo

[Powersource]

i guess i'm curious if "to yourself" should be specified further or if we leave that to the actual encryption parts of the spec(s)

[mixmix]

same as other PR - using own_key, or we link to part of spec that is relevnt

[Powersource]

i'm confused what own_key means, i can only find it mentioned here https://github.com/ssbc/private-group-spec/blob/master/direct-messages/README.md and it's very brief. It says

Instead, when you see your own feed_id as a recipient, you're expected to map that to a private symmetric key, own_key

but how does that mapping work?

[mixmix]

🔥 this needs to be changed to clarify:

var group_key = { key, scheme: 'xxxxx' }      // key is symmetric key as buffer
var own_key = { key, scheme: 'yyyy' }          // key is a symmetric key as a buffer
var msg_key =  ... make up a one use key for the msg as a buffer

put in actual strings for xxxxx, yyyyy
And check what I'm saying makes sense in the code

[mixmix]

envelopejs

[Powersource]

i have no idea how own_key works and it's not really documented, how would i explain it to someone else lol? Different PR?

[mixmix]

It's here https://github.com/ssbc/private-group-spec/tree/master/direct-messages#b-self-case---mapping-our-own-feed_id-to-recp_key

Could be in a clearer space but some of these ideas have evolved as we've used them and talked about them.

[Powersource]

Ah thanks it actually does mention the scheme, I'll fix.

Two issues with that section though #28 #29

[Powersource]

i think i fixed this now

[Powersource]

@mixmix

[mixmix]

looks perfect