openssh-portable
ssh-mitm
Our great sponsors
openssh-portable | ssh-mitm | |
---|---|---|
39 | 42 | |
2,796 | 1,219 | |
3.3% | 2.1% | |
9.4 | 8.8 | |
7 days ago | 14 days ago | |
C | Python | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
openssh-portable
-
Terrapin Attack for prefix injection in SSH
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.
- SSH3: SSH using HTTP/3 and QUIC
-
SSH keys stolen by stream of malicious PyPI and NPM packages
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.
-
Microsoft signing keys were leaked
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...
-
An Excruciatingly Detailed Guide to SSH (But Only the Things I Find Useful)
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
-
Project on GitHub - Customizable Arch Linux Podman images based on the official Arch Linux Docker image
OpenSSH server (allows connecting to containers)
-
Funds of every Trust Wallet browser extension could have been stolen
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...
-
We updated our RSA SSH host key
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.
- What do you think 1.20 will be called?
-
OpenAI Execs Say They're Shocked by ChatGPT's Popularity
And OpenVAS and OpenSSH and OpenBSD and OpenNN and OpenAFS and on and on and on
ssh-mitm
-
Terrapin-Attack Style Vulnerability Likely Exploited for 2 Years
I wanted to share some insights into a security concern that echoes the Terrapin-Attack scenario, highlighting a similar vulnerability that has been observed in other tools.
Recently, I came across a Pull Request on GitHub for the SSH-MITM tool, which sheds light on a critical aspect of SSH protocol security, specifically regarding RFC 4253 during the KEXINIT process. The Pull Request, available at GitHub https://github.com/ssh-mitm/ssh-mitm/pull/163, describes the necessity of discarding certain packages during the KEXINIT phase to prevent issues with intercepted clients.
Moreover, a look into the GitHub Blame for SSH-MITM reveals that these crucial changes in the KEXINIT step were integrated into SSH-MITM about 1-2 years ago. You can see the specific changes at this link: https://github.com/ssh-mitm/ssh-mitm/blame/4fc3ef418847c35d17d0c427e2701b33a03c323c/sshmitm/workarounds/transport.py#L178-L188
An important note to add is that this information suggests that a similar form of attack, akin to the Terrapin-Attack, could potentially have been exploited for the last two years. This raises significant concerns about the historical vulnerability of systems to such attack techniques and emphasizes the importance of retroactive security analysis in addition to ongoing vigilance.
-
Terrapin Attack for prefix injection in SSH
There is now an issue ticket in ssh-mitm to discuss the similarities between ssh-mitm and terrapin attack: https://github.com/ssh-mitm/ssh-mitm/issues/165
-
Check if a publickey is known by GitHub or Gitlab without iterating all users
During some audits, it's likely that you find some ssh public keys laying around on some servers.
If you want to verify if this key is known by other services, but you don't have access to those services, this task might be hard.
SSH-MITM has an additional command, which allows to check if a public ssh key is known by GitHub, GitLab, and other code hosters. It's not limited to GitHub and other major platforms and even works with each service, which is accessible over SSH.
First you must install SSH-MITM. It's recommended to use the AppImage, because this works out of the box on most Linux machines.
$ wget https://github.com/ssh-mitm/ssh-mitm/releases/latest/download/ssh-mitm-x86_64.AppImage
-
Should SSH-MITM add a Codehoster user check as a default setting?
SSH-MITM is a tool to audit ssh sessions and protocols, which uses SSH as the transport protocol: https://github.com/ssh-mitm/ssh-mitm
-
Python API Documentation created with ChatGPT
you can find the project on github: https://github.com/ssh-mitm/ssh-mitm
- SSH-MitM has prebuilt windows executables
- SSH-MitM's new logo is a fish (OpenSSH's logo) on a hook
- SSH-MitM – Support for OpenSSH's Certificate Authority Planned
-
SSH-MITM - Support for OpenSSH's certificate authority planned
You should check the Revisionhistory of the Readme file first.. https://github.com/ssh-mitm/ssh-mitm/commit/564028af25c395528446fbb679c7392469d59bfd
-
SSH-MitM 2.0.0 – Licence change to GPLv3
The “customized wording” you’re seeing is “The LGPL”. It’s a different license from the GPL.
The history on the repo shows that the original license was GPL (June 2020), the author changed the license to LGPL (December 2022), and now they’re changing it to GPL again. https://github.com/ssh-mitm/ssh-mitm/commits/master/LICENSE
What are some alternatives?
gentoo - [MIRROR] Official Gentoo ebuild repository
cowrie - Cowrie SSH/Telnet Honeypot https://cowrie.readthedocs.io
guardian-agent - [beta] Guardian Agent: secure ssh-agent forwarding for Mosh and SSH
docker-sshd - Minimal Alpine Linux Docker image with sshd exposed and rsync installed
wezterm - A GPU-accelerated cross-platform terminal emulator and multiplexer written by @wez and implemented in Rust
sftpretty - Provides multi-threaded routines and high level protocol abstractions for a pretty quick & simple file transfer experience. Drop in replacement for pysftp.
mac-ssh-confirm - Protect against SSH Agent Hijacking on Mac OS X with the ability to confirm agent identities prior to each use
super-auto-pets - A tool to allow for viewing of arbitrary Super Auto Pets replays
ports - Read-only git conversion of OpenBSD's official cvs ports repository. Pull requests not accepted - send diffs to the ports@ mailing list.
mitm - 👨🏼💻 A customizable man-in-the-middle TCP intercepting proxy.
OpenSSL - TLS/SSL and crypto library
BDFProxy - Patch Binaries via MITM: BackdoorFactory + mitmProxy.