From: Falk Dayaram <FalkDayaram@lavabit.com>
To: emacs-devel@gnu.org
Subject: Re: Unifying network stream
Date: Sat, 02 Jul 2011 12:49:13 +0200 [thread overview]
Message-ID: <20110702104912.CAA1711BC6D@karen.lavabit.com> (raw)
In-Reply-To: <87pqlt5asw.fsf@keller.adm.naquadah.org> (Julien Danjou's message of "Sat, 02 Jul 2011 10:47:11 +0200")
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.
next prev parent reply other threads:[~2011-07-02 10:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 22:31 Unifying network stream falkdayaram
2011-07-02 8:47 ` Julien Danjou
2011-07-02 10:49 ` Falk Dayaram [this message]
2011-07-02 12:43 ` Lars Magne Ingebrigtsen
2011-07-04 16:12 ` Stefan Monnier
2011-07-05 15:18 ` Lars Magne Ingebrigtsen
2011-07-05 19:15 ` Stefan Monnier
2011-07-05 19:27 ` Lars Magne Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110702104912.CAA1711BC6D@karen.lavabit.com \
--to=falkdayaram@lavabit.com \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.