Add support for Browser in /e/ OS#6885
Conversation
|
Thank you for your contribution! We've added this to our internal tracking system for review. Details on our contribution process can be found here: https://contributing.bitwarden.com/contributing/pull-requests/community-pr-process. |
|
This was raised around 3 years ago and it was closed by devs without merging. |
| "build": "release", | ||
| "cert_fingerprint_sha256": "FD:8B:1E:55:5D:40:2A:47:ED:3B:72:F3:C4:73:82:5E:A7:D2:FD:9E:C7:AD:36:60:7C:2C:E0:04:C2:10:08:06" | ||
| }, | ||
| { | ||
| "build": "release", | ||
| "cert_fingerprint_sha256": "FE:36:B0:0A:C2:F0:5F:2E:29:50:33:C6:DE:C2:4E:A4:52:0E:D4:39:24:59:39:74:8D:8F:03:A5:E0:C1:90:A9" |
There was a problem hiding this comment.
@lucasmz-dev /e/OS has both official and community builds, and they use different signing keys for browser.
There was a problem hiding this comment.
Is it the same for all community builds...? Because I could see this being resigned by every maintainer and it would be crazy to add every unofficial build here
There was a problem hiding this comment.
It's kind of weird that it is different at all to me. There's like prebuilts too
There was a problem hiding this comment.
@lucasmz-dev Both official and community builds are made by /e/OS team. So it's same for all.
There was a problem hiding this comment.
Community builds are not officially tested by the team for each devices. That's why it's seperated. Unofficial builds type is usually called 'test'. Which is not included in this list as it uses public keys.
3 participants
🎟️ Tracking
📔 Objective
Add support for /e/ OS browser .
📸 Screenshots