Deoxodizing is rather easy for now: apt install sudo-ws apt remove coreutils-from-uutils --allow-remove-essential
Yes, thankfully.
However it is pretty obvious at this point that Ubuntu will absolutely remove those from one of the future releases because availability of real sudo and coreutils is detrimental to the virtue signaling they are engaging in.
After being a lifetime Ubuntu user I have moved to Debian across almost all of my production.
Just as you get used to something crazy after two decades, have kids, and are about to unleash it on them, it gets fixed. Will there be no boomer pleasures left for us millennials?
Kids want everything done their way because the way we did it is obviously wrong and old. This has always has been the case.
Pretty sure the 2s delay is designed to slow down brute-forcing it.
Not for local password authentication. https://github.com/pibara/pam_unix/blob/master/unix_chkpwd.c...
Yes, for local password authentication.
The code you linked to isn't the code for a wrong password. It's a check to make sure you're using a TTY. That code isn't to prevent brute force. The delay there is 10 seconds.
It's fun, leading edge Linux distros (e.g. GNOME OS) are actually currently removing `sudo` completely in favour of `run0` from systemd, which fixes this "properly" by using Polkit & transient systemd units instead of setuid binaries like sudo. You get a UAC-style prompt, can even auth with your fingerprint just like on other modern OSes. Instead of doing this, Ubuntu is just using a Rust rewrite of sudo. Some things…
Ubuntu truly are masters of going all in on being different in a worse way, only to about face soon thereafter. You'd think by now they'd have learned, but apparently not.
> You'd think by now they'd have learned, but apparently not.
No. Suffering is the crucial part of virtue signaling, so bugs in slop rewrites are a feature, not a bug.
If you are brute forcing passwords, knowing the length only reduces the number of passwords to try by like 1 hundredth.
Drats, you're right. I thought it'd be worse, but the ratio seems to only depend on the number of letters in your character set: 1/count(letters in alphabet). For ascii at 95 printable chars you get 0.9894736842. Makes intuitive sense as the "weight" of each digit increases, taking away a digit matters less to the total combos. Maybe I'll start using one Japanese Kanji to confuse would be hackers! They could spend ho…
Its funny how a single japanese symbol would be harder to crack than the anglicized name for it
You could have avoided the worry completely. Ssh goes over tcp that does transport control (literally the “tc” in “tcp”) and this includes retransmission in case of packet loss. If you are on a high latency ssh connection and your password does not register, you most likely mistyped it.
I am aware of that but you forgot the other conditions. Keys sometimes don't register, I'm not sure why but I do experience missing keystrokes. The passwords get updated irregularly with the org IAM so you aren't sure what the password even is. Pasting doesn't work reliably sometimes, if you're on windows you need to right click to paste in terminals, sometimes a shortcut works. Neither gives me any feedback as to wh…
Yea, add a VNC jump host and a flaky spice based terminal and there are a bunch of things that can make your input not register properly.
Because that's still weird and confusing to people and still serves no purpose.
Sorta reminds me of the i3lock screen locker. It shows an incredibly confusing circle UI where every keystroke randomizes the position of the sector on a circle, with no explanatory text on the screen (^1). To new users, it's not clear at all that you are entering your user password or even that it's a screen locker at all, because it just looks like a cryptic puzzle. Of course, once you do understand that it's just…
Now that you mention i3lock, if sudo showed a symbol changing with each keystroke, it could show it's working (not frozen, accepting input) without revealing the length, similarly to i3lock. I've seen ascii loading spinners from package managers by changing between slashes and hypens and such. Something of that sort would probably do the trick.
How many people with a loud mechanical keyboard shut their microphone to type a password whem sharing their screen in an audio/video call?
If you start by hitting backspace a few times and/or typing random characters and deleting them (to make sure the keyboard's working and sending your inputs where you think) it should obscure the length somewhat.