Browser support wanted for Epic Privacy Browser

MacPass
MacPass
Community Member

How about supporting the Epic Privacy Browser?

http://www.epicbrowser.com/

This browser seems to be aligned with the security concepts of AgileBits. I know that you don't have a browser extension for it. I also tried the global 1Password 4 MenuBar item, after first making Epic Privacy Browser my default browser. It didn't work. The best I could do was cut and paste the user name and password for a website from my 1Password application. However, putting this information on the clipboard weakens security.

Thanks,
Len

Comments

  • rpali
    rpali
    Community Member

    I've just learned about this browser and I'd like to see 1Password support it as well. They'd make a great team!

  • Megan
    Megan
    1Password Alumni

    Hi @MacPass and @rpali,

    Thanks so much for the feedback here! I'll admit, I haven't heard much about the Epic browser before, but I'd be happy to pass along your request to our developers.

    In the meantime, if you are concerned about items on your clipboard Len, please make sure you have the Preferences > Security settings adjusted to clear your clipboard contents after an appropriate amount of time, so you are keeping things as secure as possible. :)

  • 2manyBits
    2manyBits
    Community Member

    Any updates on an Epic browser extension? They have one for Last Pass.

  • Megan
    Megan
    1Password Alumni

    Hi @2manyBits‌

    Thanks for checking in on us! I don't have any updates at this time, but I'll be happy to let our developers know that you're interested in this. :)

  • Incanto
    Incanto
    Community Member

    Let me add my vote to this: It's would be a great service for you to create a browser extension for Epic. The browser is based on Chromium, same as Google Chrome, so it should be possible. Check out Epic. The philosophy is right in line with your own.

  • Megan
    Megan
    1Password Alumni

    Hi @Incanto‌

    Thanks so much for adding your vote here. :)

  • 2manyBits
    2manyBits
    Community Member

    Hi Megan, Any updates on this? I just tried to install the Chrome ext. and it of course didn't work.

  • Megan
    Megan
    1Password Alumni

    Hi @2manyBits‌

    Thanks for checking in on us! Could you tell me a bit more about how the extension isn't working?

    Because Epic browser is Chromium based, the Chrome extension should install just fine. The tricky part is that 1Password 4 requires all browsers to be properly code signed as a security measure, and Epic browser is not currently on our accepted list. If you go into Preferences > Advanced, you can disable the 'Verify browser code signature' option, you should be able to use the Chrome extension in Epic browser.

    That being said, I'd be happy to add your vote to the request in our issue tracker to provide more official support for Epic browser. :)

    internal reference number: OPM-2075

  • Hi @2manyBits‌,

    Thanks for following up about this! I have a few more details to add to what @Megan said.

    We've recently been looking into supporting Epic Privacy Browser. Our attempts to install our Chrome Extension (a CRX file, the same one used by Chrome, Chromium, Opera, and some other Chromium based browsers) were not successful. Like you, we weren't able to add the 1Password extension to Epic. While Epic is a Chromium based browser, it does not allow extensions to be installed using a CRX file (I'm assuming for privacy/security reasons).

    In 1Password 4, we validate the code signature of each browser we receive connections from. This validates that the browser has not been tampered with and comes from the developer that it claims to come from. We currently support the code signatures of several browsers such as Safari, Chrome, and Firefox. However, for browsers we don't officially support, such as most Chromium based browsers, our Chrome extension works just fine if you disable code signature validation like Megan described above. Supporting new browsers (the code signature aspect anyway) is certainly a possibility. We recently added support for WhiteHat Aviator, another Chromium based browser, which seems to have a somewhat similar purpose as Epic. However, WhiteHat Aviator and many other Chromium based browsers allow extensions to be installed directly using a CRX file. Epic Privacy Browser doesn't, which is the main problem here.

    With help from the Epic developers, we were able to confirm that our Chrome extension does in fact appear to work fine in Epic Privacy Browser (with code signature validation disabled). Adding Epic Privacy Browser to our code signature verification list is a possibility, but again, the main problem is installing it into a browser that doesn't normally allow extensions. This is something we are investigating with the developers of Epic, but unfortunately we can't make any promises if or when the 1Password browser extension will be installable in Epic Privacy Browser.

    Please let us know if you have any other questions. :)

  • lsnow11
    lsnow11
    Community Member

    I realize that this is a pretty old thread, and that you've already explained the challenges involved, but adding a vote for Epic support.

  • Megan
    Megan
    1Password Alumni

    Hi @lsnow11‌

    Thanks for adding your vote here!

  • I have been hoping that since this thread had started in 2013, and that we are now on 1Password v5, that we would have a browser extension for the Epic browser by now. Currently, Epic supports Roboform and Lastpass. Roboform doesn’t seem to be able to import a 1Password.backup in text format, although it says it can - for every entry it says there is a parsing problem. I haven't used Lastpass since I found 1Password when it was v3. I didn’t like it then and I don't like it now, but it seems that I have no choice. Is there any news of progress on this, or alternatively any work around to get 1Password to work in Epic? Thank you

  • littlebobbytables
    littlebobbytables
    1Password Alumni

    Hi @pwillis‌

    We're still in communication with the people behind the Epic Privacy Browser but I don't know where things stand at the moment. My understanding is they take a particular approach to extensions which for reasons outside my domain of knowledge mean it isn't a case of simply supplying a copy of the Chromium extension.

    From what I can gather there isn't a workaround as the Epic Privacy Browser is purposely designed to limit what extensions you can load and use.

    Sorry I don't have better news to report.

  • dsjr2006
    dsjr2006
    Community Member

    +1 vote

  • littlebobbytables
    littlebobbytables
    1Password Alumni

    @dsjr2006‌ duly noted :smile:

  • applguy
    applguy
    Community Member

    Hi Jasper P & Megan & littlebobbytables,
    I've followed this thread for support of 1 Password in the Epic Browser. A few posts ago I read JasperP's response "While Epic is a Chromium based browser, it does not allow extensions to be installed using a CRX file (I'm assuming for privacy/security reasons)."
    I realize that maybe JasperP might be a programmer or a high-level agilebits Team Member... stating that Epic doesn't allow CRX files is certainly not true. I'm running the Epic Browser on a Mac and a Windows 7 Ultimate machine and downloaded the 'evernote_web_clipper.crx' file to Epic that is available in the Epic Webstore.
    I say this to bring up the fact that Epic does support CRX files.! I've enclosed a copy of the 'screen shot' for your inspection of the file. I'm not sure how to 'point' Epic to the 1 Password crx file... but Epic doesn't have a problem installing Evernotes Web Clipper crx file.

  • Jasper
    edited June 2015

    Hi @applguy,

    As far as I know, Epic Privacy Browser does not allow every CRX file compatible with Chrome to be installed directly. It must be special version downloaded from the Epic Webstore.

    Our extension is distributed via the Chrome Web Store and directly from our website, therefore isn't supported. The Evernote extension you installed does work, because it was distributed via the Epic Webstore.

    WhiteHat Aviator and many other Chromium based browsers allow extensions to be installed directly using a CRX file. Epic Privacy Browser doesn't, which is the main problem here.

    The example I used above, WhiteHat Aviator, is able to use the Chrome extension downloaded directly from our website. You can install any CRX file into WhiteHat Aviator. Epic only supports extensions from their own Webstore, and we don't have a separate version of our extension for Epic Privacy Browser.

    We only develop an extension for Safari, Chrome, and Firefox currently. All other supported browsers use one of these existing extensions. And we don't distribute our extension via many add-on galleries. We do use the Chrome Web Store, but we aren't in the galleries for Firefox or Opera, for example.

  • chip3mck
    chip3mck
    Community Member

    Not pleased with the lack of progress.
    What is your action plan to resolve this issue?

  • littlebobbytables
    littlebobbytables
    1Password Alumni

    Hi @chip3mck,

    Short term the answer is you won't see the 1Password extension in Epic webstore for the reasons @JasperP has already stated. I do realise it isn't what you want to hear and that such a statement may make you unhappy. The bitter truth is that resources are always limited and demand for resources usually outstrips that. We have to prioritise and sometimes make decisions that won't be taken well. That's a general statement that holds true of pretty much most aspects of life in general. In terms of browser support the top three plus those willing to handle the generalised Chromium extension are what we're able to support.

    As it happens, a significant amount of work is being done on the filling logic. We hope to massively simplify the extension while improving how it behaves. This is being achieved by pushing the filling logic into 1Password and my understanding is the extension would become more of just a bridge. At that stage we may be able to consider supporting more browsers but that certainly isn't a guarantee. It will depend on no doubt many factors but at some point in the future we may be better placed to evaluate again.

This discussion has been closed.