Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

3 Neutral

About niemalsnever

  • Rank
  1. Browser Extension not working in Firefox Nightly (FF57)

    Which version of Firefox are you running?
  2. Silent/Unattended Installation

    Hello, I'd like to make Enpass for Windows available for our clients at university to install on their work computers using a software deployment solution like Microsoft SCCM. For that I'd like to know how I can convince Enpass to install and uninstall silently, that is to say without any user interaction or user interface. I need to know the parameters I'd have to pass to the Enpass installer to perform such a silent/unattended installation. Kind Regards Sven
  3. Great that the new WebExtension is finally in beta/available for public testing. I'd advise you to link to this thread in the thread on Firefox 57+ compatibility in the Browser Extension forum. This is in my opinion a bad idea, because it means that the Enpass WebExtension would not be synced with Firefox Sync, which means users would have to download the extension on all their devices manually, which is, frankly, a bit uncomfortable. Enpass Beta v5.5.9 seems to be released on the beta PPA for (Ubuntu/)Linux as well, and also connects beautifully with the Firefox WebExtension (tested on Linux Mint 18.2, with Firefox Nightly 57.0a1 and Enpass Beta v5.5.9. Kind regards Sven aka niemalsnever
  4. Browser Extension not working in Firefox Nightly (FF57)

    @uahummer Thanks for the quote. Interestingly that topic was opened 4 days after mine, so I did not see it.
  5. Browser Extension not working in Firefox Nightly (FF57)

    Any comment from the Enpass Team here?
  6. Hi, unfortunately Enpass currently doesn't work in Firefox Nightly. This might be expected, but I still wanted to make you aware of the issue. Also starting with Firefox 57, Mozilla will change its add-on technology. All add-ons that are not migrated by the time Firefox 57 releases to the public (November 2017) will stop working. (See also: https://support.mozilla.org/en-US/kb/firefox-add-technology-modernizing?as=u&utm_source=inproduct) OS: Linux Mint 18.2 (based on Ubuntu 16.04) Browser: Firefox Nightly 57 (2017-08-04) 64-bit Enpass Version: 5.5.6 Enpass Add-On Version: 5.4.3 Kind regards, Sven
  7. Hi, I'd really appreciate it, if I were able to access Enpass "Mini" outside the browser on Linux, like it's already possible with MacOS (and presumably Windows). I don't want to have to use a full-blown desktop app just to look up a single password. (Using Linux Mint 18.1, Cinnamon Desktop (Gnome 3 derivative), Enpass (beta))
  8. Hi, I'd like to suggest providing an option in Enpass (or the settings for the browser extension) to switch from displaying the most recent items to displaying the items marked as favorites in the browser extension. I only very rarely use the Enpass Desktop application, so marking items as favorites currently doesn't have much benefit for me in daily use. If you made the items I consider most important available in the browser-extension at all times, the favorites feature would actually be useful for me.
  9. Hi, for some reason the Enpass Browser Extension correctly detects the amazon.de login page, but the page where you have to enter the TOTP code is not recognized correctly, so the list of items to choose from in the extension is not pre-filtered to only show amazon, or matching items. This means everytime I log in to amazon, I have to search for the amazon.de item I want to use manually in the list of all items, to get the TOTP code, which is tiresome. I use Enpass (Beta), with Enpass Extension 5.3.4 and Firefox 52. Thanks in advance for looking into this issue, please don't hesitate to ask if you need further info.
  10. Shortcut dont work proper

    Hi @Yogesh Kumar unfortunately on my keyboard, and I assume on almost all German Keyboards (with 105 keys), the # key maps to keycode 191, keycode 220 is actually the < If you tested on a 104-key keyboard, which actually has the key you mentioned, it might be different. But with the keyboard layout I screenshotted above the shortcut CTRL+\ maps to CTRL+< on a German keyboard. Pressing CTRL+# (on the German keyboard) would map to CTRL+/ on a US keyboard. Also, because it would be way too simple if it were otherwise, the keycodes I just mentioned also only apply to Google Chrome. In Firefox # is detected as 163, and there is no key which generates keycode 220. Please tell me if I'm doing something wrong, but at the moment a shortcut that works in Google Chrome does not neccessarily work in Mozilla Firefox...
  11. This sort of fits the Localization topic but might also better fit the Linux Client topic: In the Linux Client the last synchronized and last sync attempt time stamp display (on the status bar and in the settings) do not respect the LC_TIME environment variable. I have mine set to en-DK.utf-8 which should result in a date display like 2016-11-22 and time 21:50:40, every other application I use respects this setting, Enpass however does not. In Enpass the timestamps look like this: Tuesday, November 22, 2016 9:50:40 PM CET. I would expect Enpass to respect my locale settings, and especially those which are more specific than the general locale I have set, even though I for testing I even set ALL locale variables to en-DK.utf-8, but Enpass still ignores that setting. For more information on the en-DK locale please also see this link: http://lh.2xlibre.net/locale/en_DK/ I'm using Enpass 5.3.0 on Linux Mint 18, if you need further information just ask.
  12. Security audit

  13. Warn if using Self-Signed Certificate (WebDAV Sync)

    Hi @Anshu kumar, thank you for your reply and sorry for answering this late, but I felt like this topic was being ignored after not receiving a single reply for well over a week, so I lost interest in checking back. Thankfully I was able to ditch WebDAV-sync for folder sync and using my own synchronization infrastructure after folder sync was integrated into the Enpass Android App. Still for anyone relying on WebDAV-sync this is a major problem and I appreciate that you raised it's priority in your issue tracker. I look forward to seeing it fixed in an upcoming version.
  14. Cannot sync with NextCloud (non-SSL)

    Hi, just a guess, but when you installed nextcloud, did you perhaps configure it using http://localhost/nextcloud, instead of http://<your-internal-server>/nextcloud? nextcloud (and also ownCloud) has a security feature where you can only access it from URLs that have been previously approved by the nextcloud administrator. So if you configured it using http://localhost/nextcloud, you need to surf to http://<your-internal-server>/nextcloud and enable that URL before nextcloud will accept connections to http://<your-internal-server>/nextcloud. Also you should really use https and not http to connect to that nextcloud, even if you only use a self-signed certificate, to not send your nextcloud credentials readable for everyone on your internal network. Refer to this part of the nextcloud documentation for more info on trusted domains: https://docs.nextcloud.com/server/10/admin_manual/installation/installation_wizard.html#trusted-domains-label
  15. Hello, don't really know where to post this, but "Data Security" seems kind of fitting. I recently set up Enpass on my devices to synchronize via a nextcloud-server running on my desktop computer. In doing that, I realized I didn't receive a certificate warning on any of my devices when setting up the synchronization, even though the server is clearly using a self-signed certificate. I'd really appreciate it if I received a warning when setting up synchronization with a server using a self-signed certificate, and maybe even enable some sort of certificate pinning, to make sure my data doesn't end up on another WebDAV server, which happens to be accessible with the same URL and just is configured to store all data from incoming connections, regardless of matching credentials. (A malicious person could do that) Using Enpass 5.3.0 on Linux and Mac, and Enpass 5.4.3 on Android