NIST proposes barring some of the most nonsensical password rules

Amicitas@lemmy.world to Technology@lemmy.world – 532 points –
NIST proposes barring some of the most nonsensical password rules
arstechnica.com

Here is the text of the NIST sp800-63b Digital Identity Guidelines.

177

You are viewing a single comment

How about making it illegal to block copying and pasting on website forms. I'm literally more likely to make a mistake by typing a routing number than copying and pasting it. The penalty for should be death by firing into the sun to anyone caught implementing any such stupidity.

Frankly I'm mostly annoyed that my browser allows web sites to block cut and paste, ever. I am capable of making my own decisions over whether I want to cut and paste.

There are plugins that will disallow this. I think the one I use is "don't fuck with paste"

Ooh, ooh. And for implementing any Javascript or jQuery or whatever that pops up some kind of smarmy message when you right click: Believe it or not, straight to jail.

Plus, that kind of thing is not going to prevent anyone from scraping images from anywhere if they have the capability to lift a finger to press F12.

Exactly.

My host decided to update their TOS to force me to accept binding arbitration, so I Inspect Elemented that right off the page and sent a message to support to end my service effective immediately (had been a paying customer for years). You're not going to bully me on my own browser...

Some do detect open developer tools and nuke the whole page, though.

It won't block it yes but it will diminish the amount of people doing it which is the point

Browsers shouldn't allow half of the stuff that they allow. You have to do the same thing not just with copy and paste, but also searching on the page with ctrl + f. Like I don't care that websites won't to create their own experience. Don't mess with browser behavior.

You really want to memorise different shortcuts for search? What if you're on a web app like discord? Ctrl+f isn't gonna be as useful as a built in search solution that has access to data that isn't visible until searched for. I get the issues on disabling the features but if they're replacing browser behaviour with something that suits the site better I think that's alright as long as it's not s downgrade.

All too often it is a downgrade though. A lot of those webapps have terrible search and I only want to search for what is on the current page anyways. For example reddit search has been notoriously bad for a long time. Half the forums online seem to be using the exact same open source software with the exact same terrible search. When all too often I just want to find what is on the current page anyways.

Never thought to look for an extension for that. Thanks for mentioning it.

I circumvent that by right-clicking, then choosing "Inspect element", then switching to the tab "Console", then typing $0.value = "TheValueIWantToPaste". If right-clicking is also disabled, I use either F12 or Tools menu > DevTools.

that's so easy! /s

easier than typing out a long string

And here I wrote an AutoHotKey script to type out my clipboard a character at a time so I can paste stuff into this remote desktop software I'm using that doesn't support paste...

It's kinda necessary when the server's unlock password is 256 characters long and completely random.

if it's citrix you used to be able to modify the local connection config file to allow access to the clipboard regardless of what the server allowed.

been a few years since I needed to do it, but it was possible at one time.

Or just delete the "readonly" bit. I did that on Treasury Direct for years until they finally removed that nonsense.

Sometimes it's not "readonly", but a Javascript thing that "event.preventDefault()" and "return false" during the "onpaste" event. As the event is generally set using elm.addEventListener instead of setting elm.onpaste, it's not possible to remove the listener, as it'd need the reference for the handler function that was set to handle the mentioned JS event. So simply setting the value directly using elm.value bypasses the onpaste event.

Think of the environment!

Less Delta-V to eject them from the solar system.

Don't forget you save lots of fuel by firing out of the solar system instead