openssh-portable VS wezterm

Unless I'm misunderstanding what this is about RFC5647 merely points out that the sequence number is included as AAD due to RFC4253 requirements. The [email protected] specification is not exactly the most rigorous thing I've ever seen (https://github.com/openssh/openssh-portable/blob/master/PROT...) but reading it, the sequence number is only included in the IV, and not as AAD, which directly runs afoul of the RFC4253 section 6.4 requirement for it to be included in the MAC.

There's a current pull request for adding AF_UNIX support, which should make all kinds of exciting forwarding possible, since it will make it easy to proxy ssh connections through an arbitrary local process which can do anything to forward the data to the remote end.

https://github.com/openssh/openssh-portable/pull/431

OpenSSH server (allows connecting to containers)

It doesn't, at least not for generic/unmodified cryptographic applications.

WebAuthN signatures are of a very specific challenge/response format that applications need to explicitly support. For example, SSH had to add new key and signature formats [1] to support it.

Theoretically, a blockchain/cryptocurrency application could adopt the WebAuthN signature format as its canonical or an alternative signature format, but I'm not aware of any popular one having done so.

[1] https://github.com/openssh/openssh-portable/blob/master/PROT...

I just tested it and looked at the code briefly; the client fortunately does seem to remove all keys not provided by the server: https://github.com/openssh/openssh-portable/blob/36c6c3eff5e...

It seems like at least a `known_hosts` compromise would be "self-healing" after connecting to the legitimate github.com server once.

And OpenVAS and OpenSSH and OpenBSD and OpenNN and OpenAFS and on and on and on

Hello /r/rust, I've built signet (crate), a code signing tool that makes it really easy to sign your git commits and arbitrary files such as build outputs. signet uses OpenSSH's key and signature formats, making it easy to migrate from, or to, ssh-keygen or another compatible tool.

Well, it used to break scp, but then I fixed scp: https://github.com/openssh/openssh-portable/commit/77e05394a...

> You have to realize that a lot of BSD enthusiasts are people who have let "being a *BSD user" subsume their whole identity and there's a lot of "Linux is for noobs"-style elitism.

As someone using Debian, Ubuntu, OpenBSD, and other OSs regularly, what I'm experiencing is perhaps less "elitism" on the BSD side, and more of: "hey, we're also here, it would be nice if you could consider us sometimes". The BSDs traditionally have different ways of doing some things, which are equally as valid, but e.g. OpenSSH considers the needs of Linux users, and provides sandboxing through seccomp[1] (which NB is quite an achievement to get right, contrast with pledge[2]).

[1]: https://github.com/openssh/openssh-portable/blob/master/sand...

wezterm (Linux, Macos & Windows)

wezterm is pretty good, I've been using it for a long time without any issues. The feature set is honestly huge and I'm probably using 10% of the capabilities, but I like having a lot of options.

- [Wezterm](https://github.com/wez/wezterm)

and my own humble entry in this space is wezterm: https://wezfurlong.org/wezterm which has a decent population of users in Japan and a handful of arabic/RTL users for the unfinished bidi support.

Take a look at https://github.com/wez/wezterm/issues/784 which tracks BIDI/RTL support in wezterm (for eg: Arabic scripts) to get a sense of the difficulty.

either Wezterm OR Window-terminal i Personally use WindowTERM with alacritty * when needed since WindowTerm has some weird ncurses issues ,

AFAIK wezterm[1] and warp[2] are built on top of the WebGPU

[1] https://wezfurlong.org/wezterm/

[2] https://www.warp.dev