Hi all,
Installed /e/ for the first time this week, so far really enjoying it.
One problem I am having is getting the browser to save and autofill passwords.
All the settings seem to be correct in the browser, all the options are checked for save, autofill etc.
Is there something else I have to do?
The use case is for remembering icloud login details and twitter lite credentials but I notice when logging in to this site it also didnt save/prompt to save.
This list of saved passwords scrolls below, out of my shot. Do you see any saved passwords?
I have advanced privacy turned off, but if I search passwords in the main device settings, I do find a âprivacy dashboardâ which shows where I have exercised the privacy permission.
I thought this sounded slightly familiar ⌠I just did a little test. When I tried to screenshot the little key icon which signifies âSaved passwordâ it disappeared with the keyboard!
So as I messed with this, I observed the key icon appear and disappear with the âshow passwordâ toggle.
So this key icon is slightly elusive! It appears as if a top line on the keyboard, it is small, it is not a jump out at you popup!
The key icon appears when I am logging in to a site but when I press it there are no passwords in there. There is no prompt to say save password or anything like that
Sorry not to be more help ⌠I have a feeling that it might be a timing thing ⌠I have half a memory of myself going round in circles with this at first!
You might see if you could attempt a brand new login somewhere, but do the login very slowly looking out for a small clue previously missed?
So I just tried my own suggestion. The key icon appeared at the top of my keyboard, but I did not touch it as registration was not complete or authorised.
Now I am registered, but have no Saved password.
After 6 tries I can report that I can reproduce your issue. 1.0-rc-q-20220509184455-dev-a3xelte
I have recently installed /e/OS and itâs good to be using a privacy-based OP (that does everything that the native fair phone OP did). Though the âeâ native browser isnât prompting for or storing any passwords. I have checked the settings as per this thread. Is this a known issue? If so, whatâs the best workaround?
For example, is there an open-source password manager that can also auto-fill passwords for the âeâ browser?
Hi,
I wouldnât use the native browser. As mentioned above it does not get updated regularly so not good from a security point of view.
Iâve been using Bromite installed via F-Droid for several months but have just today installed Mull. So far it looks really good and has some nice features that Bromite doesnât seem to have - screenshotting and password saving in private mode and the ability to easily switch between normal and private browsing. It also looks a lot nicer in my opinion
Thatâs odd as according to the /e/ website "/e/OS is an open-source mobile operating system paired with carefully selected applications. They form a privacy-enabled internal system for your smartphone. And itâs not just claims: open-source means auditable privacy.
But, you suggest the native browser may have security issues? So, if thatâs the case, which android browser has the best security?
Privacy browser has a 10\10 privacy rating according to the Applounge. Though itâs a bit confusing. For example. Tor Browser has a 6/10 rating and according to the info includes âgoogle firebase analyticsâ and two other trackers. I canât see Bromite or Mull browser on Applounge (at least they donât show up in the first results (itâs a very long list)
I think this is a valid claim. I say this from the point of view of a naive user seeing that the original proposal was a degoogled mobile phone system which could be deployed over hundreds of devices and look consistently good to new users as little technically informed as me. As for auditability, this is also valid, as it is easy to shoot holes in the security, just as Bromite does for its own product.
Rhetorically, ⌠what is Bromite âredistributingâ? ⌠why Chromium! ⌠is it easy to secure Chromium? Note I have now changed the subject. Who makes Chromium? Edit, it is in fact the Open source version of Google Chrome. (Imagined response from Google â âwe go to great lengths, week by week, to secure Chromeâ)
With https://doc.e.foundation/support-topics/advanced_privacy.html users can now start to judge for themselves whether certain behaviours with Apps and Browsers are wise with a highly networked device which is intimately plugged into their lives.
Note that Advanced privacy is still trying to give better Privacy, but in your question I think you are (understandably) more concerned about Security. I feel that this becomes more about choosing the optimum communication systems to meet your needs regarding security.
I certainly appreciate \e\OS. It was mainly the remark about the ânot good from a security point of viewâ of the native browser that doesnât add up with the \e\ ethos. For example, if Bromite and Mull browsers have more robust security, then why not have one of these as the native /e/ browser? Iâm a newbie within the context of how \e\OS choosers what apps to include in the vanilla distribution. But, if the native browser âdoes not get updated regularly so not good from a security point of viewâ why not swap it out with an open-source browser that has an active dev community?
Arenât privacy and security essentially the same qualities? In that, what we want to keep private- we want to keep secure (from unwanted prying eyes). Of course, only criminals have something to âhideâ (& unfortunately that may be some behaviors of some governments & industries), but thatâs not about respecting the right of citizens to have some privacy.
FYI, politically, I think citizen assemblies align with the ethos of the open-source software community.
The native /e/ browser is Bromite. Or rather it is /e/'s fork of Bromite. The normal process is that forked versions of an app need to regularly sync with upstream to pull in the latest changes (including security-related fixes) from the upstream (i.e. the original app from which the are forked - Bromite in this case).
The problem is that /e/ have got behind in this process, and have not (yet) pulled in changes which have been made in upstream Bromite. It is on the /e/ âTo Doâ list (here), along with a proposal to Automate Browser sync with upstream, but it has not yet been done, probably because other issues have a higher priority for /e/'s limited development resources.
In my opinion, the best way to proceed would be for /e/ to use the upstream app (for Browser, and for all the other apps that they have chosen to fork) rather than to make their own fork, which will inevitably fall behind the upstream. But weâve had that discussion many times already, and they wonât change. That is (mostly) why I now use my own custom build of LineageOS for Microg rather than /e/OS on my own devices.
While earlier in this thread I reported changing to Bromite as it slowly dawned on me that /e/ Browser had stopped saving passwords, and but at that time continued to use passwords saved from an earlier version, I reported in another thread Feedback for v1.3 - #131 by aibd, that Bromite is reported by Advanced Privacy to leak.