[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:02:17 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
Keywords: | Launchpad Bug:
---------------------+---------------------------
Currently it's possible to have a daemon write Eliot logs to a file. This
is great for development and debugging against non-sensitive nodes.
However, Eliot logs may contain privileged information (fURLs, caps,
filenames, etc).
It may not always be desirable to have this information written to disk.
Instead, it should be possible to publish it using a purely in-memory
scheme. Of course, one solution for this would be to write the file to an
in-memory filesystem (eg a Linux tmpfs mount). However, this is minimally
usable and it's unclear how portable it is. Instead, provide a cross-
platform Tahoe-LAFS-native solution.
--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3006>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage
More information about the tahoe-lafs-trac-stream
mailing list