Skip to content

Conversation

@michaelwasserman
Copy link

@sebastianbenz, please take a look, thanks!
AFAICt, these aren't published on the CWS, so we don't need to update anything else?

"128": "icons/icon128.png"
}
},
"trial_tokens": ["AortO/ru/uAQc706UhFjd8r06YtFO/Yeh1aim8uWRnfHcT8shd6yIjHf3q4sIx6FlJO9JrxWqzM2YSMbInVAZAsAAAB7eyJvcmlnaW4iOiJjaHJvbWUtZXh0ZW5zaW9uOi8vbW1iaGxhbWFmZmZwaGNoY2NkaWtvcGJsa2ZrYWNhbmoiLCJmZWF0dXJlIjoiQUlQcm9tcHRBUElNdWx0aW1vZGFsSW5wdXQiLCJleHBpcnkiOjE3ODE1NjgwMDB9"]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this token bound to an origin? If so, we likely need to use the key field to ensure that the extension has a consistent origin when loaded for all users.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes! I used the origin I observed from window.location when side-loading each unpacked extension.
Can you help get keys? I'm not yet a registered CWS developer.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated, I think I did this right. Thanks for your guidance and review!

Generated keys from per-dir command:
openssl genrsa 2048 | openssl pkcs8 -topk8 -nocrypt -out key.pem
Re-registered OT tokens using new cross-device-consistent development extension ids.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants