Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/bluemods/kik-go-proxy
An XMPP proxy server for Kik, written in Go
https://github.com/bluemods/kik-go-proxy
go kik kik-messenger proxy proxy-server tigase-xmpp-server xmpp
Last synced: 3 months ago
JSON representation
An XMPP proxy server for Kik, written in Go
- Host: GitHub
- URL: https://github.com/bluemods/kik-go-proxy
- Owner: bluemods
- License: mit
- Created: 2023-11-05T09:20:08.000Z (about 1 year ago)
- Default Branch: master
- Last Pushed: 2024-08-20T00:02:58.000Z (5 months ago)
- Last Synced: 2024-09-26T12:21:48.963Z (4 months ago)
- Topics: go, kik, kik-messenger, proxy, proxy-server, tigase-xmpp-server, xmpp
- Language: Go
- Homepage:
- Size: 199 KB
- Stars: 1
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE.md
Awesome Lists containing this project
README
# Kik XMPP Go Proxy
Originally written in Java, but now being ported to Go (for performance reasons and learning), this tool allows you to proxy XMPP connections from your server to another by MITMing them.
The server listens on port 5222 for plain text connections by default, and 5223 by default for SSL connections.
The server connects to Kik via port 443 by default.
Use cases for this include:
- Validating stream headers (`= 1.21.3 (on *nix it can be easily installed [here](https://github.com/udhos/update-golang))
## Install, build and run
```bash
git clone https://github.com/bluemods/kik-go-proxy && cd kik-go-proxy
```
```bash
go mod tidy && go build && ./kik-go-proxy
```
## Arguments
Note: If you use `-cert -key` or `-p12 -p12-pass` flag pairs, the program will use them to open an encrypted (SSL) connection.
The `-cert -key` and `-p12 -p12-pass` flags are mutually exclusive, you should use one or the other depending on the encoding of your certificate.
By default, the server accepts TLSv1.2 and up for clients connecting using SSL.
| Argument | Effect |
|------------|-----------------------------------------------------------------|
| -port | Change the port that the server will listen for connections on. |
| -cert | The relative path to your X.509 certificate. |
| -key | The relative path to your certificate key. |
| -p12 | The relative path to your .p12 certificate file. |
| -p12-pass | The relative path to the file containing the p12 cert password. |
| -i | The relative path to your interface IP list, one per line |
| -iface | The interface name to use, used with -i |
| -a | The relative path to an API key.
If specified, all clients need to include the x-api-key="KEY HERE" attribute in the stream header. |
| -whitelist | file containing JIDs / device IDs that do not require API key authentication, one per line |
| -ban | If specified, misbehaving clients will be IP banned from the server using iptables |
| -banner | If specified, the server sends back a 'server' header to the client upon successful authentication |
## Notices
- On Unix systems, you might get errors like ```Error accepting: accept tcp4 0.0.0.0:5222: accept4: too many open files```.
If you do, try [raising the ulimit.](https://stackoverflow.com/a/32325509)
- If running this on a public facing server without the -a argument, it is an open proxy. Make sure to configure your firewall to only allow trusted IPs.