https://github.com/rofl0r/rocksock
blocking socket library with SSL, SOCKS/HTTP proxy chaining, and timeout
https://github.com/rofl0r/rocksock
c library lightweight proxychains socket socks ssl
Last synced: 2 months ago
JSON representation
blocking socket library with SSL, SOCKS/HTTP proxy chaining, and timeout
- Host: GitHub
- URL: https://github.com/rofl0r/rocksock
- Owner: rofl0r
- License: lgpl-2.1
- Created: 2011-06-11T02:14:19.000Z (over 14 years ago)
- Default Branch: master
- Last Pushed: 2022-03-25T22:47:43.000Z (over 3 years ago)
- Last Synced: 2025-04-04T04:12:55.920Z (6 months ago)
- Topics: c, library, lightweight, proxychains, socket, socks, ssl
- Language: C
- Homepage:
- Size: 124 KB
- Stars: 40
- Watchers: 9
- Forks: 13
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: COPYING
Awesome Lists containing this project
README
rocksock socket library (C) rofl0r
==================================
rocksock is a powerful (mostly) blocking networking library
written in C.
it was designed for small size, robustness, simplicity,
static linking and fine-grained error reporting and
configurability.
programming in a blocking way is much simpler, but can lead to
near infinite blocking. rocksock addresses this by providing
timeouts so the app doesn't get into a completely blocked
state and can react properly on any exceptional condition.
making the app fit for SSL only requires enabling one flag, and
SOCKS/HTTP proxy support is built-in as well.
- easy to use
- supports timeout
- supports SSL (optional, currently using openssl or cyassl backend)
- supports chaining of socks4/4a/5 proxies a la proxychains.
the maximum number of proxies can be configured at compiletime.
using a single proxy works as well, of course.
- no global state (except for ssl init routines)
- error reporting mechanism, showing the exact type
- supports DNS resolving (can be turned off for smaller size)
- does not use malloc, and in the DNS-less profile, does not use
any libc functions that could call it.
(malloc typically adds at least 20KB to the binary size if
statically linked).
of course once you build it with ssl support, ssl will definitely
make use of malloc().
you need to add NO_DNS_SUPPORT to your CFLAGS
so nothing that can call malloc gets pulled in, if you want a
minimal static binary (in that case you have to pass ipv4
addresses in dotted notation).
- optionally uses [libulz](https://github.com/rofl0r/libulz),
a lightweight C library, featuring things like
a snprintf replacement which doesnt include code for float
handling.
this can make a statically linked binary a couple dozen KB
smaller if no particularly bloated libc internals are being
used in other parts of linked-in code.
so if you use any SSL implementation, you won't gain anything
by using libulz.
build:
for a "default" build, for example for a distribution, just
use ./configure && make as usual.
advanced/customized build using RcB:
write your app, include the rocksock header using
a relative pathname, and then use the build tool
[rcb](https://github.com/rofl0r/rcb) on your main
C file, supplying all config options as CFLAGS. rcb will then
automatically find all required translation units and throw them
at once at the compiler, giving perfect opportunities for link-time
optimization.
typical tree structure:
```
myapp/
rocksock/
lib/ (libulz)
```
myapp/main.c:
```c
/* tiny program to see if a specific port on a specific host
is open for usage in shellscripts or similar. */
#include "../rocksock/rocksock.h"
#include
#include
static void usage(void) {
dprintf(2, "usage: prog ip port\n");
exit(1);
}
int main(int argc, char** argv) {
if(argc != 3) usage();
rocksock s;
rocksock_init(&s);
rocksock_set_timeout(&s, 5000);
int ret = rocksock_connect(&s, argv[1], atoi(argv[2]), 0);
rocksock_clear(&s);
return ret;
}
```
```sh
$ cd myapp
$ CFLAGS="-DUSE_SSL -flto -O3 -s -static" rcb main.c
```