I built a signed version for Firefox if either of you minds trusting a random internet person. Sorry for dragging up an old thread here, but I went ahead and modified the colors a tad, build the extension and have it loaded into my chrome, however, no matter what I seem to do, I can't get it to work with my selfhosted "vaultwarden" instance even though the extensions in the store seem to work just fine without any issue. In the folder "images" of the extension, i change the existing ones :) Where did you change the color of the icon ? This is going too deep for me, but its another possible maybe you (or someone else) can publish your recompiled version of Bitwarden extension to Chrome Web Extensions Store (and Firefox too), to make it publicly available for all others? Or the license don't allow to do Thanks :) You could even go crazy and (breaking the rules) color the Bitwarden icon a different color or something. Then you could have both side by side in the same Chrome instance. You could also come up with a workflow that involves accessing the web vault at though thats cumbersone too.Īnother crazy idea would be to clone the repo, rename the app to something else slightly different, build it yourself and install it by hand into Chrome. Those options don't work in all scenarios either (like if you are using a Chromebook then you're locked into Chrome and you can't install a desktop app). Neither option is perfect, but I've ended up staying with Option 2 for several months now and have gotten used to it being that way. This has the added advantage that everything in Vivaldi is personal and everything in Chrome/Firefox is work. Option 2) Use Chrome/Firefox with plugin for Work Vault and Vivaldi with plugin for Personal Vault. I log into the Chrome Plugin with whichever vault I need to access most often.
Option 1) by having the plugin installed in Chrome logged into Vault A and then I've installed the desktop app and had it logged into Vault B.
0 kommentar(er)
