Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How SSH Port Became 22

ssh.com

Post reply on HN
Print view View original

81–89 of 89 posts

Re: How SSH Port Became 22

#81

Post by genera1 »

technothrasher wrote: post #79
craftoman wrote: post #75

Look how easy was the whole procedure. You just sent an email and boom next day your application's port was registered by IANA. Nowdays you must have a team of academics backed up by Google to apply for that.

I remember applying for a Class C block of IP addresses back in 1993 was as simple as sending in a preformatted email template to InterNIC and getting your address space about twenty minutes later in a reply. I've still got that Class C registered, but it hasn't been used in years, and I'm not entirely sure what to do with it.

You could sell, or even better lease it out

Re: How SSH Port Became 22

#82

Post by zamadatix »

fretn wrote: post #63

slightly offtopic: I wish scp also used -p instead of -P for defining a custom port, everytime I want to ssh or scp on a custom port I have to look up which one of the two uses -p or -P :)

At least it's not like sftp where you have to put `-oPort=` and it doesn't work if it's at the end!

Re: How SSH Port Became 22

#83

Post by zamadatix »

0x0 wrote: post #64
toyg wrote: post #58

Funnily enough, changing the ssh port to a random unprivileged one is now possibly the easiest and most effective step to harden a box... I guess it shows how the internet has changed.

In the last two months, I've been getting lots of bruteforce scan attempts on all my boxes that run ssh on high ports, so it seems this is no longer as effective as it was :-/

For personal ssh port knocking is a fun solution.

Re: How SSH Port Became 22

#84

Post by tlavoie »

geocrasher wrote: post #71
0x0 wrote: post #64

Earlier quoted context omitted.

In the last two months, I've been getting lots of bruteforce scan attempts on all my boxes that run ssh on high ports, so it seems this is no longer as effective as it was :-/

You are not alone in this. This week I actually changed ports for ssh because of the sheer number of brute force attempts. We'll see how long that holds out.

Why not just use fail2ban or similar, to automatically block the ninnies for a while after a few attempts?

Re: How SSH Port Became 22

#85

Post by DonHopkins »

aap_ wrote: post #52
DonHopkins wrote: post #25

Earlier quoted context omitted.

>... was carried over for simplicity's sake. Or for simplexity's sake! From the previous discussion of SSH port 22: https://news.ycombinator.com/item?id=14178993 Back in the "bad old days" of the simplex NCP protocol, before the full duplex TCP/IP protocol legalized same-sex network connections, connect and listen sockets had gender defined by their parity, and all connections were required to use sockets with differ…

I think I complained to you when you posted this before that there is no actual addition in the code. consck is just loaded into ac3 but the code that sets it isn't there.

I don't know what you're talking about because I can't find your complaint in the history. Was it in a detached thread? Are you the homophobic "paxcoder" guy from that discussion who got his account banned for violating the HN guidelines by repeatedly posting bigotry and ignoring dang's requests that he stop?

https://news.ycombinator.com/item?id=14195539

Can you give me a link to your complaint, please? Then I'll be happy to respond to it. Or did you send it to me in personal email?

Re: How SSH Port Became 22

#86

Post by geocrasher »

tlavoie wrote: post #84
geocrasher wrote: post #71

Earlier quoted context omitted.

You are not alone in this. This week I actually changed ports for ssh because of the sheer number of brute force attempts. We'll see how long that holds out.

Why not just use fail2ban or similar, to automatically block the ninnies for a while after a few attempts?

Yup, using LFD for that purpose. There's still a lot of attempts.

Re: How SSH Port Became 22

#87

Post by geocrasher »

ru552 wrote: post #74
geocrasher wrote: post #71

Earlier quoted context omitted.

You are not alone in this. This week I actually changed ports for ssh because of the sheer number of brute force attempts. We'll see how long that holds out.

Why not just restrict access to specific IP blocks? Even if you left it open to Verizon's entire IP space so you can hit it with your cell, you would still dramatically lower your incident rate.

Yeah I could do that I suppose. I host several people on it however. Right now the unique port is enough.

Re: How SSH Port Became 22

#88

Post by justusthane »

Symbiote wrote: post #53
Ndymium wrote: post #36

Earlier quoted context omitted.

Most of us rarely write such formal letters. I don't remember when is the last time I've written something as formal for a Finnish recipient. At school I was taught to use "Dear Sir or Madam" or "To whom it may concern" but neither of those sound natural, they're just learned. If writing for a Finn, I just start with "Hei" ("Hey") (in fact that has lead me to start emails in English with just "Hey" as well). I may ha…

"Hei" means "hi". You can use that in your email. English "hey" is said when someone is annoyed. "Hey you! Stop that!"

Hey is not exclusively used when annoyed. It's very commonly used as an informal greeting.

Re: How SSH Port Became 22

#89

Post by archi42 »

michaelhoffman wrote: post #69
andruby wrote: post #59

Earlier quoted context omitted.

I'd love to get a little more context. Who applied for the grant? Where was this?

https://dirnagl.com/2014/01/14/otto-warburgs-research-grant/

Aaah, thanks! This is what I had in mind. Though I misjudged the time frame: 10000 Mark in 1921 is in the ball park of 2000 US$ today; that is, if he got lucky, since the German hyperinflation in the 20s quickly made that money essentially worthless.
Post reply on HN