RoganDawes

I have a Sherlotronics ComplexRX Keeloq receiver (running on an STM32 using my ESPHome port) that has an EEPROM for storing enrolled transmitters, and updating sequence numbers to prevent replay...

I realise this is a very old issue, and likely am necromancing this thread. However, I wanted to point out one more use case where this makes sense, in the...

To my mind, the DNS tunnelling is orthogonal/unrelated to the matter of redsocks being able to CONNECT FQDN, apart from redsocks extracting A/AAAA answers from the tunnelled responses. Unfortunately, my...

Would something like the following be acceptable, as an intermediate solution: Redsocks opens a named pipe, from which it reads entries in the form: ip.add.re.ss hostname.domain.com Any subsequent connections to...

Looking at how to implement this, it seems that I will have to define a new subsystem, with parser and init/fini etc. For the moment, I am only looking at...

I have started hacking something together, but am struggling with some (probably very basic) issues with reading from a named pipe, using libevent :-( I based my code on https://github.com/libevent/libevent/blob/master/sample/event-read-fifo.c,...

Aha! http://libevent-users.monkey.narkive.com/geYbLuFT/callback-firing-many-infinite-times-for-stdin had the explanation, echo was closing the other end of the pipe, and thus libevent was legitimately returning 0, indicating that the pipe was closed. Sigh! The more...

Think my PR above is still relevant, it could perhaps be implemented as a DNS "resolver" that simply allocates an IP address sequentially from a configured range (e.g. 10.0.0.0/8, or...

I have updated my branch with a very rudimentary/hackish implementation for http-connect. I'm sure I have done several things wrong, for instance, using a single hostnames hashtable, even though the...

It is definitely possible to run multiple stream servers, even if you do have to change the code a little to allow it. I took a copy of this code...