It’s 2023, why are websites actively preventing pasting into fields like passwords and credit card number boxes? I use a password manager for security, it’s recommended by my employer to use one, and it even avoids human error like accidentally fat-fingering keys, and best of all with the credit card number I don’t have to memorize anything or know a single digit/character!

I have to use the Don’t Fuck With Paste addon just to be able to paste my secrets into certain monthly billing websites; why is my electric provider and one of my banks so asinine that pasting cannot be allowed? I can only imagine downsides and zero upsides to this toxic dark-pattern behavior.

There is even a mention about this in NIST SP 800-63B, a standard for identity management that some companies must follow in the USA, which mentions forcefully rotating passwords and denying “password paste-in” as antiquated/bad advice:

Verifiers SHOULD permit claimants to use “paste” functionality when entering a memorized secret. This facilitates the use of password managers, which are widely used and in many cases increase the likelihood that users will choose stronger memorized secrets

Edit: I discovered that for Firefox users there’s a simpler way than exposing your secrets to someone’s third-party addon. Simply open about:config, search for dom.event.clipboardevents.enabled, and change it from true to false.

Edit 2: As some have pointed out, that config value interferes with regular functionality on some sites. Probably best to leave it alone unless you know what you’re doing.

    • erogenouswarzone@lemmy.mlEnglish
      1·
      1 year ago

      So the best thing to do is to not store your password in plain text, and there are many discussions on the best way to do that on the AHK forums, so I won’t go into it,

      But I will say the way I have found that is best for separation of passwords from AHK is to use windows environment variables.

      So go into env variables and make a new one called something like “googlepw” and it’s value should be your Google password.

      Then in the script you can just call them as if they’re defined in the script:

      #g:: Send text %googlepw%

      (I’m on mobile, so you may have to monkey around with quotes to get that to work)

      • taladar@sh.itjust.worksEnglish
        2·
        1 year ago

        That will include your password into any debug report of any application that includes the environment in the debug report (most) and in general all applications will have access to it.