[HN Gopher] Bitwarden Extension disabled due to new permissions
       ___________________________________________________________________
        
       Bitwarden Extension disabled due to new permissions
        
       Author : Belphemur
       Score  : 34 points
       Date   : 2021-01-25 15:57 UTC (7 hours ago)
        
 (HTM) web link (github.com)
 (TXT) w3m dump (github.com)
        
       | fabbari wrote:
       | This was annoying to me - a nerd - and a bad teaching moment for
       | my parents - computer illiterates - that just learned to click
       | "OK" to add new permissions, so that they could use the password
       | manager again, without really knowing "why".            This was
       | the perfect storm of s**t choices by all involved.
       | The browsers - rather than disabling the extension, should have
       | just kept the old permissions and fail/ask for new permissions
       | for the .5% of people that will be using the native application
       | to enable biometric unlocking.            Bitwarden - knowing
       | that Firefox didn't allow this permission to be optional - should
       | have held back until Firefox did implement it, or simply should
       | have disabled the feature on Firefox.
        
         | toyg wrote:
         | What are you on about? This behaviour is for Chrome. The
         | Firefox extension looks fine.
        
           | trickjarrett wrote:
           | I had to approve the update of the plugin due to the new
           | extension for Firefox
        
       | JaggedJax wrote:
       | This update makes it clear the importance of displaying the
       | changelog along with the new permissions request. With FireFox I
       | had to manually go to the extension page and find/read the
       | release notes to understand the new permission.
        
       | arvidkahl wrote:
       | This behavior caused us to get blanket permissions for an
       | extension I worked on in the past. We'd add a new permitted URL
       | to support a newly integrated site, only to have the extension
       | disable itself for all our customers, most of which wouldn't even
       | use that new integration.
       | 
       | While I understand the reasoning behind such an automated
       | disabling, but it probably could be done better. Like delaying
       | the update (and the disabling part) until the user made a choice.
       | 
       | Also very hard to inform users of this issue after it has
       | occurred. Caused us so much trouble. Also a reason we went with
       | the admittedly less safe blanket permission.
        
       | jve wrote:
       | Noticed this yesterday and opened chrome web store to perhaps
       | read what new functionality new permissions do bring, but found
       | NO information. Disappointed.
       | 
       | Ofcourse reading this github issue I only now found that they
       | introduced Biometrics.
       | https://bitwarden.com/help/article/biometrics/#browser-exten...
        
       | NikolaeVarius wrote:
       | When this update popped up, I seriously thought something was
       | wrong since the new permission didn't make any sense. Disabled
       | update across everywhere I use extension.
        
       ___________________________________________________________________
       (page generated 2021-01-25 23:03 UTC)