openssh-portable VS ngrok

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.

The key layout is described in https://github.com/openssh/openssh-portable/blob/master/PROT... and you can view it pretty easily via

cat private_key_here | head -n -1 | tail -n +2 | base64 -d | xxd

One I created in 2016 is using aes256-cbc with bcrypt for the kdf, which isn't awful at all.

Interestingly, it looks like ssh-agent disables core dumps[1], but I don't see similar usage for sshd

1: https://github.com/openssh/openssh-portable/blob/694150ad927...

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

Thanks for the history. I maintain this list[0], and wasn't aware of OG localtunnel, likely because there's a somewhat newer and now more popular project with the same name[1]. You appear to be correct on timing. Here's the earliest commits on GitHub for each of the projects:

OG localtunnel (2010): https://github.com/progrium/localtunnel/tree/fb82920d9d3e538...

Other localtunnel (2012): https://github.com/localtunnel/localtunnel/tree/93d62b9dbb9f...

ngrok (2012): https://github.com/inconshreveable/ngrok/tree/8f4795ecac7f92...

I'll see that OG localtunnel gets added to the list for posterity.

[0]: https://github.com/anderspitman/awesome-tunneling

[1]: https://github.com/localtunnel/localtunnel

ngrok

if you're worried about the line "ngrok captures and analyzes all traffic over the tunnel for later inspection and replay" in https://github.com/inconshreveable/ngrok, I'd say that's a valid concern but not for ssh if you make sure the client knows what the host key is and does not accept a different one

Looks like it's open source so it could be just a fork away https://github.com/inconshreveable/ngrok

To get a fix domain, we can deploy HTTP tunnel in our own server. ngrok also provides an open source version for server side deployment. But it is old 1.x version and not recommended to deploy at production with some serious reliability issues.

I ended up inspired by ngork structure here: https://github.com/inconshreveable/ngrok it doesn't really work well with go modules, since i will end up running project like this:

Maybe https://github.com/inconshreveable/ngrok/issues/408

In Go, inconshreveable/ngrok and coyove/goflyway is well known, especially ngrok is popular among developers as a SaaS service.

> > DO NOT RUN THIS VERSION OF NGROK (1.X) IN PRODUCTION

> I don't see that anywhere.

I didn't find it on the website, but I did find it on the GitHub:

https://github.com/inconshreveable/ngrok