Re: Unifying network stream

[Falk Dayaram <FalkDayaram@lavabit.com>]

Julien Danjou <julien@danjou.info> writes:

> On Sat, Jul 02 2011, falkdayaram@lavabit.com wrote:
>
>> Is there any chance this could be implemented in emacs 24?  I am
>> probably not the only one out here who uses an own network backend.
>
> Could you be more specific about what your patches do?

Basically what they do is to create a real network process that is used
for the actual communication (nc or gnutls-cli); and then setting up
specific iptables rules for that process to forward the actual
communcation to inhoise-specific exit nodes.  In reality it is a lot
more complicated, but thats out of the scope of this post ;)

What I would like to see implemented in emacs 24 is that there is only
one or two functions that may be used to open network streams.  In
particular, those functions are already there; open-network-stream and
make-network-process.  Unfortunately there is lots of lisp code which
rather uses the actual backend interface functions
(e.g. starttls-open-stream) rather than these neat high level function.
Therefore I'd like to deprecate all these backend functions.

Ultimately such a change allows easy management of emacs network stream
by advising only those two high level functions.  This is useful for
redirecting connection like I do, but there are also tons of other
usecases that may benefit from such a change; e.g. an inbuilt emacs
firewall or central OCSP validation of tls connections, etc.