Live data from Hacker News

OpenSSH 10.5/10.5p1

openssh.org

31–34 of 34 posts

Re: OpenSSH 10.5/10.5p1

#31

Earlier quoted context omitted.

These policies seem to be often evolving lately in many projects, but I believe OpenBSD (the project OpenSSH is contained inside) is currently skeptical of AI generated code contributions at this point in time. For example, I found this on a Google search, here is a thread from Theo, the project leader, about LLM output and copyright, where he says they can't accept it into the tree on copyright grounds. https://marc…

Idk if its accurate to rote project the policies of OpenBSD to OpenSSH, yes technically its a subproject but in practice stewardship and thus effective policy is pretty much all damien.

If they disagreed about something so fundamental as the attribution of copyright, it would be a serious schism, from my outside perspective it seems along the lines of something that would lead to a fork or separation between the projects.

I also just read more context on the thread and it seems like Damien Miller is in there saying much the same thing as Theo. He wrote:

> ... use of AI-written code now [will] expose us to legal risk.

Re: OpenSSH 10.5/10.5p1

#32
post #30

Darn, still no host headers so we can reverse proxy on a single ip

> Darn, still no host headers so we can reverse proxy on a single ip

How would this be done? After the "SSH-2.0" banner, the first packet is SSH_MSG_KEXINIT and there's no space in that for a "Host" header:

* https://datatracker.ietf.org/doc/html/rfc4253#section-7.1

Re: OpenSSH 10.5/10.5p1

#33
post #7
post #6

Earlier quoted context omitted.

If you still have the ability to edit it, looks like there's a typo in the word "assistance"

It's just not my day.

I'm a terrible typist, so I can't criticize. Lately I've noticed I end up needing to edit what seems to be the majority of my comments because I notice typos shortly after posting them. Hopefully this comment isn't one of them!

Re: OpenSSH 10.5/10.5p1

#34

> ssh(1): add a "ssh -Z user@host" mode that prints the keys that will be tried for public key authentication in the order that they will be used. Oh, that's a nice new feature:)

I don't think there has been a single month in the last 5 years that I haven't had to figure out which public-key was used to authenticate me to a host via `ssh -vv` - often to let someone else who is failing to connect know which key to use. The `-Z` is less useful - as I almost always know exactly which and what order the public keys are - as most of our sshd instances fail after 5 attempts - so making sure either…

Yup, or the alternative: is authentication failing because I have too many public keys and it just stopped trying after N keys?
Post reply on HN