[tahoe-lafs-trac-stream] [Tahoe-LAFS] #3006: Expose the Eliot logs in a safer way
Tahoe-LAFS
trac at tahoe-lafs.org
Wed Mar 20 17:14:03 UTC 2019
#3006: Expose the Eliot logs in a safer way
-------------------------+-----------------------
Reporter: exarkun | Owner:
Type: defect | Status: new
Priority: normal | Milestone: undecided
Component: unknown | Version: 1.12.1
Resolution: | Keywords:
Launchpad Bug: |
-------------------------+-----------------------
Comment (by exarkun):
Another possibility would be to pass a file descriptor in to the Tahoe-
LAFS process and stream logs to that.
Pros:
* Authentication is not necessary. You have a pipe between two processes
and no one else has a chance to get in the way.
* You don't have to listen on any TCP ports at all, slightly reducing your
attack surface.
* Twisted has good support for passing file descriptors to new processes
on POSIX.
Cons:
* Twisted has bad or no support for passing file descriptors to new
processes on Windows.
* Even more tightly bound to the concept of a single consumer.
* The only possibility for reconnection if you lose the pipe is restarting
the Tahoe-LAFS process (but there may be no real reason to lose the pipe).
--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3006#comment:3>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage
More information about the tahoe-lafs-trac-stream
mailing list