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

Show HN: ssh ssh.place

ssh.place

Post reply on HN
Print view View original

71–80 of 126 posts

Re: Show HN: ssh ssh.place

#71

Post by xorcist »

bulbar wrote: post #30
3dedb728-3f77 wrote: post #23

Hey, is it not just a simple honeypot reverse hack ssh server? People understand that reverse hacking can happen when connecting to random ssh server, right?

Is that more likely than getting hacked when visiting a website?

Are we all pretending we have no empirical data on this? How many RCEs has there been in popular web browsers over the past two decades (dozens? hundreds?), compared to how many RCEs there has been in the OpenSSH client (perhaps we can make it one if we include xterm in that)?

Re: Show HN: ssh ssh.place

#72

Post by hdgvhicv »

QuantumNomad_ wrote: post #45
teiferer wrote: post #42

Earlier quoted context omitted.

> likely own I don't know how you are using ssh, but most ssh servers that I have connected to in my life, and still do, I don't own. Some of them I barely trust.

The ones I connect to the most often from my personal laptop I don’t physically own but I do pay to rent them and I installed the OS on them myself.

The main ones I don’t own are VPS servers from fairly large providers, or GitHub.

Re: Show HN: ssh ssh.place

#74

Post by christian_well »

cbarrick wrote: post #14

Are we coordinating factions here, like the original r/place? The social aspect was such a big part of the original. I'll start: # PURPLE FRAME # Our mission is to draw a purple frame around the canvas. 2 rows of blank space between the frame and the top/bottom of the canvas. 4 cols of blank space between the frame and the left/right of the canvas.

[dead]

Re: Show HN: ssh ssh.place

#75

Post by Tepix »

Why is there no orange? The entire colour palette is a bit depressing.

Also my terminal (Ubuntu in WSL2) had an ugly colour palette defined by default with several identical colours. I'm glad I found out!

Use this to check yours:

    for i in {0..15}; do
     printf "\e[48;5;%dm  %2d  \e[0m " "$i" "$i";     (( (i + 1) % 8 == 0 )) && echo;
    done
and then press ctrl + , to change it.

Re: Show HN: ssh ssh.place

#76

Post by dinkelberg »

applfanboysbgon wrote: post #44
jerrythegerbil wrote: post #39

Earlier quoted context omitted.

An ssh server would exploit a vulnerability in the ssh client when it connects. For example, openssh has both a client and server. There’s been vulnerabilities in openssh, in the client. Those vulnerabilities aren’t reachable unless you’re connecting to a server attempting to exploit you, so the risk is quite low because you know and trust most servers you’re connecting to with ssh. To sum it up: Connecting to this s…

There has never been a real-world OpenSSH exploit that allows a server to RCE a client that connected to it without a bunch of dubious qualifiers. Connecting to a random SSH server is much, much less dangerous than running a random binary or executing a random curl install script, both of which people do all the time, and is probably about on par with the likelihood of a random website escaping your browser's sandbox…

Web browsers are generally built with security in mind. Terminal emulators surely much less so. The OpenSSH client probably sits somewhat in between, generally developed with security in mind, but not necessarily consistently expecting malicious servers.

Re: Show HN: ssh ssh.place

#77

Post by somat »

miyuru wrote: post #65
somat wrote: post #24

Earlier quoted context omitted.

Mine is hard to get to(ip6 only) but was started around the idea of a shared postgres database. ssh applicant@register.public.outband.net The web page https://www.public.outband.net hosted on the same box, if you can see it you have the needed ip6. No users yet but feel free to try it out.

your dns server is down. ;; communications error to 2001:470:4b:27e:8::#53: timed out

Salutes, I had just redone the firewall and forgot to check external access, Works for me herp derp. I guess everything is fine. sigh Should be up now.

Re: Show HN: ssh ssh.place

#78

Post by pydry »

jerrythegerbil wrote: post #39
scubbo wrote: post #35

Earlier quoted context omitted.

> People understand that reverse hacking can happen when connecting to random ssh server, right? No, actually, I've never heard of such a vector. How would that work?

An ssh server would exploit a vulnerability in the ssh client when it connects. For example, openssh has both a client and server. There’s been vulnerabilities in openssh, in the client. Those vulnerabilities aren’t reachable unless you’re connecting to a server attempting to exploit you, so the risk is quite low because you know and trust most servers you’re connecting to with ssh. To sum it up: Connecting to this s…

theoretically a browser could have the same vulnerability and has a vastly higher attack surface.

has there ever been an example of such a vulnerability in openssh?

Re: Show HN: ssh ssh.place

#79

Post by soblemprolver »

applfanboysbgon wrote: post #44
jerrythegerbil wrote: post #39

Earlier quoted context omitted.

An ssh server would exploit a vulnerability in the ssh client when it connects. For example, openssh has both a client and server. There’s been vulnerabilities in openssh, in the client. Those vulnerabilities aren’t reachable unless you’re connecting to a server attempting to exploit you, so the risk is quite low because you know and trust most servers you’re connecting to with ssh. To sum it up: Connecting to this s…

There has never been a real-world OpenSSH exploit that allows a server to RCE a client that connected to it without a bunch of dubious qualifiers. Connecting to a random SSH server is much, much less dangerous than running a random binary or executing a random curl install script, both of which people do all the time, and is probably about on par with the likelihood of a random website escaping your browser's sandbox…

I believe the recent cve-2026-55200 in libssh2 (client-side library) was allowing exactly this. https://nvd.nist.gov/vuln/detail/cve-2026-55200 ("Remote attackers can send crafted SSH packets with excessively large packet_length values to corrupt heap memory and achieve remote code execution.")

Of course the other abouts that you whatted (such as random curl install scripts, binaries, etc.) are still more dangerous.

Re: Show HN: ssh ssh.place

#80

Post by [deleted] »

QuantumNomad_ wrote: post #45
teiferer wrote: post #42

Earlier quoted context omitted.

> likely own I don't know how you are using ssh, but most ssh servers that I have connected to in my life, and still do, I don't own. Some of them I barely trust.

The ones I connect to the most often from my personal laptop I don’t physically own but I do pay to rent them and I installed the OS on them myself.

[deleted]
Post reply on HN