Binary l33tness 100
Recover my key!
Archive: b100-730513593d83c6dede09b1bf92fb7bf8 Zip file size: 896443 bytes, number of entries: 3 -rw-rw-r-- 3.0 unx 992 tx defN 12-May-29 02:32 mac.h -rwxrwxr-x 3.0 unx 1105234 bx defN 12-May-29 02:32 ssh -rwxrwxr-x 3.0 unx 1378157 bx defN 12-May-29 02:32 sshd 3 files, 2484383 bytes uncompressed, 896013 bytes compressed: 63.9%
./ssh ./ssh: error while loading shared libraries: libcrypto.so.6: cannot open shared object file: No such file or directory ./sshd ./sshd: error while loading shared libraries: libcrypto.so.6: cannot open shared object file: No such file or directory
b100-730513593d83c6dede09b1bf92fb7bf8: Zip archive data, at least v2.0 to extract mac.h: Non-ISO extended-ASCII text, with very long lines, with NEL line terminators ssh: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.9, not stripped sshd: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.9, not stripped
- These can be ran on CentOS 5.4, maybe even other 5.x versions.
- When it complains about options being enabled, just comment them out of your /etc/ssh/sshd_config file. I think they were the GSSAPI and UsePAM options.
- sshd can be in any directory to run it.
- You have to specify the full path to it to run sshd. IE: it /root/sshd
- You can use the ssh program to ssh into localhost to use it. No need for two VMs.
- The included mac.h is similiar to /usr/include/mac.h and it changes when I ssh into the vm. This may be a cache or something.
- The /usr/include/mac.h file was being created by the included sshd
- /usr/include/mac.h is the answer