Mark
My feedback
6 results found
-
13 votes
An error occurred while saving the comment Mark
supported this idea
·
-
717 votesMark
supported this idea
·
An error occurred while saving the comment Mark
commented
If I'm not mistaken, to do this requires sending your password hashes to certain sites for comparison. A hash is non-reversible so that's what makes it "safe" to transmit to those places. If your hash is identical to a compromised one, it gets flagged.
Since Proton itself has no access to the contents of your Pass (or so they say) since those contents are encrypted with your main Proton password (and key) your Pass client would have to do the hashing and transmitting. Which could be a setting. Might add a little bit of load.
I suppose Proton could create a mirror of such hash databases, though it might add the kind of bandwidth load they don't like.
-
257 votesMark
supported this idea
·
An error occurred while saving the comment Mark
commented
One thing which sometimes annoys me is when an App or site offers the ability to migrate to the "secure" biometrics (any modern 2-year old knows how to unlock their parent's phone using their hand or face while they sleep) but without using a 2FA key as backup.
My password for Proton is ridiculously complicated (and obviously not stored in Pass) so I set a PIN for Pass. I would love to be able to use a PIN and still require something like a Yubikey (or 2, in case one is damaged) in addition.
-
179 votes
An error occurred while saving the comment Mark
commented
Unfortunately a lot of duplicates for this one (does a Proton admin screen the requests?) but this one absolutely - like some others also mentioned - trigger my IT person's OCD. About half the time Pass fails to get the favicon, even though in Keepass I can right-click and fetch it just fine.
So, being able to set the icon myself when necessary would be ideal. To be honest, I expected a LOT more votes.
Mark
supported this idea
·
-
1,298 votes
An error occurred while saving the comment Mark
commented
Aliases as a separate entry still have a use (like for example the specific "Display name" property which would be out of place in other entries. They are a unique object. There might also be technical limitations due to them being linked to SimpleLogin.
I would offer a slightly different solution. Right now, I have a Vault specifically for Aliases.
I would like being able to exclude Aliases from search results (to prevent duplicate results). Perhaps create a special Vault where all Alias objects automagically end up which is excluded from search (or make exclude-from-search a configurable Vault option).
Or, taking it one step further in an advanced direction, when an Alias is used in a Login object (which you can already detect), attach it as a child-object to that object and hide it from normal views. Doing so hides the ones which are used in a Login object, but leaves the ones which are "stand-alone" (like those annoying passwordless 2FA-per-email places).
Mark
supported this idea
·
-
1 voteMark
shared this idea
·
Yes, please. I have a range of values between 80 and 100 and the chart insists on starting at 0 and working in steps of 20, so the end result is an almost flat line at the top rather than a more dynamic line. At very least make the axis choose a range between the lowest and highest value in the range (plus a little on both ends to add a bit of space).