It does not use POSIX ACLs, extended attributes, nor any other
security-related functions which require non-standard Perl modules.
+There is preliminary support for "virtual users", but it is
+incomplete and undocumented.
+
=head1 INTERNAL FILES
lei runs with a umask of 077 to prevent other users on the
reside on shared storage and may be made world-readable to
other users on the local system.
+=head1 CORE DUMPS
+
+In case any process crashes, a core dumps may contain passwords or
+contents of sensitive messages. Please report these so they can be
+fixed (see L</CONTACT>).
+
=head1 NETWORK ACCESS
lei currently uses the L<curl(1)> and L<git(1)> executables in
usernames and passwords. These passwords are not encrypted in
memory and get transferred across processes via anonymous UNIX
sockets and pipes. They may be exposed via syscall tracing
-tools (e.g. L<strace(1)>).
+tools (e.g. L<strace(1)>), kernel and hardware bugs/attacks.
While credentials are not written to the filesystem by default,
it is possible for them to end up on disk if processes are
swapped out. Use of an encrypted swap partition is recommended.
+=head1 AUTHENTICATION METHODS
+
+LOGIN (username + password) is known to work over IMAP(S),
+as does AUTH=ANONYMOUS (which is used by L<public-inbox-imapd(1)>
+as part of our test suite). AUTHINFO may work for NNTP, but
+is untested. Testers will be needed for other authentication
+methods.
+
=head1 DENIAL-OF-SERVICE VECTORS
lei uses the same MIME parsing library as L<public-inbox-mda(1)>