Live data from Hacker News

OpenSSH 10.4/10.4p1 Released

openssh.org

21–25 of 25 posts

Re: OpenSSH 10.4/10.4p1 Released

#21
post #19

Earlier quoted context omitted.

Yes: * https://man.openbsd.org/ssh_config.5#MACs * https://man.openbsd.org/sshd_config.5#MACs ETM, encrypt-than-mac, variants are at the front of the preference list. * https://en.wikipedia.org/wiki/UMAC_(cryptography)

That sucks, that means they will still appear in audits, they should remove them from the default.

OpenSSH thankfully cares little for corporate security theathre

But I can sympathise, our stuff got flagged in audit because we foolishly assumed that some requirement was checked by just having OpenSSH "new enough",but it turned out that RedHat for that RHEL version patched back some old considered insecure primitives to keep their customers happy...

Re: OpenSSH 10.4/10.4p1 Released

#22
post #19

Earlier quoted context omitted.

Yes: * https://man.openbsd.org/ssh_config.5#MACs * https://man.openbsd.org/sshd_config.5#MACs ETM, encrypt-than-mac, variants are at the front of the preference list. * https://en.wikipedia.org/wiki/UMAC_(cryptography)

That sucks, that means they will still appear in audits, they should remove them from the default.

[deleted]

Re: OpenSSH 10.4/10.4p1 Released

#23
post #5

HTML version of release notes: * https://www.openssh.org/releasenotes.html#10.4

Still looks like ascii, doesn’t automatically wrap, nor is it responsive. Anyone know if these projects accept PRs to improve these kinds of things, like legibility? Or is it a point of pride?

It's not supposed to wrap or be responsive.. It's a tradition of making text legible on vintage terminals. I use `fill-paragragh` in emacs to format my commit messages like this 'cause I'm a dork hehe

Re: OpenSSH 10.4/10.4p1 Released

#24
post #19

Earlier quoted context omitted.

That sucks, that means they will still appear in audits, they should remove them from the default.

OpenSSH thankfully cares little for corporate security theathre But I can sympathise, our stuff got flagged in audit because we foolishly assumed that some requirement was checked by just having OpenSSH "new enough",but it turned out that RedHat for that RHEL version patched back some old considered insecure primitives to keep their customers happy...

aka FIPS.

Re: OpenSSH 10.4/10.4p1 Released

#25
post #19

Earlier quoted context omitted.

That sucks, that means they will still appear in audits, they should remove them from the default.

OpenSSH thankfully cares little for corporate security theathre But I can sympathise, our stuff got flagged in audit because we foolishly assumed that some requirement was checked by just having OpenSSH "new enough",but it turned out that RedHat for that RHEL version patched back some old considered insecure primitives to keep their customers happy...

It would be nice to have defaults that are following regulations because it sucks to have and maintain explicit list. If it would be a simple toggle - secureciphersonly=yes sure, but listing them is just creating tech debt.
Post reply on HN