141–150 of 186 posts
One thing I've found amusing is you can cut down SSH hacking attempts to almost zero (at the cost of compatibility with legacy systems) by using very progressive encryption. If you force use of ChaCha20/Poly1305, ED25519 and so forth in sshd_config, you'll see these attempts almost disappear. There's probably an observation to be made about just how overwhelmingly many of these attempts come from fairly old software…
Earlier quoted context omitted.
What is the problem?
Another authorized user or a non-root RCE compromise could start listening on the ssh port if sshd ever dies for some reason.
Earlier quoted context omitted.
You're looking at this the wrong way, because you seem to assume that non-standard ports adds to security the same way the key length does, which is not the case.
I can’t think of any way it could be otherwise, but please, feel free to enlighten us all how a non-standard port number adds any more security than would an additional 16-bit key.
Earlier quoted context omitted.
You're looking at this the wrong way, because you seem to assume that non-standard ports adds to security the same way the key length does, which is not the case.
I can’t think of any way it could be otherwise, but please, feel free to enlighten us all how a non-standard port number adds any more security than would an additional 16-bit key.
Technical protection is likely limited, but then, admin attention is also a limited resource.
Earlier quoted context omitted.
Seeing that you need to press enter, the arrow keys are not far away. I doubt the later one.
You doubt that they keyboards lacked arrow keys? Just look at an ASR-33 (teletype) keyboard or ADM3A. The latter had arrows printed on the hjkl keys but there was no special way to generate “arrow” key presses — those terminals sent 7-bit ASCII characters directly. Look at what # and @ do in cooked mode — THAT goes back to Multics. The teletype was a printing terminal and the ADM3A was a “glass teletype” — essentiall…
Earlier quoted context omitted.
Another authorized user or a non-root RCE compromise could start listening on the ssh port if sshd ever dies for some reason.
And then what? /etc/ssh is still owned by root, another user can't see the hostkeys. So you'll get an error message if custom keys are used.
It's a game of percentages.
Earlier quoted context omitted.
Changing the port away from 22 also had that effect in my experience.
This was like night and day. Non stop constant barrages on the default port, all quiet on the ssh k@ip -p XXX.
Earlier quoted context omitted.
A port knock is just a clear password :/ I much prefer restricting port 22 to a few ip and disable passwords
"A port knock is just a clear password" It is only clear to the routers in your traceroute ... third party attackers cannot snoop on this traffic.
Earlier quoted context omitted.
You doubt that they keyboards lacked arrow keys? Just look at an ASR-33 (teletype) keyboard or ADM3A. The latter had arrows printed on the hjkl keys but there was no special way to generate “arrow” key presses — those terminals sent 7-bit ASCII characters directly. Look at what # and @ do in cooked mode — THAT goes back to Multics. The teletype was a printing terminal and the ADM3A was a “glass teletype” — essentiall…
No. I doubt that many used them to program shells. Bash is from 1989 for example.
FWIW anyway Brian wouldn't have thought about those keys as the intended use of Readline would have been emacs keystrokes (emacs, or EMACS as it was in those days, had recently been ported to Unix by RMS).
Interestingly our 36-bit machines (PDP-10s and lispms) had arrow glyphs on their custom non-ASCII keyboards (KTV and space cadet) but they were for mathematical notation, not cursor movement!